The CI task 'node-test-commit-v8-linux' fails sometimes #58410
Description
I have noticed that this task has been failing frequently over the past period. Moreover, many PRs can trigger this failure, which seems to be unrelated to the changes made by the user.
console output:
21:38:39 + git rebase --abort
21:38:39 fatal: No rebase in progress?
21:38:39 + true
21:38:40 + git checkout -f _jenkins_local_branch
21:38:40 Already on '_jenkins_local_branch'
21:38:40 + git status
21:38:40 On branch _jenkins_local_branch
21:38:40 Untracked files:
21:38:40 (use "git add <file>..." to include in what will be committed)
21:38:40 depot_tools/
21:38:40 deps/_bad_scm/
21:38:40 deps/v8/depot_tools/
21:38:40
21:38:40 nothing added to commit but untracked files present (use "git add" to track)
21:38:40 + git rev-parse HEAD
21:38:40 413c49a2dbc8e28699b35a93c5f676c16f5a302e
21:38:40 + '[' -z '' ']'
21:38:40 + '[' nodejs '!=' nodejs ']'
21:38:40 + '[' node '!=' node ']'
21:38:40 + echo refs/pull/58350/head
21:38:40 + grep -qE '^(refs/)?pull/[0-9]+'
21:38:40 + echo 'Error: Starting CI for refs/pull/58350/head from nodejs/node is not allowed without a specified COMMIT_SHA_CHECK value'
21:38:40 Error: Starting CI for refs/pull/58350/head from nodejs/node is not allowed without a specified COMMIT_SHA_CHECK value
21:38:41 + exit 1
21:38:41 Build step 'Execute shell' marked build as failure
more failures:
- https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/6569/console
- https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/6567/console
- https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/6560/console
I am raising this issue because my PR #58350 is being blocked by it. This is my first contribution to Node.js, and I don't know how to handle this situation or how to call for help.