nodejs / nodejs/reliability

CI Reliability 2025-09-10

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-09-10 00:10 0 27 20 3 50 27.84%

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

Progress
  • parallel/test-without-async-context-frame (5)
  • sequential/test-single-executable-application-exec-argv-extension-cli (5)
  • sequential/test-single-executable-application-exec-argv-extension-env (5)
  • sequential/test-single-executable-application-exec-argv-extension-none (5)
  • wpt/test-streams (5)
  • parallel/test-runner-run-watch (4)
  • client-proxy/test-https-proxy-request-invalid-char-in-url (3)
  • sequential/test-performance-eventloopdelay (3)
  • async-hooks/test-emit-before-on-destroyed (2)
  • parallel/test-zlib-brotli-16GB (2)
  • sequential/test-single-executable-application (2)
  • sequential/test-single-executable-application-asset-keys (2)
  • sequential/test-single-executable-application-asset-keys-empty (2)
  • sequential/test-single-executable-application-assets (2)
  • sequential/test-single-executable-application-assets-raw (2)
  • sequential/test-single-executable-application-disable-experimental-sea-warning (2)
  • sequential/test-single-executable-application-exec-argv (2)
  • sequential/test-single-executable-application-exec-argv-empty (2)
  • sequential/test-single-executable-application-inspect (2)
  • sequential/test-single-executable-application-inspect-in-sea-flags (2)
  • sequential/test-single-executable-application-snapshot (2)
  • sequential/test-single-executable-application-snapshot-and-code-cache (2)
  • sequential/test-single-executable-application-snapshot-worker (2)
  • sequential/test-single-executable-application-use-code-cache (2)
  • Failed to create a temp file on /home/iojs/build/workspace/node (5)
  • fatal: No rebase in progress? (4)
  • fatal error: Killed signal terminated program cc1plus (3)
  • fatal error: ld terminated with signal 9 [Killed] (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 the linked CI job range and the generated report at reports/2025-09-10.md, then group the repeated failures by affected test. Review the listed Node.js tests and build errors to identify a narrowly scoped cause; done means the selected recurring failure is resolved and its CI runs reliably.

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.