nodejs / nodejs/reliability

CI Reliability 2026-08-10

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-08-10 00:13 2 21 17 4 56 22.34%

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

Progress
  • ERROR: Error fetching remote repo 'origin' (5)
  • error: could not apply 61890720c8a... add readme and initial code (4)
  • sh: line 12: [: -gt: unary operator expected (4)
  • Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified. (3)
  • Failed to trigger node-test-commit (3)
  • fatal: No rebase in progress? (3)
  • ERROR: out of memory (2)
  • parallel/test-stream-pipeline-http2 (20)
  • parallel/test-worker-terminate-http2-respond-with-file (15)
  • parallel/test-sqlite-backup (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-esm-code-cache (2)
  • sea/test-single-executable-application-exec-argv (2)
  • sea/test-single-executable-application-exec-argv-empty (2)
  • sea/test-single-executable-application-exec-argv-extension-cli (2)
  • sequential/test-watch-mode-restart-esm-loading-error (2)
  • wpt/test-timers (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-10.md and the linked node-test-pull-request jobs, using the listed failure messages and test names to group failures. Review how the report was generated with ncu-ci walk pr --stats=true --markdown reports/2026-08-10.md. Done means the relevant CI failures are investigated and the checked progress items have been resolved or clearly documented.

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
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.