CI Reliability 2025-05-07
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/66563 to node-test-pull-request/66653 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-07.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-05-07 00:11 | 9 | 10 | 14 | 10 | 57 | 12.35% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-05-07.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(12) -
Build timed out (after 30 minutes). Marking the build as failed.(8) -
Failed to trigger node-test-commit(3) -
pummel/test-heapdump-zlib(6) -
parallel/test-buffer-tostring-rangeerror(5) -
pummel/test-heapdump-worker(5) -
parallel/test-http2-client-socket-destroy(3) -
parallel/test-http2-close-while-writing(3) -
pummel/test-heapdump-shadow-realm(3) -
parallel/test-runner-run-watch(2) -
pummel/test-heapdump-tls(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-07.md and the linked CI job range to inspect details for the listed timeout, trigger, and test failures. Reproduce the affected jobs and use the Progress checklist to track investigation; done means the listed failures are resolved and CI reliability improves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100