nodejs / nodejs/reliability

CI Reliability 2026-08-05

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-08-05 00:26 10 17 21 15 37 22.67%

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

Progress
  • Unexpected termination of the channel (3)
  • Command "git reset --hard" returned status code 128: (2)
  • Failed to trigger node-test-commit (4)
  • fatal: No rebase in progress? (3)
  • ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (2)
  • fatal: failed to run prune (2)
  • parallel/test-sqlite-backup (5)
  • parallel/test-worker-terminate-http2-respond-with-file (5)
  • sequential/test-watch-mode-restart-esm-loading-error (4)
  • parallel/test-stream-pipeline-http2 (2)
  • test-runner/test-run-watch-cwd-isolation-none (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 CI jobs and the failure details in reports/2026-08-05.md, then choose one unchecked failure from the Progress list to investigate. Reproduce or trace that failure and document a fix or confirmed resolution so the selected checklist item no longer fails.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, node.js, shell
Domain
ci-cd, devops, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.