CI Reliability 2026-06-11
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/73948 to node-test-pull-request/74047 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-06-11.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-06-11 00:40 | 1 | 25 | 20 | 4 | 50 | 26.32% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-06-11.md to see failure details
Progress
-
addons/worker-addon-exit/test(3) -
wpt/test-webcrypto(3) -
parallel/test-http-server-consumed-timeout(2) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(6) -
error: could not apply 61890720c8a... add readme and initial code(3) -
fatal: No rebase in progress?(3) -
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(2) -
Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(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-11.md and the linked node-test-pull-request runs 73948 through 74047. Review the failure details for the repeated checklist entries, then trace each one to its CI job or test. Done means the recurring failures are addressed and the affected CI runs become reliable again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, 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