Release #121
superm1release.yml
on: schedule
Matrix: windows-cpu
Matrix: ubuntu-22-cuda
Matrix: ubuntu-22-rocm
Matrix: windows-rocm
Matrix: windows-cuda
release
3m 24s
Annotations
1 error, 22 warnings, and 1 notice
|
release
Unhandled error: SyntaxError: Unexpected identifier 'core'
|
|
windows-rocm (7.13.0, gfx906;gfx908;gfx90a;gfx942;gfx950;gfx1010;gfx1011;gfx1012;gfx1030;gfx1031;...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, ggml-org/ccache-action@v1.2.16. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-cuda (sm_90)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Jimver/cuda-toolkit@v0.2.21. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-cuda (sm_90)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0/sAdagAAAACi0FojfHRiSJamfyF2jzufTVNQMzExMDAwMTA1MDMxAEVkZ2U=
|
|
windows-cuda (sm_90)
Failed to restore: Cache service responded with 400
|
|
windows-cuda (sm_100)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Jimver/cuda-toolkit@v0.2.21. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-cuda (sm_100)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0/MAdagAAAAA/0TiQo/dHSIS/yYhWqPn8UEhMMzBFREdFMDExOQBFZGdl
|
|
windows-cuda (sm_100)
Failed to restore: Cache service responded with 400
|
|
windows-cuda (sm_80)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Jimver/cuda-toolkit@v0.2.21. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-cuda (sm_80)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0/8AdagAAAAD+OiKEIFv3RbbBGp8AjNBuQ0hJMzBFREdFMDMwOQBFZGdl
|
|
windows-cuda (sm_80)
Failed to restore: Cache service responded with 400
|
|
windows-cuda (sm_89)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Jimver/cuda-toolkit@v0.2.21. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-cuda (sm_89)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0AMEdagAAAABmUpUfwCfYTqxxAMjjyf8+TVNQMzExMDAwMTA3MDUxAEVkZ2U=
|
|
windows-cuda (sm_89)
Failed to restore: Cache service responded with 400
|
|
windows-cuda (sm_120)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Jimver/cuda-toolkit@v0.2.21. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-cuda (sm_120)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0/8AdagAAAADhSXSrnINKS6MhmpdsRgDQTEFYMzExMDAwMTExMDIzAEVkZ2U=
|
|
windows-cuda (sm_120)
Failed to restore: Cache service responded with 400
|
|
windows-cuda (sm_86)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Jimver/cuda-toolkit@v0.2.21. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-cuda (sm_86)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0/cAdagAAAACdhYllg2BaRblFfev41o/MUEhMMzBFREdFMDEwNwBFZGdl
|
|
windows-cuda (sm_86)
Failed to restore: Cache service responded with 400
|
|
windows-cuda (sm_75)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Jimver/cuda-toolkit@v0.2.21. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-cuda (sm_75)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0EMEdagAAAACxwtst0TpTT53l2Xn/PLseQ0hJMzBFREdFMDMxMwBFZGdl
|
|
windows-cuda (sm_75)
Failed to restore: Cache service responded with 400
|
|
windows-cpu (x64)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
llama-bin-ubuntu-rocm-7.13-x64.tar.gz
|
211 MB |
sha256:79884f13f5c06cf13b02ea6fa585b43916a1c98a0d8b414bf75450ec921c6ddb
|
|
|
llama-bin-win-cpu-x64.zip
|
15.3 MB |
sha256:78c04283cebd6e31fbe55b62af215b0b28593f248fad80105470af61c4d87f2a
|
|
|
llama-bin-win-rocm-7.13-x64.zip
|
210 MB |
sha256:35740263e0d2faa0f1c26ca510ba70ad41ef916ffa1753828080f9bed74e4a03
|
|
|
llama-ubuntu-cuda-sm_100-x64.tar.xz
|
567 MB |
sha256:7957dc5ded6cbe5cba3baa6819124569296af7f4164a67a2558abc209c5b29aa
|
|
|
llama-ubuntu-cuda-sm_120-x64.tar.xz
|
566 MB |
sha256:ff755ef99392c229bd209328e91bfcb82c7aaee67f9e449469385fed48207902
|
|
|
llama-ubuntu-cuda-sm_75-x64.tar.xz
|
567 MB |
sha256:932775f88c63050897aa704bf7beed863fa32d0dc3739799b4b537241c41a1a6
|
|
|
llama-ubuntu-cuda-sm_80-x64.tar.xz
|
565 MB |
sha256:03d5d0aae0bf517e091cfc737e03fedb71013403678941f458f796bdca939f25
|
|
|
llama-ubuntu-cuda-sm_86-x64.tar.xz
|
564 MB |
sha256:7122af6031ad3063704260a07d8f101b29ec2969325a60b581ca978c583905c8
|
|
|
llama-ubuntu-cuda-sm_89-x64.tar.xz
|
564 MB |
sha256:4f6636008e1fe5d70ab0a8669c395ce6ad76dd6da30fce75e9a3643b2e35dfa0
|
|
|
llama-ubuntu-cuda-sm_90-x64.tar.xz
|
566 MB |
sha256:a3f40a3ab3d21d6b72c4513a354a33a064a24687babef21019313af816ddedb4
|
|
|
llama-windows-cuda-sm_100-x64.7z
|
537 MB |
sha256:52c0cd3a8e162098aafc650dab867845fc8e8374ffcb694ff65bc061342cfc75
|
|
|
llama-windows-cuda-sm_120-x64.7z
|
537 MB |
sha256:ae3381c21d8c742f9cf1e70965c08019642f00c75a1f454bfd08ca1a0cd42d4e
|
|
|
llama-windows-cuda-sm_75-x64.7z
|
537 MB |
sha256:b7a264f4b0f1391a59a9fc8df5b2b4e1ec99dc642de31f7cc438ad0396e588e0
|
|
|
llama-windows-cuda-sm_80-x64.7z
|
536 MB |
sha256:c5476d2ccb06c4e873d679187fddb704a67615267df82c6d38caff2fc2d0baaf
|
|
|
llama-windows-cuda-sm_86-x64.7z
|
535 MB |
sha256:cb90a34fa3c91d2ecc353e2b7c030f47b6300ebf15c39e5d78ab40d8589c0bf1
|
|
|
llama-windows-cuda-sm_89-x64.7z
|
535 MB |
sha256:93714079c572fad0ecd3d209f1586dba7706278fef8b7edfe4cfaae2b4635eda
|
|
|
llama-windows-cuda-sm_90-x64.7z
|
536 MB |
sha256:285c46dca0e612fdfb645aa78639f77ddf3d1618271230a03952485c12e77b18
|
|