nodejs / nodejs/reliability

CI Reliability 2026-04-29

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-04-29 00:29 2 18 19 1 60 18.56%

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

Progress
  • ERROR: Error fetching remote repo 'origin' (5)
  • fatal: No rebase in progress? (6)
  • fatal: no rebase in progress (4)
  • Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified. (2)
  • Failed to trigger fanned build (2)
  • parallel/test-sqlite-database-sync (15)
  • parallel/test-process-finalization (7)
  • parallel/test-runner-watch-mode (4)
  • sequential/test-debugger-pid (4)
  • sea/test-build-sea (3)
  • sea/test-build-sea-custom-argv0 (3)
  • sea/test-build-sea-executable-field (3)
  • sea/test-build-sea-missing-output (3)
  • sea/test-single-executable-application-asset-keys (3)
  • sea/test-single-executable-application-asset-keys-empty (3)
  • sea/test-single-executable-application-assets (3)
  • sea/test-single-executable-application-assets-raw (3)
  • sea/test-single-executable-application-disable-experimental-sea-warning (3)
  • sea/test-single-executable-application-empty (3)
  • sea/test-single-executable-application-esm (3)
  • sea/test-single-executable-application-esm-code-cache (3)
  • sea/test-single-executable-application-exec-argv (3)
  • sea/test-single-executable-application-exec-argv-empty (3)
  • sea/test-single-executable-application-exec-argv-extension-cli (3)
  • sequential/test-performance-eventloopdelay (3)
  • test-runner/test-run-watch-repeatedly (3)
  • test-runner/test-run-watch-run-duration (3)
  • wpt/test-hr-time (3)
  • parallel/test-http2-close-while-writing (2)
  • sea/test-build-sea-already-exists (2)
  • sea/test-single-executable-application-exec-argv-extension-env (2)
  • sea/test-single-executable-application-exec-argv-extension-none (2)
  • sea/test-single-executable-application-snapshot (2)
  • test-runner/test-run-watch-dependency-repeatedly (2)
  • test-runner/test-run-watch-emit-restarted (2)
  • test-runner/test-run-watch-without-file (2)
  • wasi/test-wasi-pthread (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-04-29.md and the Jenkins job range node-test-pull-request/72907 through 73003, using the listed ncu-ci walk pr command to review failure details. Trace one or more unchecked failures, including the named Node.js tests, and consider the work done when the recurring failures are addressed and the progress checklist is updated.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, shell
Domain
ci-cd, testing-qa
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.