CI Reliability 2025-02-25
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/65324 to node-test-pull-request/65421 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-02-25.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-02-25 00:09 | 0 | 13 | 21 | 21 | 45 | 16.46% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-02-25.md to see failure details
Progress
-
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](5) -
fatal: No rebase in progress?(2) -
parallel/test-assert-fail(9) -
parallel/test-file-write-stream4(8) -
parallel/test-runner-run-watch(7) -
parallel/test-http-server-headers-timeout-keepalive(2) -
parallel/test-runner-output(2) -
parallel/test-zlib-brotli-16GB(2) -
sequential/test-perf-hooks(2) -
sequential/test-tls-session-timeout(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-02-25.md and the linked node-test-pull-request Jenkins runs to inspect the listed failures. Use the failure details to trace each affected test or CI step; done means the reported failures are addressed and the corresponding CI runs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- build-system, 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