CI Reliability 2025-02-21
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/65248 to node-test-pull-request/65346 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-02-21.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-02-21 00:10 | 0 | 5 | 20 | 13 | 62 | 5.75% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-02-21.md to see failure details
Progress
-
parallel/test-assert-fail(10) -
parallel/test-buffer-tostring-rangeerror(10) -
parallel/test-file-write-stream4(6) -
parallel/test-runner-run-watch(5) -
parallel/test-http-get-pipeline-problem(3) -
parallel/test-runner-output(3) -
wpt/test-compression(3) -
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) -
sequential/test-tls-session-timeout(2) -
wpt/test-timers(2) -
Build timed out (after 30 minutes). Marking the build as failed.(6) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(6) -
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?(3) -
Error: EBUSY: resource busy or locked, rmdir '\\?\c:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.638'(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-21.md and the linked CI jobs for the listed failures, then inspect the corresponding test names such as parallel/test-assert-fail and wpt/test-compression. Reproduce the failures and use the Progress checklist to track them; done means the listed recurring failures are resolved and CI is green.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100