CI Reliability 2026-05-26
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/73628 to node-test-pull-request/73726 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-26.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-26 00:33 | 0 | 9 | 6 | 4 | 81 | 9.38% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-26.md to see failure details
Progress
-
parallel/test-debugger-probe-failure-resume(20) -
parallel/test-debugger-probe-timeout(9) -
parallel/test-webcrypto-crypto-job-mode(8) -
parallel/test-fs-watch-recursive-delete(4) -
sequential/test-debugger-pid(3) -
ffi/test-ffi-void-parameter(2) -
sequential/test-watch-mode-restart-esm-loading-error(2) -
wpt/test-hr-time(2) -
ERROR: Error fetching remote repo 'origin'(2) -
fatal: No rebase in progress?(14) -
error: could not apply 61890720c8a... add readme and initial code(9) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(3) -
Error: getWindowSize EINVAL(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-26.md and the linked CI runs from node-test-pull-request/73628 through 73726. Investigate the listed recurring failures, then update the progress items as each cause is resolved and confirm that the affected PR checks become reliable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100