Skip to content

Merge CI triggered from @joshuacolvin0 of #751

Merge CI triggered from @joshuacolvin0 of

Merge CI triggered from @joshuacolvin0 of #751

Triggered via merge group April 3, 2026 23:52
Status Failure
Total duration 1h 42m 29s
Artifacts 14

merge.yml

on: merge_group
Matrix: go-tests / main
changes  /  Detect file changes
2m 41s
changes / Detect file changes
can_see_status
2s
can_see_status
rust-tests  /  Run Rust tests
rust-tests / Run Rust tests
bold-legacy  /  Run Bold Legacy challenge tests
bold-legacy / Run Bold Legacy challenge tests
codecov  /  Aggregate test results
11s
codecov / Aggregate test results
can_proceed
3s
can_proceed
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 7 warnings
go-tests / main (flaky) / Go tests
Process completed with exit code 1.
go-tests / main (defaults-B) / Go tests
Process completed with exit code 1.
go-tests / main (pathdb) / Go tests
Process completed with exit code 1.
can_proceed
Process completed with exit code 1.
go-tests / main (l3challenge) / Go tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
go-tests / main (stylus) / Go tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
go-tests / main (flaky) / Go tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
go-tests / main (defaults-A) / Go tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
go-tests / main (challenge) / Go tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
codecov / Aggregate test results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: codecov/test-results-action@v1. 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/
codecov / Aggregate test results
This action is being deprecated in favor of 'codecov-action'. Please update CI accordingly to use 'codecov-action@v5' with 'report_type: test_results'. The 'codecov-action' should and can be run at least once for coverage and once for test results

Artifacts

Produced during runtime
Name Size Digest
challenge-full.log
3.51 KB
sha256:53b8eb2fa59729e1e5be120bd46f4c7387d71bd660410045cab7905a6d32bb52
defaults-A-full.log
2.31 MB
sha256:7c3fbc33a2f86d099d58b399ad2f4cfd00d490191dcc41488c956c50a69f5972
defaults-B-full.log
1.9 MB
sha256:be9b126bd03b819cab82b1c7573660568d35b7d94142c5ec1e7694140ebfae5f
flaky-full.log
42.1 KB
sha256:9bb02b73788e9560b4c360ac942af90b6e6cc664e0477a3ba53c5700a723a1e4
junit-reports-go-challenge
3.69 KB
sha256:829779b0d0a8e1cfe6d6c04289ca2045a81c91dae06ecaefe9d91ec05b97f4c5
junit-reports-go-defaults-A
15.6 KB
sha256:d6606a3764e11e6dcc8dd3c416664af6108926cb07b8fb0fd1092f44327a6192
junit-reports-go-defaults-B
24.8 KB
sha256:279a7f6a24e688e5f0d38d3fd42125809482b47b497836ea9505157dea863ad9
junit-reports-go-flaky
4.17 KB
sha256:d6faaa899fc27eaa33b7a1553ac515015c228160a7dfdbdb8d21d8a6fdb5a7b2
junit-reports-go-l3challenge
3.25 KB
sha256:007e8804bf5d8295175aa32084347de63ad32841d6863d84baeec28b0f0d5d2b
junit-reports-go-pathdb
40.1 KB
sha256:cca8f30b0761032a7b2ffae6e7cb24910a2d469784d992fe40676f3986a87cfb
junit-reports-go-stylus
3.31 KB
sha256:2ad3011db93dc06d4a9ae89b740fb96072097dfff293692128aa1b98672a813c
l3challenge-full.log
3.12 KB
sha256:2b444563fd847aa4876dbc1b227657f2bbf2acf1ffd36f1b855522a8790103ef
pathdb-full.log
6.17 MB
sha256:16244aabffe38c0493ef66dacc1db0435d2712a0d0a820adc34f39775000f6db
stylus-full.log
3.23 KB
sha256:9f53d6d6ea85acb8615c51b371411e21493ba0ea5cd3277c861a00c33d38658d