CI Reliability 2025-04-28
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/66394 to node-test-pull-request/66492 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-04-28.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-04-28 00:11 | 0 | 5 | 34 | 1 | 60 | 5.05% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-04-28.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(4) -
Failed to trigger node-test-commit(5) -
error: remote GitHub already exists.(2) -
parallel/test-repl-import-referrer(10) -
parallel/test-stream-readable-unpipe-resume(5) -
parallel/test-buffer-tostring-rangeerror(4) -
parallel/test-http2-options-max-headers-block-length(4) -
parallel/test-debugger-break(3) -
parallel/test-without-async-context-frame(3) -
sequential/test-performance-eventloopdelay(3) -
sequential/test-tls-session-timeout(3) -
parallel/test-http2-close-while-writing(2) -
parallel/test-inspector-connect-to-main-thread(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)
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-28.md and the linked node-test-pull-request jobs, using the ncu-ci walk pr command context from the issue. Compare the repeated failures listed under Progress and identify which failures remain reproducible. Done means the relevant CI failures are addressed and the Progress checklist reflects their status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100