CI Reliability 2026-05-30
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/73733 to node-test-pull-request/73832 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-30.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-30 00:34 | 0 | 22 | 21 | 10 | 47 | 24.44% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-30.md to see failure details
Progress
-
parallel/test-fs-watch-recursive-delete(5) -
async-hooks/test-improper-order(3) -
sequential/test-perf-hooks(3) -
parallel/test-debugger-probe-failure-resume(2) -
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) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
Command "git reset --hard" returned status code 128:(2) -
fatal: No rebase in progress?(8) -
error: could not apply 61890720c8a... add readme and initial code(4) -
ERROR: out of memory(2) -
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 node-test-pull-request jobs and the reliability report at reports/2026-05-30.md, focusing on the failures listed under Progress. Use the generated ncu-ci walk pr --stats=true --markdown reports/2026-05-30.md output to trace each repeated failure. Done means the listed recurring failures have been investigated and the CI reliability issue is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100