CI Reliability 2025-05-05
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/66502 to node-test-pull-request/66600 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-05.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-05-05 00:11 | 0 | 8 | 18 | 22 | 52 | 10.26% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-05-05.md to see failure details
Progress
-
pummel/test-heapdump-worker(8) -
pummel/test-heapdump-zlib(7) -
parallel/test-buffer-tostring-rangeerror(6) -
pummel/test-heapdump-shadow-realm(6) -
parallel/test-runner-run-watch(2) -
parallel/test-without-async-context-frame(2) -
pummel/test-heapdump-http2(2) -
pummel/test-heapdump-inspector(2) -
pummel/test-heapdump-tls(2) -
pummel/test-process-hrtime(2) -
pummel/test-timers(2) -
sequential/test-performance-eventloopdelay(2) -
Build timed out (after 30 minutes). Marking the build as failed.(6) -
Build timed out (after 60 minutes). Marking the build as failed.(5) -
fatal: No rebase in progress?(4) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(2) -
fatal error: Killed signal terminated program cc1plus(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-05.md and the linked node-test-pull-request builds, using the listed failure names as entry points. Review the failures generated by ncu-ci walk pr --stats=true --markdown reports/2025-05-05.md; done means investigating the repeated failures and updating the Progress checklist with their outcomes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100