CI Reliability 2026-06-19
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/74141 to node-test-pull-request/74235 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-06-19.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-06-19 00:45 | 1 | 23 | 12 | 4 | 60 | 24.21% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-06-19.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(3) -
ERROR: Error fetching remote repo 'origin'(4) -
Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(4) -
Failed to trigger node-test-commit(3) -
fatal: No rebase in progress?(2) -
addons/worker-addon-exit/test(11) -
parallel/test-cluster-dgram-reuse(4) -
parallel/test-fs-utimes-y2K38(4) -
parallel/test-runner-watch-mode(4) -
parallel/test-util-styletext(4) -
es-module/test-vm-contextified-script-leak(2) -
parallel/test-debugger-probe-failure-process-exit(2) -
parallel/test-debugger-probe-global-option-order(2) -
parallel/test-http-server-consumed-timeout(2) -
parallel/test-http2-close-while-writing(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-06-19.md and the linked node-test-pull-request runs to review the failure details behind each listed category. Investigate the failures and test names in the Progress checklist, then verify that the affected CI jobs no longer fail repeatedly and the build reliability improves.
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