`request-ci` fails without error when CI is locked down

[targos]

See #39725 (comment)

The request-ci label was removed but the request-ci-failed label was not added.

I don't know what the Jenkins API responds in this case, but it doesn't seem like we handle it.

Workflow run: https://github.com/nodejs/node/runs/3296324085?check_suite_focus=true

[targos]

@nodejs/actions

[richardlau]

We should handle the error but during a CI lockdown I think it's expected that request-ci would not start CI's.

[targos]

during a CI lockdown I think it's expected that request-ci would not start CI's

agreed

[richardlau]

I'm fairly certain this is a node-core-utils issue.

[github-actions]

This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.

[github-actions]

This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.