CI Reliability 2025-04-03
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/65891 to node-test-pull-request/65989 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-04-03.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-04-03 00:10 | 0 | 2 | 15 | 4 | 79 | 2.08% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-04-03.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(11) -
Build timed out (after 30 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(2) -
Error: list index out of range(10) -
Failed to trigger node-test-commit(7) -
fatal: No rebase in progress?(3) -
ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ...(2) -
error C1085: Cannot write precompiled header file: 'out\Release\obj\cctest\cctest.pch': There is not enough space on the disk. [C:\workspace\node-compile-windows\node\cctest.vcxproj](2) -
fatal error: Killed signal terminated program cc1plus(2) -
pummel/test-buffer-large-size(23) -
parallel/test-file-write-stream4(10) -
sequential/test-tls-session-timeout(6) -
pummel/test-heapdump-http2(4) -
es-module/test-typescript-eval(2) -
parallel/test-cluster-fork-stdio(2) -
parallel/test-http-chunk-problem(2) -
pummel/test-timers(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-03.md and the linked node-test-pull-request runs to group the repeated timeout, infrastructure, and test failures. Review the listed failing tests, including pummel/test-buffer-large-size and parallel/test-file-write-stream4; done means the recurring failures are addressed and subsequent CI runs no longer reproduce them.
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
- 30/100