nodejs / nodejs/reliability

CI Reliability 2025-10-10

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-10-10 00:11 1 0 28 4 67 0.00%

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

Progress
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (2)
  • Build timed out (after 60 minutes). Marking the build as failed. (2)
  • ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ... (3)
  • fatal error: ld terminated with signal 9 [Killed] (2)
  • parallel/test-without-async-context-frame (19)
  • sequential/test-worker-prof (14)
  • sequential/test-perf-hooks (12)
  • client-proxy/test-https-proxy-request-invalid-char-in-url (8)
  • parallel/test-http2-close-while-writing (8)
  • parallel/test-runner-run-watch (6)
  • wpt/test-hr-time (6)
  • parallel/test-runner-watch-mode-kill-signal (5)
  • parallel/test-quic-test-client (4)
  • parallel/test-fs-watch-recursive-delete (2)
  • parallel/test-zlib-brotli-16GB (2)
  • wpt/test-wasm-webapi (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-10.md and the linked node-test-pull-request jobs, then examine the listed failure categories and test names. Reproduce or inspect each recurring failure and update the Progress checklist as causes are addressed; done means the reported failures have been investigated and the CI runs no longer reproduce them.

Written by the indexing model from the issue text.

Assessment

Tech stack
nodejs, 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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.