CI Reliability 2025-09-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/69216 to node-test-pull-request/69314 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-09-22.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-09-22 00:11 | 2 | 14 | 30 | 14 | 40 | 16.67% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-09-22.md to see failure details
Progress
-
parallel/test-runner-run-watch(3) -
parallel/test-runner-watch-mode-kill-signal(3) -
parallel/test-http2-close-while-writing(2) -
parallel/test-worker-nearheaplimit-deadlock(2) -
sequential/test-performance-eventloopdelay(2) -
wpt/test-streams(2) -
Build timed out (after 60 minutes). Marking the build as failed.(6) -
Build timed out (after 30 minutes). Marking the build as failed.(4) -
Unexpected termination of the channel(2) -
fatal: No rebase in progress?(3) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
Error: HEAD does not match expected COMMIT_SHA_CHECK'(2) -
Failed to trigger node-test-commit(2) -
fatal error: too many errors emitted, stopping now [-ferror-limit=](2) -
fatal: no rebase in progress(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/2025-09-22.md and the generated report command shown in the issue, then inspect the linked CI run range and the listed failures. Use the Progress checklist to track each failure category; the work is done when the listed recurring CI failures have been investigated and the checklist reflects their resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100