nodejs / nodejs/reliability

CI Reliability 2026-08-26

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-08-26 00:09 14 9 1 20 56 13.64%

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

Progress
  • ERROR: Error fetching remote repo 'origin' (6)
  • ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (4)
  • fatal: No rebase in progress? (2)
  • node-api/test_sea_addon/test (28)
  • sea/test-build-sea (28)
  • sea/test-build-sea-executable-field (28)
  • sea/test-single-executable-application (28)
  • sea/test-single-executable-application-asset-keys (28)
  • sea/test-single-executable-application-asset-keys-empty (28)
  • sea/test-single-executable-application-assets (28)
  • sea/test-single-executable-application-assets-raw (28)
  • sea/test-single-executable-application-disable-experimental-sea-warning (28)
  • sea/test-single-executable-application-empty (28)
  • sea/test-single-executable-application-esm (28)
  • sea/test-single-executable-application-esm-code-cache (28)
  • sea/test-single-executable-application-exec-argv (28)
  • sea/test-single-executable-application-exec-argv-empty (28)
  • sea/test-single-executable-application-exec-argv-extension-cli (28)
  • sea/test-single-executable-application-exec-argv-extension-env (28)
  • sea/test-single-executable-application-exec-argv-extension-none (28)
  • sea/test-single-executable-application-inspect (28)
  • sea/test-single-executable-application-inspect-in-sea-flags (28)
  • sea/test-single-executable-application-snapshot (28)
  • sea/test-single-executable-application-snapshot-and-code-cache (28)
  • sea/test-single-executable-application-snapshot-worker (28)
  • sea/test-single-executable-application-use-code-cache (28)
  • parallel/test-fastutf8stream-destroy (4)
  • parallel/test-fastutf8stream-reopen (4)
  • parallel/test-inspect-async-hook-setup-at-inspect (4)
  • sequential/test-debugger-pid (4)
  • parallel/test-debugger-extract-function-name (2)
  • parallel/test-stream-pipeline-http2 (2)
  • test-runner/test-run-watch-cwd-isolation-none (2)
  • test-runner/test-run-watch-cwd-isolation-none-argv (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 reports/2026-08-26.md and the Jenkins failures from builds 76379 through 76473. Review the listed remote-repository, JUnit-report, rebase, SEA, and test failures to determine their causes. Done means the listed recurring failures are resolved and the affected CI runs no longer fail.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.