nodejs / nodejs/reliability

CI Reliability 2025-10-02

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-10-02 00:10 1 3 8 5 83 3.19%

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

Progress
  • Unexpected termination of the channel (4)
  • Build timed out (after 30 minutes). Marking the build as failed. (2)
  • fatal: No rebase in progress? (2)
  • sequential/test-single-executable-application (34)
  • sequential/test-single-executable-application-asset-keys (34)
  • sequential/test-single-executable-application-asset-keys-empty (34)
  • sequential/test-single-executable-application-assets (34)
  • sequential/test-single-executable-application-assets-raw (34)
  • sequential/test-single-executable-application-disable-experimental-sea-warning (34)
  • sequential/test-single-executable-application-exec-argv (34)
  • sequential/test-single-executable-application-exec-argv-empty (34)
  • sequential/test-single-executable-application-exec-argv-extension-cli (34)
  • sequential/test-single-executable-application-exec-argv-extension-env (34)
  • sequential/test-single-executable-application-exec-argv-extension-none (34)
  • sequential/test-single-executable-application-inspect (34)
  • sequential/test-single-executable-application-inspect-in-sea-flags (34)
  • sequential/test-single-executable-application-snapshot (34)
  • sequential/test-single-executable-application-snapshot-and-code-cache (34)
  • sequential/test-single-executable-application-snapshot-worker (34)
  • sequential/test-single-executable-application-use-code-cache (34)
  • parallel/test-runner-run-watch (31)
  • client-proxy/test-https-proxy-request-invalid-char-in-url (17)
  • parallel/test-runner-watch-mode-kill-signal (10)
  • parallel/test-quic-test-client (8)
  • sequential/test-perf-hooks (7)
  • parallel/test-without-async-context-frame (6)
  • parallel/test-http2-close-while-writing (5)
  • wpt/test-hr-time (4)
  • parallel/test-fs-promises-watch-iterator (3)
  • sequential/test-gc-http-client (2)
  • wpt/test-streams (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-02.md and the linked node-test-pull-request builds 69400–69498 to inspect the listed failures. Review the unchecked progress items and their failure details; done means the relevant CI failures are addressed and the affected checks no longer reproduce.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.