Skip to content

v8-canary

v8-canary #2

Manually triggered March 23, 2026 07:42
Status Failure
Total duration 1m 52s
Artifacts

v8-canary.yml

on: workflow_dispatch
metadata
6s
metadata
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
Build aarch64-unknown-linux-musl
Process completed with exit code 34.
Build x86_64-unknown-linux-musl
Process completed with exit code 34.
Build aarch64-unknown-linux-musl
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazelbuild/setup-bazelisk@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build aarch64-unknown-linux-musl
Failed to restore: Cache service responded with 400
Build x86_64-unknown-linux-musl
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazelbuild/setup-bazelisk@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build x86_64-unknown-linux-musl
Failed to restore: Cache service responded with 400