CI Reliability 2026-05-05
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/73007 to node-test-pull-request/73106 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-05.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-05 00:29 | 0 | 23 | 16 | 3 | 58 | 23.71% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-05.md to see failure details
Progress
-
Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(4) -
fatal: No rebase in progress?(3) -
parallel/test-sqlite-database-sync(14) -
sequential/test-watch-mode-worker(9) -
parallel/test-process-finalization(5) -
parallel/test-runner-run(4) -
sequential/test-performance-eventloopdelay(4) -
test-runner/test-output-test-runner-watch-spec(3)
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-05.md and the linked node-test-pull-request jobs, using the listed failure messages and test names as entry points. Review the generated report for failure details, then investigate the recurring CI failures. Done means the listed failures are resolved and the affected pull requests no longer fail for these reasons.
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
- Needs clarification
- Newbie friendliness
- 35/100