nodejs / nodejs/reliability

CI Reliability 2026-02-25

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-02-25 00:18 0 16 30 7 47 17.20%

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

Progress
  • Build timed out (after 60 minutes). Marking the build as failed. (2)
  • Failed to create a temp file on /home/iojs/build/workspace/node (2)
  • ERROR: Error fetching remote repo 'origin' (4)
  • fatal: No rebase in progress? (4)
  • Failed to trigger sub builds (2)
  • wpt/test-hr-time (5)
  • parallel/test-runner-run-watch (4)
  • sequential/test-performance-eventloopdelay (4)
  • async-hooks/test-emit-before-on-destroyed (3)
  • parallel/test-async-context-frame (3)
  • parallel/test-child-process-fork-exec-path (3)
  • parallel/test-file-write-stream4 (3)
  • parallel/test-http-client-response-domain (3)
  • parallel/test-module-loading-globalpaths (3)
  • parallel/test-promise-reject-callback-exception (3)
  • parallel/test-runner-watch-mode (3)
  • parallel/test-tls-dhe (3)
  • test-runner/test-run-watch-emit-restarted (3)
  • async-hooks/test-improper-order (2)
  • client-proxy/test-https-proxy-request-invalid-char-in-url (2)
  • parallel/test-async-hooks-http-parser-destroy (2)
  • parallel/test-strace-openat-openssl (2)
  • parallel/test-vm-sigint (2)
  • sea/test-build-sea (2)
  • sea/test-build-sea-already-exists (2)
  • sea/test-build-sea-custom-argv0 (2)
  • sea/test-build-sea-executable-field (2)
  • sea/test-build-sea-missing-output (2)
  • sea/test-single-executable-application-asset-keys (2)
  • sea/test-single-executable-application-asset-keys-empty (2)
  • sea/test-single-executable-application-assets (2)
  • sea/test-single-executable-application-assets-raw (2)
  • sea/test-single-executable-application-disable-experimental-sea-warning (2)
  • sea/test-single-executable-application-empty (2)
  • sea/test-single-executable-application-esm (2)
  • sea/test-single-executable-application-exec-argv (2)
  • sea/test-single-executable-application-exec-argv-extension-cli (2)
  • sequential/test-single-executable-application-empty (2)
  • test-runner/test-run-watch-without-file (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-02-25.md and the linked node-test-pull-request builds, using the listed failure messages and test names as the entry points. Review how the failures affect multiple pull requests and use ncu-ci walk pr --stats=true --markdown reports/2026-02-25.md to reproduce the report; done is addressing the relevant recurring CI failures and confirming the affected jobs recover.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, shell
Domain
ci-cd, testing
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.