nodejs / nodejs/reliability

CI Reliability 2026-09-11

Open
#1,657 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/77192 to node-test-pull-request/77311 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-09-11.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-09-11 00:16 15 4 9 42 30 9.30%

Open https://github.com/nodejs/reliability/blob/main/reports/2026-09-11.md to see failure details

Progress
  • client-proxy/test-https-proxy-request-invalid-char-in-url (5)
  • parallel/test-http2-close-while-writing (3)
  • parallel/test-runner-watch-mode (3)
  • parallel/test-bench-cli (2)
  • parallel/test-bench-errors (2)
  • parallel/test-external-memory-reasonable-size (2)
  • parallel/test-fs-stat-bigint (2)
  • sequential/test-performance-eventloopdelay (2)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (2)
  • ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (15)
  • fatal: No rebase in progress? (3)
  • ERROR: All mapping items must start at the same column at line 7, column 1: (2)
  • ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (2)
  • Error: [WinError 5] Access is denied: 'C:\\Users\\Administrator\\clcache\\stats.txt.new' -> 'C:\\Users\\Administrator\\clcache\\stats.txt' (2)
  • ERROR: Error fetching remote repo 'origin' (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/2026-09-11.md and the linked CI runs to inspect details for the listed failures. Reproduce the affected node-test cases, including client-proxy/test-https-proxy-request-invalid-char-in-url and parallel/test-runner-watch-mode, along with the infrastructure errors. Done means the recurring failures in this report are addressed and the affected CI jobs become reliable.

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
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.