nodejs / nodejs/reliability

CI Reliability 2025-04-21

Open
#1,180 0 comments 0 reactions 0 assignees View on GitHub

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/66290 to node-test-pull-request/66388 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-04-21.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-04-21 00:11 0 4 33 7 56 4.30%

Open https://github.com/nodejs/reliability/blob/main/reports/2025-04-21.md to see failure details

Progress
  • Build timed out (after 30 minutes). Marking the build as failed. (4)
  • Failed to trigger node-test-commit (3)
  • fatal: No rebase in progress? (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-debug\node\tools\v8_gypfiles\v8_turboshaft.vcxproj] (2)
  • error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj] (2)
  • fatal error: Killed signal terminated program cc1plus (2)
  • parallel/test-file-write-stream4 (7)
  • parallel/test-http2-options-max-headers-block-length (4)
  • sequential/test-performance-eventloopdelay (4)
  • sequential/test-tls-session-timeout (3)
  • parallel/test-debugger-break (2)
  • parallel/test-debugger-heap-profiler (2)
  • parallel/test-http2-close-while-writing (2)
  • parallel/test-runner-run-watch (2)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with reports/2025-04-21.md and the linked Jenkins runs from node-test-pull-request/66290 through 66388. Review the listed build, compiler, and test failures to determine which recurring failures remain reproducible. Done means addressing the reported failures so the affected CI jobs no longer fail repeatedly.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.