CI Reliability 2025-04-04
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/65915 to node-test-pull-request/66014 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-04-04.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-04-04 00:10 | 0 | 2 | 22 | 2 | 74 | 2.04% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-04-04.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(11) -
ERROR: Error fetching remote repo 'origin'(3) -
Error: list index out of range(9) -
Failed to trigger node-test-commit(6) -
fatal: No rebase in progress?(4) -
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) -
error: remote GitHub already exists.(2) -
pummel/test-buffer-large-size(22) -
parallel/test-file-write-stream4(7) -
sequential/test-tls-session-timeout(6) -
pummel/test-heapdump-http2(4) -
pummel/test-timers(2) -
sequential/test-perf-hooks(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-04.md and the linked node-test-pull-request jobs, using the ncu-ci walk pr command described in the issue. Review the listed timeout, repository, trigger, Windows disk, and test failures to determine which failures are actionable. Done means the recurring failures are addressed and the affected CI jobs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100