nodejs / nodejs/reliability

CI Reliability 2026-01-27

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-01-27 00:14 5 14 12 5 64 15.56%

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

Progress
  • fatal: No rebase in progress? (3)
  • Failed to trigger node-test-commit (2)
  • fatal: no rebase in progress (2)
  • parallel/test-repl-programmatic-history (23)
  • parallel/test-inspector-network-http2-compressed (20)
  • sequential/test-watch-mode-restart-esm-loading-error (4)
  • es-module/test-vm-contextified-script-leak (3)
  • sequential/test-performance-eventloopdelay (3)
  • sea/test-build-sea (2)
  • sea/test-build-sea-executable-field (2)
  • sequential/test-single-executable-application-empty (2)
  • test-runner/test-run-watch-repeatedly (2)
  • test-runner/test-run-watch-without-file (2)
  • wpt/test-streams (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-01-27.md failure details and the node-test-pull-request Jenkins runs from 70955 through 71049. Review the listed failures, including the rebase and test-runner entries, to identify which failures remain reproducible. Done means the reported CI failure entries have been addressed and the affected checks no longer fail.

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
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.