Skip to content
Post-trigger check new failing tests

fix #16

Sign in to view logs

fix

fix #16

Triggered via push May 6, 2026 10:44
@ydshiehydshieh
pushed 5a0393a
post_trigger_check_new_failing_tests
Status Success
Total duration 7m 10s
Artifacts 2

post_trigger_check_new_failing_tests.yml

on: push
Fetch inputs from source run
1m 21s
Fetch inputs from source run
Check new failures  /  Setup matrix for finding commits
7s
Check new failures / Setup matrix for finding commits
Matrix: Check new failures / Find commits for new failing tests
Check new failures  /  process bad commit reports
24s
Check new failures / process bad commit reports
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Fetch inputs from source run
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
Check new failures / Find commits for new failing tests (0)
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. 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/
Check new failures / process bad commit reports
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, slackapi/slack-github-action@6c661ce58804a1a20f6dc5fbee7f0381b469e001. 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
new_failures_with_bad_commit_run_models_gpu
1021 Bytes
sha256:b0a933c2487cf4091309e3455087b66f29450ca486d5e713fff4442d9e7642d2
new_failures_with_bad_commit_run_models_gpu_0
661 Bytes
sha256:78677d3003265ce0f77868198b949dae52990fc21245125cca5b9e3c64342482