CI Reliability 2026-05-10
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/73211 to node-test-pull-request/73308 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-10.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-10 00:30 | 0 | 6 | 7 | 5 | 82 | 6.32% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-10.md to see failure details
Progress
-
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(8) -
fatal: No rebase in progress?(4) -
sh: line 12: [: -gt: unary operator expected(2) -
parallel/test-process-finalization(13) -
parallel/test-memory-usage(12) -
sequential/test-debugger-pid(5) -
sequential/test-watch-mode-worker(5) -
parallel/test-dgram-udp6-link-local-address(4) -
parallel/test-sqlite-database-sync(3) -
test-runner/test-run-watch-dependency-repeatedly(3) -
sea/test-single-executable-application-exec-argv-extension-env(2) -
sea/test-single-executable-application-inspect(2) -
sequential/test-performance-eventloopdelay(2) -
test-runner/test-run-watch-run-duration(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-10.md and the linked CI runs, using the listed failure names to identify which failures are reproducible. Check the generated report after investigating the affected tests and CI errors; done means the identified failures are addressed and the CI reliability results improve.
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
- 30/100