CI Reliability 2026-05-09
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/73185 to node-test-pull-request/73281 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-09.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-09 00:30 | 1 | 16 | 7 | 7 | 69 | 17.39% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-09.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(8) -
fatal: No rebase in progress?(6) -
sh: line 12: [: -gt: unary operator expected(2) -
parallel/test-process-finalization(11) -
parallel/test-memory-usage(9) -
sequential/test-watch-mode-worker(7) -
sequential/test-debugger-pid(6) -
parallel/test-dgram-udp6-link-local-address(5) -
parallel/test-sqlite-database-sync(4) -
sequential/test-performance-eventloopdelay(4) -
test-runner/test-run-watch-dependency-repeatedly(3) -
test-runner/test-run-watch-run-duration(3) -
sea/test-single-executable-application-exec-argv-extension-env(2) -
sea/test-single-executable-application-inspect(2) -
test-runner/test-run-watch-repeatedly(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-09.md and the linked node-test-pull-request failures. Review the listed CI errors and failing tests, then trace each failure to its relevant entry point. Done means the recurring failures are addressed and the affected CI runs no longer reproduce them.
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
- Mostly clear
- Newbie friendliness
- 38/100