CI Reliability 2026-06-12
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/73972 to node-test-pull-request/74065 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-06-12.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-06-12 00:41 | 1 | 25 | 21 | 4 | 49 | 26.32% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-06-12.md to see failure details
Progress
-
addons/worker-addon-exit/test(2) -
parallel/test-debugger-probe-text(2) -
parallel/test-http-server-consumed-timeout(2) -
wpt/test-streams(2) -
wpt/test-webcrypto(2) -
ERROR: Error fetching remote repo 'origin'(2) -
error: could not apply 61890720c8a... add readme and initial code(4) -
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(2) -
fatal: No rebase in progress?(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-12.md and the linked node-test-pull-request runs 73972 through 74065. Review the failure details for each entry in the Progress list, then trace them to the affected CI jobs or tests. Done means the recurring failures are resolved and the relevant pull requests can return to a green CI result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100