CI Reliability 2026-05-02
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/72966 to node-test-pull-request/73064 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-02.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-02 00:28 | 0 | 18 | 20 | 4 | 58 | 18.75% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-02.md to see failure details
Progress
-
Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(5) -
fatal: no rebase in progress(4) -
fatal: No rebase in progress?(3) -
Failed to trigger fanned build(2) -
parallel/test-sqlite-database-sync(15) -
sequential/test-watch-mode-worker(7) -
parallel/test-process-finalization(6) -
sequential/test-performance-eventloopdelay(5) -
parallel/test-runner-watch-mode(3) -
test-runner/test-output-test-runner-watch-spec(2) -
test-runner/test-run-watch-run-duration(2) -
wpt/test-hr-time(2) -
wpt/test-timers(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-05-02.md and the linked node-test-pull-request builds to inspect the failure details behind the listed checks. Compare the repeated failures across the reported jobs; done means the identified CI failures are resolved and the affected checks no longer fail repeatedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100