nodejs / nodejs/reliability

CI Reliability 2026-08-23

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-08-23 00:08 30 17 7 3 43 25.37%

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

Progress
  • Build timed out (after 30 minutes). Marking the build as failed. (10)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (2)
  • Command "git reset --hard" returned status code 128: (2)
  • Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified. (3)
  • Failed to trigger node-test-commit (3)
  • Failed to trigger sub builds (3)
  • ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (2)
  • error: could not apply 61890720c8a... add readme and initial code (2)
  • fatal: No rebase in progress? (2)
  • parallel/test-fastutf8stream-reopen (8)
  • sea/test-single-executable-application-asset-keys-empty (8)
  • sea/test-single-executable-application-disable-experimental-sea-warning (8)
  • sea/test-single-executable-application-exec-argv-extension-env (8)
  • sea/test-single-executable-application-inspect (8)
  • sea/test-single-executable-application (5)
  • node-api/test_sea_addon/test (4)
  • parallel/test-runner-run-watch (4)
  • parallel/test-stream-pipeline-http2 (4)
  • sea/test-build-sea (4)
  • sea/test-build-sea-executable-field (4)
  • sea/test-single-executable-application-asset-keys (4)
  • sea/test-single-executable-application-assets (4)
  • sea/test-single-executable-application-assets-raw (4)
  • sea/test-single-executable-application-empty (4)
  • sea/test-single-executable-application-esm (4)
  • sea/test-single-executable-application-esm-code-cache (4)
  • sea/test-single-executable-application-exec-argv (4)
  • sea/test-single-executable-application-exec-argv-empty (4)
  • sea/test-single-executable-application-exec-argv-extension-cli (4)
  • sea/test-single-executable-application-exec-argv-extension-none (4)
  • sea/test-single-executable-application-inspect-in-sea-flags (4)
  • sea/test-single-executable-application-snapshot (4)
  • sea/test-single-executable-application-snapshot-and-code-cache (4)
  • sea/test-single-executable-application-snapshot-worker (4)
  • sea/test-single-executable-application-use-code-cache (4)
  • parallel/test-runner-watch-mode (3)
  • parallel/test-fastutf8stream-destroy (2)
  • parallel/test-inspect-async-hook-setup-at-inspect (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-08-23.md and the linked node-test-pull-request builds, using the generated ncu-ci walk pr --stats=true --markdown reports/2026-08-23.md report to group recurring failures. Review the listed timeout, trigger, Git, build, and test failures first; done means the relevant CI failure causes are addressed and the affected PR checks become reliable.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, 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.