Repository navigation
[executorch][muse] Serve Muse Glimmer CUDA batching on a batched-sequence cache #37752
pytorchbotbuild-cadence-runner.yml
on: pull_request
Resolve CI docker image
9s
vision-build
/
vision
9m 32s
cpu-test
/
...
/
test-aot
7m 15s
cpu-test
/
...
/
test-ops
7m 12s
hifi-op-test
/
hifi4
17m 38s
hifi1s-op-test
/
hifi1s
13m 17s
hifi5s-op-test
/
hifi5s
15m 30s
Annotations
12 errors, 11 warnings, and 1 notice
|
cpu-build / build
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
cpu-build / build
Process completed with exit code 1.
|
|
cpu-build / build
[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.
|
|
cpu-build / build
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
|
|
cpu-test / test-ops / test-ops
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
cpu-test / test-ops / test-ops
Process completed with exit code 1.
|
|
cpu-test / test-ops / test-ops
[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.
|
|
cpu-test / test-ops / test-ops
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
|
|
cpu-test / test-aot / test-aot
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
cpu-test / test-aot / test-aot
Process completed with exit code 1.
|
|
cpu-test / test-aot / test-aot
[OSDC] Step script exited with code 1. This is a script/workflow error, not an infrastructure issue. Check the step logs above for the actual failure.
|
|
cpu-test / test-aot / test-aot
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
|
|
Resolve CI docker image
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
cpu-build / build
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
vision-build / vision
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
cpu-test / test-ops / test-ops
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
cpu-test / test-aot / test-aot
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
hifi1s-build / hifi1s
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
hifi5s-build / hifi5s
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
hifi-build / hifi4
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
hifi1s-op-test / hifi1s
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, aws-actions/configure-aws-credentials@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
hifi5s-op-test / hifi5s
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, aws-actions/configure-aws-credentials@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
hifi-op-test / hifi4
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, aws-actions/configure-aws-credentials@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Resolve CI docker image
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
cadence-runner-build
|
530 KB |
sha256:f710cea09f307b7811dd35e4c1285fe6bbcb7c9c2af1cc6efe5bc7c61dea84d1
|
|
|
cadence-xtensa-build-hifi1s
|
1.43 MB |
sha256:1fe1f37a98c59a82d390fa8a5ee76db1da9aa409916c68c2a5990e720a577331
|
|
|
cadence-xtensa-build-hifi4
|
1.68 MB |
sha256:4635e55f9017da7229178300f625449dba3d3139c8748caf5fdf89902e0de848
|
|
|
cadence-xtensa-build-hifi5s
|
1.72 MB |
sha256:c3b7b3f7c64821b3abd7bb0e74725a9244da38d917a67962c9ec0791fcccceca
|
|
|
cadence-xtensa-build-vision
|
887 KB |
sha256:1ffd53bd13aa8653e5a9de7c4add019e18323bec51bff847e654cc654defe7c7
|
|