CI Reliability 2026-05-22
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 57
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Failures in node-test-pull-request/73513 to node-test-pull-request/73607 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-22.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-22 00:34 | 0 | 30 | 12 | 9 | 49 | 32.97% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-22.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(3) -
sh: line 12: [: -gt: unary operator expected(8) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(4) -
fatal: No rebase in progress?(3) -
ERROR: out of memory(2) -
Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(2) -
Unexpected token '<', "(2) -
sequential/test-watch-mode-worker(3) -
wpt/test-hr-time(3) -
parallel/test-runner-run-watch(2) -
parallel/test-runner-watch-mode(2) -
test-runner/test-run-watch-run-duration(2)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading reports/2026-05-22.md and the linked node-test-pull-request runs, then reproduce or investigate the failures listed in the Progress section. Use ncu-ci walk pr --stats=true --markdown reports/2026-05-22.md to inspect the failure data. Done means the recurring CI failures are addressed and the affected checks no longer fail repeatedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100