nodejs / nodejs/reliability

CI Reliability 2026-06-08

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-06-08 00:39 0 23 15 2 60 23.47%

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

Progress
  • ERROR: Error fetching remote repo 'origin' (5)
  • Failed to trigger fanned build (9)
  • fatal: No rebase in progress? (3)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
  • Error: Timed out waiting for restart (2)
  • sea/test-build-sea (5)
  • sea/test-build-sea-already-exists (5)
  • sea/test-build-sea-custom-argv0 (5)
  • sea/test-build-sea-executable-field (5)
  • sea/test-build-sea-missing-output (5)
  • sea/test-single-executable-application-asset-keys (5)
  • sea/test-single-executable-application-asset-keys-empty (5)
  • sea/test-single-executable-application-exec-argv-extension-cli (5)
  • sea/test-single-executable-application-exec-argv-extension-env (5)
  • sea/test-single-executable-application-exec-argv-extension-none (5)
  • sea/test-single-executable-application-inspect (5)
  • sea/test-single-executable-application-assets (4)
  • sea/test-single-executable-application-assets-raw (4)
  • sea/test-single-executable-application-exec-argv (4)
  • sea/test-single-executable-application-snapshot-and-code-cache (4)
  • addons/worker-addon-exit/test (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-empty (3)
  • sea/test-single-executable-application-snapshot (3)
  • parallel/test-cluster-dgram-reuse (2)
  • parallel/test-debugger-probe-failure-process-exit (2)
  • parallel/test-fs-watch-recursive-delete (2)
  • parallel/test-http-server-consumed-timeout (2)
  • sea/test-single-executable-application-inspect-in-sea-flags (2)
  • sea/test-single-executable-application-snapshot-worker (2)
  • sea/test-single-executable-application-use-code-cache (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-06-08.md and the linked node-test-pull-request jobs, then inspect the failures generated by ncu-ci walk pr --stats=true --markdown reports/2026-06-08.md. The issue spans repository, build, test, and SEA failures rather than naming one entry point. Done means addressing the recurring failure categories and completing the listed progress items.

Written by the indexing model from the issue text.

Assessment

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