CI Reliability 2025-02-23
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/65281 to node-test-pull-request/65376 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-02-23.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-02-23 00:11 | 1 | 7 | 22 | 18 | 52 | 8.64% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-02-23.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(3) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](8) -
fatal: No rebase in progress?(3) -
Error: EBUSY: resource busy or locked, rmdir '\\?\c:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.638'(2) -
parallel/test-assert-fail(10) -
parallel/test-file-write-stream4(8) -
parallel/test-runner-run-watch(6) -
parallel/test-buffer-tostring-rangeerror(4) -
parallel/test-runner-output(3) -
sequential/test-perf-hooks(3) -
parallel/test-http-get-pipeline-problem(2) -
parallel/test-http-server-connection-list-when-close(2) -
parallel/test-http-server-headers-timeout-keepalive(2) -
parallel/test-pipe-file-to-http(2) -
parallel/test-stream-readable-unpipe-resume(2) -
wpt/test-compression(2) -
wpt/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-02-23.md and the linked CI jobs, using the listed failure messages and test names to identify which failures are actionable. Review the command that generated the report, ncu-ci walk pr --stats=true --markdown, and trace each recurring failure to its relevant test or build step. Done means the selected CI failures are addressed and the affected jobs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100