Skip to content

Make release upload idempotent and retry-safe #113

Make release upload idempotent and retry-safe

Make release upload idempotent and retry-safe #113

Triggered via pull request June 1, 2026 02:49
Status Cancelled
Total duration 18m 32s
Artifacts 4

release.yml

on: pull_request
Matrix: windows-cpu
Matrix: ubuntu-22-cuda
Matrix: ubuntu-22-rocm
Matrix: windows-rocm
Matrix: windows-cuda
release
0s
release
Fit to window
Zoom out
Zoom in

Annotations

3 errors, 4 warnings, and 1 notice
windows-cuda (sm_89)
Canceling since a higher priority waiting request for Release-refs/pull/11/merge exists
windows-cuda (sm_89)
The operation was canceled.
Release
Canceling since a higher priority waiting request for Release-refs/pull/11/merge exists
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_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>0tvUcagAAAACIQQ6iIsvPRonk3FAlzUZSQ0hJMzBFREdFMDMyMQBFZGdl
windows-cuda (sm_89)
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:104f9c20c6971138cce4a1e20407d71c0b58d72c6bc52ece1f25107dbfeb58e7
llama-bin-win-cpu-x64.zip
15.3 MB
sha256:c9bc703e59ed53ac66824752211c0c593bb924b0c8330f8942e0c65e2f5eddf9
llama-bin-win-rocm-7.13-x64.zip
210 MB
sha256:31e08178e9991f73bf1029c3b21c13171135535aa0435f26b6e629d98cf09e78
llama-ubuntu-cuda-sm_89-x64.tar.xz
564 MB
sha256:073eb6142265063365cbc49b247cab6e350901b9709184e51e01e72f767b5758