nodejs / nodejs/reliability

CI Reliability 2026-07-19

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-07-19 00:25 0 21 16 3 60 21.65%

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

Progress
  • fatal: No rebase in progress? (10)
  • error: could not apply 61890720c8a... add readme and initial code (5)
  • sh: line 12: [: -gt: unary operator expected (5)
  • ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (2)
  • parallel/test-process-finalization (11)
  • sequential/test-debugger-pid (6)
  • parallel/test-sqlite-backup (4)
  • sea/test-single-executable-application (4)
  • parallel/test-debugger-probe-failure-process-exit (2)
  • parallel/test-inspector-exit-worker-in-wait-for-connection2 (2)
  • parallel/test-npm-install (2)
  • parallel/test-runner-run-watch (2)
  • sequential/test-performance-eventloopdelay (2)
  • sequential/test-watch-mode-restart-esm-loading-error (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-07-19.md failure details for node-test-pull-request builds 74786 through 74884. Review the listed Progress failures, including the rebase errors, missing JUnit reports, and named Node.js tests, to determine which failure is actionable. Done means the selected recurring failure is resolved and the affected CI runs no longer report it.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, shell
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.