Skip to content

Create a Runner operations task #303

Create a Runner operations task

Create a Runner operations task #303

Triggered via pull request March 12, 2026 03:19
Status Failure
Total duration 16m 17s
Artifacts 16

ci.yml

on: pull_request
Matrix: CLI / Action `devel`
Matrix: CLI / Action `main`
Matrix: CLI / Cargo `devel`
Matrix: CLI / Cargo `main`
Matrix: CLI / Script Cloud
Matrix: CLI / Script Gen
Matrix: CLI / Script Gen Version
CLI  /  CLI PR No-op
CLI / CLI PR No-op
CLI  /  Build CLI Docker
CLI / Build CLI Docker
Test  /  Cargo Test
10m 10s
Test / Cargo Test
Test  /  Cargo Test
0s
Test / Cargo Test
Test  /  API Smoke Test
4m 5s
Test / API Smoke Test
Test  /  Cargo Audit
52s
Test / Cargo Audit
Test  /  Cargo Unused Deps
5m 27s
Test / Cargo Unused Deps
Test  /  Cargo Check Workspace (not(plus))
2m 53s
Test / Cargo Check Workspace (not(plus))
Test  /  Bencher Console (not(plus))
3m 27s
Test / Bencher Console (not(plus))
Test  /  Docker API Smoke Test
3m 4s
Test / Docker API Smoke Test
Build  /  Build GitHub Action
0s
Build / Build GitHub Action
Build  /  Build API Docker
15m 43s
Build / Build API Docker
Build  /  Build Console Docker
2m 34s
Build / Build Console Docker
Build  /  Build `bencher` Nix Package
7m 13s
Build / Build `bencher` Nix Package
Build  /  Build `api` Nix Package
14m 57s
Build / Build `api` Nix Package
Matrix: Runner / build_runner
Waiting for pending jobs
Runner  /  Test Runner Scenarios
Runner / Test Runner Scenarios
Matrix: CLI / Build CLI
Build  /  Build `bencher_valid` WASM
1m 49s
Build / Build `bencher_valid` WASM
Matrix: CLI / Package CLI
Build  /  Test `bencher_valid` WASM
45s
Build / Test `bencher_valid` WASM
Build  /  vitest
52s
Build / vitest
Build  /  Build Console UI
1m 56s
Build / Build Console UI
Test  /  ...  /  Track Benchmarks with Bencher
Test / Track Benchmarks / Track Benchmarks with Bencher
Matrix: Release / Release API Smoke Test
Waiting for pending jobs
Deploy  /  Deploy API to Fly.io Test
Deploy / Deploy API to Fly.io Test
Deploy  /  Deploy API to Fly.io Dev
Deploy / Deploy API to Fly.io Dev
Release  /  Release Bencher
Release / Release Bencher
Deploy  /  Deploy API to Fly.io Prod
Deploy / Deploy API to Fly.io Prod
Deploy  /  Deploy Console UI to Netlify Dev
Deploy / Deploy Console UI to Netlify Dev
Deploy  /  Deploy Console UI to Netlify Prod
Deploy / Deploy Console UI to Netlify Prod
CI Success
3s
CI Success
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 25 warnings
Test / Cargo Audit
Process completed with exit code 1.
Build / vitest
Response status code does not indicate success: 401 (Unauthorized).
Test / Cargo Unused Deps
Process completed with exit code 101.
Test / Cargo Unused Deps
Process completed with exit code 101.
CI Success
Process completed with exit code 1.
Detect Changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@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/
Test / Cargo Audit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. 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/
Lint / Cargo Clippy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. 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 / Build `bencher_valid` WASM
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4. 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 / Build Console Docker
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@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 / Test `bencher_valid` WASM
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. 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 / vitest
Back off 26.861 seconds before retry.
Build / vitest
Failed to download action 'https://api.github.com/repos/actions/download-artifact/tarball/d3f86a106a0bac45b974a628896c90dbdf5c8093'. Error: Response status code does not indicate success: 401 (Unauthorized). 4441:AE409:B2D5CA:B6047E:69B2316E
Build / vitest
Back off 21.663 seconds before retry.
Build / vitest
Failed to download action 'https://api.github.com/repos/actions/download-artifact/tarball/d3f86a106a0bac45b974a628896c90dbdf5c8093'. Error: Response status code does not indicate success: 401 (Unauthorized). 4440:215A1D:BA8D83:BDBC9D:69B23158
CLI / Build CLI (macos-x86-64, macos-14, x86_64-apple-darwin)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
Test / API Smoke Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-go@v5. 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/
Test / API Smoke Test
Restore cache failed: Dependencies file is not found in /home/runner/work/bencher/bencher. Supported file pattern: go.sum
Build / Build Console UI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. 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/
CLI / Build CLI (linux-arm-64, ubuntu-22.04, aarch64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, mlugg/setup-zig@v1. 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/
CLI / Build CLI (macos-arm-64, macos-14, aarch64-apple-darwin)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
CLI / Build CLI (linux-x86-64, ubuntu-22.04, x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, mlugg/setup-zig@v1. 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/
Test / Cargo Unused Deps
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. 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/
CLI / Build CLI (windows-x86-64, windows-2022, x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
Test / Cargo Bench
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
CLI / Build CLI (windows-arm-64, windows-2022, aarch64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
Test / Cargo Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4. 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/
CLI / Package CLI (linux-x86-64, ubuntu-22.04, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/upload-artifact@v4. 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/
CLI / Package CLI (linux-arm-64, ubuntu-22.04, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/upload-artifact@v4. 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 / Build API Docker
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@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/

Artifacts

Produced during runtime
Name Size Digest
bencher-api.tar.gz
59.9 MB
sha256:1b1d0144044b3d0bda5420525ce282ff828816b4758fd15b0291a9d11d5acb7d
bencher-console.tar.gz
149 MB
sha256:77c29d33abd42d35518fce689e514ee082b0589298c1fe02d59e2dc2ee52e93a
bencher-u-ep-runner-ops-linux-arm-64
6.12 MB
sha256:012b19b98ede23e325d96da2d3e5a060df55791035868c4abf8c8e69596dca78
bencher-u-ep-runner-ops-linux-arm-64.deb
3.58 MB
sha256:5e2c9cd5636c7ccab99f2b40a2e26b064c185a6811281e33292d12624d25c399
bencher-u-ep-runner-ops-linux-x86-64
6.47 MB
sha256:ef88fc92b630c6e261d7368c63e2b3e7bf44086b9baa8c9a45928c12fc8ab450
bencher-u-ep-runner-ops-linux-x86-64.deb
4.06 MB
sha256:2668b5d43d75e3cd2235a625d2ad29367d167c41ae64d7ca24a3a3b57f027c08
bencher-u-ep-runner-ops-macos-arm-64
7.57 MB
sha256:a5b927fca6b23caf27f66fd23eec3b1dd4b034278d0cda29ff8b1d15e9596a7e
bencher-u-ep-runner-ops-macos-x86-64
7.49 MB
sha256:9e8c66ef9c32213830cd6ccbe89ed18fe6732d5489e73eb29d5d7a04d323a0f7
bencher-u-ep-runner-ops-windows-arm-64.exe
6.6 MB
sha256:0ef456aab23fd82879bc19159901c0710844cc477b318689f841015bd70dc6ac
bencher-u-ep-runner-ops-windows-x86-64.exe
6.84 MB
sha256:1e8b1830c82e7afd9c511d763e1d427f944981f4672e5457bd4dced04e6e8506
bencher-valid-pkg
353 KB
sha256:8b03860e09c9d11bf96edcaf64743be49a0123a6e7295cf752a998d2cd6d21eb
bencherdev~bencher~GUWNAK.dockerbuild
161 KB
sha256:f99112051b82284601fcbc6e43d8b40eb31a54ccba1b4673c8e7619e1213f84e
bencherdev~bencher~NZ4BJY.dockerbuild
212 KB
sha256:3df263108c2ead6961ac7c0a607263716e4c8a56014f737a6e866438596d919d
benchmark_results.txt
2.71 KB
sha256:abeffce1ad48436bd83e1b254f9446b8c0a3108628c146aa83e2395db3f8f10e
event.json
3.33 KB
sha256:ae3b2cc9ee56b505f56fde9acb96ac6ae211a0ce6c6ff36c20ee2e5f67c70ba5
perf.jpeg
42.3 KB
sha256:45353b0d1ffea308b571342911ce1b9a8570153465a88c2c97e05e716787af00