CI Reliability 2025-04-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/66412 to node-test-pull-request/66509 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-04-30.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-04-30 00:11 | 0 | 3 | 33 | 2 | 62 | 3.06% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-04-30.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(5) -
Failed to trigger node-test-commit(5) -
fatal: No rebase in progress?(3) -
parallel/test-repl-import-referrer(10) -
parallel/test-stream-readable-unpipe-resume(4) -
parallel/test-without-async-context-frame(4) -
sequential/test-tls-session-timeout(4) -
parallel/test-buffer-tostring-rangeerror(3) -
sequential/test-performance-eventloopdelay(3) -
parallel/test-debugger-break(2) -
parallel/test-http-get-pipeline-problem(2) -
parallel/test-http2-close-while-writing(2) -
parallel/test-http2-options-max-headers-block-length(2) -
parallel/test-tls-min-max-version(2) -
parallel/test-whatwg-url-canparse(2) -
parallel/test-zlib-brotli-16GB(2) -
parallel/test-zlib-brotli-flush(2) -
pummel/test-heapdump-http2(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-04-30.md and the linked node-test-pull-request runs to examine the listed timeout, trigger, and test failures. Use the generated ncu-ci report and the individual CI jobs to determine which failures remain reproducible. Done means the listed failure categories have been investigated and the progress checklist reflects their resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100