Skip to content

fix: devnet consensus config test (k=3 not 5), enable hanzo-l2 + hanz… #21

fix: devnet consensus config test (k=3 not 5), enable hanzo-l2 + hanz…

fix: devnet consensus config test (k=3 not 5), enable hanzo-l2 + hanz… #21

Triggered via push April 4, 2026 21:20
Status Failure
Total duration 53s
Artifacts 1

build-docker.yml

on: push
docker  /  build-amd64
50s
docker / build-amd64
docker  /  build-arm64
0s
docker / build-arm64
docker  /  create-manifest
0s
docker / create-manifest
docker  /  tag-single-arch
0s
docker / tag-single-arch
docker  /  deploy
0s
docker / deploy
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
docker / build-amd64
buildx failed with: ERROR: failed to build: failed to solve: failed to compute cache key: failed to calculate checksum of ref jqzhuxykvkdyvsyi0c0at5t3j::q8uyrlvnnwurhy7m2fcnhm1pu: "/build/hanzo-tools-runner-resources": not found
docker / build-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Artifacts

Produced during runtime
Name Size Digest
hanzoai~node~WPN7O3.dockerbuild
27 KB
sha256:320d194cb9d2de864d93d8f3619ae36c2339b01d1639df7ff6c2569c2c83599c