CI Reliability 2025-04-06
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/65974 to node-test-pull-request/66073 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-04-06.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-04-06 00:11 | 0 | 5 | 31 | 2 | 62 | 5.10% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-04-06.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(2) -
Error: list index out of range(7) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](3) -
Failed to trigger node-test-commit(2) -
fatal: No rebase in progress?(2) -
pummel/test-buffer-large-size(24) -
parallel/test-file-write-stream4(7) -
parallel/test-runner-plan(5) -
sequential/test-tls-session-timeout(4) -
sequential/test-performance-eventloopdelay(3) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-runner-run-watch(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-06.md and the linked node-test-pull-request jobs; review the listed failure messages and test names, including pummel/test-buffer-large-size and parallel/test-runner-plan. Re-run or inspect the ncu-ci walk pr --stats=true --markdown report generation command. Done means the reported failures have been investigated and the corresponding progress items are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100