nodejs / nodejs/reliability

CI Reliability 2026-06-18

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-06-18 00:42 3 23 10 3 61 24.47%

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

Progress
  • Build timed out (after 60 minutes). Marking the build as failed. (3)
  • ERROR: Error fetching remote repo 'origin' (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)
  • addons/worker-addon-exit/test (12)
  • parallel/test-cluster-dgram-reuse (4)
  • parallel/test-fs-utimes-y2K38 (4)
  • parallel/test-runner-watch-mode (4)
  • parallel/test-util-styletext (4)
  • es-module/test-vm-contextified-script-leak (2)
  • parallel/test-debugger-probe-failure-process-exit (2)
  • parallel/test-http2-close-while-writing (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-18.md and the linked node-test-pull-request runs, using the listed failure messages and test names to identify which failures are reproducible. Review the ncu-ci walk pr --stats=true --markdown command output; done means the listed CI failures are investigated and the relevant progress items can be resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
nodejs
Domain
ci-cd, 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.