CI Reliability 2026-04-17
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/72630 to node-test-pull-request/72726 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-17.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-04-17 00:24 | 1 | 18 | 15 | 7 | 59 | 19.57% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-04-17.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(3) -
fatal: No rebase in progress?(6) -
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) -
sequential/test-fs-watch(8) -
wpt/test-wasm-jsapi(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-dependency-repeatedly(3) -
test-runner/test-run-watch-without-file(3) -
parallel/test-dgram-udp6-link-local-address(2) -
parallel/test-fs-cp-sync-preserve-timestamps-readonly(2) -
parallel/test-fs-promises-watch(2) -
parallel/test-fs-watch(2) -
parallel/test-fs-watch-enoent(2) -
sequential/test-debugger-pid(2) -
test-runner/test-run-watch-run-duration(2) -
wpt/test-wasm-webapi(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 reports/2026-04-17.md and the linked CI job range, then use the listed failure categories and test names to investigate each recurring failure. The issue is complete when the reported CI failures have been addressed and the corresponding progress items can be checked off.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, 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