CI Reliability 2025-03-04
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/65461 to node-test-pull-request/65550 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-03-04.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-03-04 00:10 | 3 | 17 | 22 | 7 | 51 | 18.89% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-03-04.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(5) -
Failed to trigger sub builds(3) -
fatal: No rebase in progress?(3) -
sh: line 12: [: -gt: unary operator expected(3) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](2) -
fatal: no rebase in progress(2) -
parallel/test-assert-fail(15) -
parallel/test-runner-run-watch(12) -
parallel/test-file-write-stream4(6) -
sequential/test-perf-hooks(4) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-fs-watch-recursive-delete(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-03-04.md and the node-test-pull-request jobs 65461 through 65550 to review the listed failures. Trace the recurring build, repository, sub-build, and test errors, then verify that their corresponding checklist items are resolved in a subsequent CI run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, 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
- 25/100