CI Reliability 2026-04-16
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/72611 to node-test-pull-request/72708 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-16.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-04-16 00:25 | 1 | 18 | 15 | 8 | 58 | 19.78% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-04-16.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(2) -
fatal: No rebase in progress?(5) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(3) -
sh: line 12: [: -gt: unary operator expected(2) -
wpt/test-wasm-jsapi(9) -
sequential/test-fs-watch(8) -
parallel/test-watch-mode-files_watcher(7) -
pummel/test-fs-watch-non-recursive(7) -
parallel/test-fs-watch-recursive-delete(5) -
sequential/test-performance-eventloopdelay(5) -
test-runner/test-run-watch-run-duration(3) -
test-runner/test-run-watch-without-file(3) -
parallel/test-dgram-udp6-link-local-address(2) -
parallel/test-fs-promises-watch(2) -
parallel/test-fs-watch(2) -
parallel/test-fs-watch-enoent(2) -
parallel/test-net-connect-memleak(2) -
parallel/test-runner-output(2) -
sequential/test-debugger-pid(2) -
test-runner/test-run-watch-dependency-repeatedly(2) -
wpt/test-hr-time(2) -
wpt/test-webcrypto(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 the linked node-test-pull-request jobs and the generated reports/2026-04-16.md report, using the listed failure messages and recurring test names as the entry points. Investigate which failures are actionable rather than transient; done means the identified CI failures are addressed and the affected checks no longer fail repeatedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100