nodejs / nodejs/reliability

CI Reliability 2026-05-18

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-05-18 00:33 1 22 16 5 56 23.40%

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

Progress
  • ERROR: Error fetching remote repo 'origin' (4)
  • sh: line 12: [: -gt: unary operator expected (11)
  • fatal: No rebase in progress? (9)
  • ERROR: out of memory (3)
  • sequential/test-watch-mode-worker (8)
  • parallel/test-http2-close-while-writing (6)
  • test-runner/test-run-watch-repeatedly (3)
  • parallel/test-worker-nearheaplimit-deadlock (2)
  • sequential/test-performance-eventloopdelay (2)
  • sequential/test-watch-mode-restart-esm-loading-error (2)
  • test-runner/test-run-watch-dependency-repeatedly (2)
  • test-runner/test-run-watch-without-file (2)
  • wpt/test-webcrypto (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 reliability report at reports/2026-05-18.md and the CI job range node-test-pull-request/73420 through 73513. Review the listed error groups and failing tests, then use the referenced ncu-ci walk pr command and job logs to investigate each recurring failure. Done means the identified CI failures are addressed and the affected checks become reliable.

Written by the indexing model from the issue text.

Assessment

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