CI Reliability 2026-05-20
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/73469 to node-test-pull-request/73558 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-20.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-20 00:35 | 5 | 29 | 14 | 6 | 46 | 32.58% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-20.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'(4) -
fatal: No rebase in progress?(6) -
sh: line 12: [: -gt: unary operator expected(6) -
ERROR: out of memory(4) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(3) -
sequential/test-watch-mode-worker(6) -
sequential/test-watch-mode-restart-esm-loading-error(3) -
test-runner/test-run-watch-repeatedly(3) -
parallel/test-http2-close-while-writing(2) -
parallel/test-worker-nearheaplimit-deadlock(2) -
test-runner/test-run-watch-dependency-repeatedly(2) -
test-runner/test-run-watch-run-duration(2) -
test-runner/test-run-watch-without-file(2) -
wpt/test-hr-time(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 with reports/2026-05-20.md and the linked node-test-pull-request jobs to inspect the failure details. Group the listed CI errors and failing tests, including test-runner/test-run-watch-mode-worker and wpt/test-hr-time, before determining which failures can be addressed. The issue does not define a specific change or completion condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100