ydshieh
Fetch inputs from source run
48s
Check new failures
/
Setup matrix for finding commits
4s
Matrix: Check new failures / Find commits for new failing tests
Check new failures
/
process bad commit reports
13s
Annotations
6 errors and 1 warning
|
Check new failures / Find commits for new failing tests (0)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
Check new failures / Find commits for new failing tests (0)
Process completed with exit code 1.
|
|
Check new failures / Find commits for new failing tests (0)
Error: failed to run script step: command terminated with non-zero exit code: error executing command [sh -e /__w/_temp/c2cbbef0-492b-11f1-8103-2d05b800016c.sh], exit code 1
|
|
Check new failures / process bad commit reports
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
Check new failures / process bad commit reports
Process completed with exit code 1.
|
|
Check new failures / process bad commit reports
Error: failed to run script step: command terminated with non-zero exit code: error executing command [sh -e /__w/_temp/d0c30860-492b-11f1-8a96-73ada67efe4f.sh], exit code 2
|
|
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/
|