CI Reliability 2025-05-01
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/66424 to node-test-pull-request/66518 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-01.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-05-01 00:12 | 2 | 4 | 30 | 2 | 62 | 4.17% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-05-01.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(6) -
Failed to trigger node-test-commit(3) -
fatal: No rebase in progress?(3) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(2) -
error: remote GitHub already exists.(2) -
fatal error: Killed signal terminated program cc1plus(2) -
parallel/test-repl-import-referrer(9) -
parallel/test-without-async-context-frame(4) -
sequential/test-performance-eventloopdelay(4) -
sequential/test-tls-session-timeout(4) -
parallel/test-stream-readable-unpipe-resume(3) -
parallel/test-buffer-tostring-rangeerror(2) -
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-05-01.md and the linked node-test-pull-request builds 66424 through 66518; the report was generated with ncu-ci walk pr --stats=true --markdown. Investigate the listed build and test failures, then verify that the affected failures are resolved and CI reliability improves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, node.js, 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