CI Reliability 2025-05-24
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/66934 to node-test-pull-request/67033 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-24.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-05-24 00:11 | 0 | 13 | 18 | 1 | 68 | 13.13% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-05-24.md to see failure details
Progress
-
fatal: No rebase in progress?(4) -
parallel/test-http2-debug(21) -
pummel/test-blob-slice-with-large-size(14) -
parallel/test-buffer-tostring-range(11) -
parallel/test-buffer-tostring-rangeerror(11) -
async-hooks/test-emit-after-on-destroyed(4) -
async-hooks/test-improper-unwind(3) -
parallel/test-runner-run-watch(3) -
parallel/test-runner-output(2) -
parallel/test-stream-readable-to-web(2) -
parallel/test-worker-nearheaplimit-deadlock(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/2025-05-24.md and the linked node-test-pull-request jobs to inspect the failure details. Review the listed failures, including parallel/test-http2-debug and the buffer, async-hooks, runner, stream, and worker tests, then reproduce the relevant CI cases. Done means the reported recurring failures are resolved or otherwise tracked with updated progress.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100