nodejs / nodejs/reliability

CI Reliability 2025-04-14

Open
#1,173 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/66145 to node-test-pull-request/66244 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-04-14.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-04-14 00:11 1 0 34 7 58 0.00%

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

Progress
  • pummel/test-buffer-large-size (18)
  • parallel/test-file-write-stream4 (8)
  • parallel/test-runner-plan (7)
  • parallel/test-crypto-authenticated (3)
  • parallel/test-debugger-heap-profiler (3)
  • sequential/test-tls-session-timeout (3)
  • parallel/test-repl-custom-eval (2)
  • parallel/test-stream-readable-unpipe-resume (2)
  • sequential/test-performance-eventloopdelay (2)
  • Build timed out (after 30 minutes). Marking the build as failed. (2)
  • ERROR: Error fetching remote repo 'origin' (3)
  • Error: list index out of range (7)
  • ERROR: The process with PID 9828 (child process of PID 10148) could not be terminated. (2)
  • Failed to trigger node-test-commit (2)
  • error C2065: 'NoArrayBufferZeroFillScope': undeclared identifier [C:\workspace\node-compile-windows\node\libnode.vcxproj] (2)
  • error: remote GitHub already exists. (2)
  • fatal: No rebase in progress? (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-14.md and the failures linked from this issue, using the listed ncu-ci walk command to understand how the report was generated. Investigate the named test failures and CI errors across the affected jobs; done means the Progress entries have been addressed and subsequent CI runs provide evidence of improvement.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.