CI Reliability 2026-05-31
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/73740 to node-test-pull-request/73838 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-31.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-31 00:36 | 0 | 22 | 21 | 9 | 48 | 24.18% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-31.md to see failure details
Progress
-
parallel/test-fs-watch-recursive-delete(5) -
async-hooks/test-improper-order(3) -
parallel/test-fs-read-stream(2) -
parallel/test-http2-close-while-writing(2) -
parallel/test-webcrypto-crypto-job-mode(2) -
test-runner/test-run-watch-cwd-isolation-none(2) -
wpt/test-streams(2) -
wpt/test-webcrypto(2) -
fatal: No rebase in progress?(7) -
Failed to trigger sub builds(4) -
error: could not apply 61890720c8a... add readme and initial code(3) -
sh: line 1: 429:: command not found(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 the linked reliability report at reports/2026-05-31.md and review the failures listed in the issue, including the named test paths and CI errors. Trace each repeated failure back to its job or test; done means the recurring failures are understood and the corresponding checklist items can be resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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