CI Reliability 2025-04-18
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/66235 to node-test-pull-request/66336 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-04-18.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-04-18 00:11 | 0 | 2 | 28 | 7 | 63 | 2.15% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-04-18.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(6) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
Error: list index out of range(12) -
error C2065: 'NoArrayBufferZeroFillScope': undeclared identifier [C:\workspace\node-compile-windows\node\libnode.vcxproj](9) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](7) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows-debug\node\tools\v8_gypfiles\v8_turboshaft.vcxproj](4) -
error: remote GitHub already exists.(3) -
Failed to trigger node-test-commit(2) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers_host.vcxproj](2) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_turboshaft_host.vcxproj](2) -
fatal: No rebase in progress?(2) -
parallel/test-file-write-stream4(8) -
parallel/test-runner-plan(5) -
sequential/test-tls-session-timeout(4) -
parallel/test-debugger-break(3) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-debugger-heap-profiler(2) -
sequential/test-performance-eventloopdelay(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-18.md and the linked node-test-pull-request jobs, using the listed timeout, compiler, Git, and test failures as entry points. The issue does not identify one change to make or define a completion criterion, so the report details must be reviewed before a concrete fix can be scoped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, 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