nodejs / nodejs/reliability

CI Reliability 2025-08-21

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-08-21 00:10 1 0 35 2 62 0.00%

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

Progress
  • sequential/test-single-executable-application (8)
  • sequential/test-single-executable-application-assets (8)
  • sequential/test-single-executable-application-assets-raw (8)
  • sequential/test-single-executable-application-disable-experimental-sea-warning (8)
  • sequential/test-single-executable-application-exec-argv (8)
  • sequential/test-single-executable-application-exec-argv-empty (8)
  • sequential/test-single-executable-application-snapshot (8)
  • sequential/test-single-executable-application-snapshot-and-code-cache (8)
  • sequential/test-single-executable-application-snapshot-worker (8)
  • sequential/test-single-executable-application-use-code-cache (8)
  • parallel/test-runner-mock-timers-scheduler (7)
  • parallel/test-http-keep-alive-empty-line (6)
  • parallel/test-http-outgoing-end-cork (5)
  • sequential/test-performance-eventloopdelay (3)
  • parallel/test-debugger-break (2)
  • parallel/test-debugger-random-port (2)
  • parallel/test-fs-cp-sync-preserve-timestamps-readonly (2)
  • parallel/test-http-client-close-with-default-agent (2)
  • parallel/test-performance-eventlooputil (2)
  • parallel/test-runner-run (2)
  • parallel/test-worker-nearheaplimit-deadlock (2)
  • wasi/test-wasi (2)
  • wpt/test-streams (2)
  • wpt/test-webcrypto (2)
  • Build timed out (after 30 minutes). Marking the build as failed. (8)
  • fatal: No rebase in progress? (4)

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-08-21.md and the linked CI runs, using the listed failing test names and build errors as entry points. Determine the causes of the repeated failures and address them until the affected checks no longer fail; completion is reflected by clearing the progress list and restoring a green CI run.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, shell
Domain
ci-cd, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.