nodejs / nodejs/reliability

CI Reliability 2025-10-29

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-10-29 00:12 0 21 20 2 57 21.43%

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

Progress
  • Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 938203, exit value: 1 (5)
  • Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 957237, exit value: 1 (4)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (2)
  • ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (11)
  • fatal: No rebase in progress? (2)
  • sequential/test-worker-prof (8)
  • es-module/test-esm-wasm (4)
  • parallel/test-watch-mode-kill-signal-override (4)
  • addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max (3)
  • addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-binary (3)
  • addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-utf8 (3)
  • parallel/test-quic-test-client (3)
  • addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-base64 (2)
  • addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-hex (2)
  • addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-2 (2)
  • parallel/test-http2-close-while-writing (2)
  • parallel/test-net-connect-abort-controller (2)
  • parallel/test-perf-hooks-timerify (2)
  • parallel/test-runner-output (2)
  • parallel/test-watch-mode-files_watcher (2)
  • parallel/test-watch-mode-kill-signal-default (2)
  • sequential/test-perf-hooks (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-10-29.md and the linked CI job range, generated by ncu-ci walk pr --stats=true --markdown reports/2025-10-29.md. Review the listed shell, workspace, rebase, and Node.js test failures, then use the corresponding CI logs and test names to identify which failures are actionable. Done requires resolving the recurring failures or documenting their disposition in the Progress checklist.

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
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.