nodejs / nodejs/reliability

CI Reliability 2026-06-14

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-06-14 00:39 4 23 18 3 52 24.73%

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

Progress
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (2)
  • error: could not apply 61890720c8a... add readme and initial code (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: no rebase in progress (2)
  • Unexpected token '<', " (2)
  • addons/worker-addon-exit/test (7)
  • parallel/test-debugger-probe-failure-hang-during-evaluate (2)
  • parallel/test-http-server-consumed-timeout (2)
  • test-runner/test-run-watch-emit-restarted (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 reports/2026-06-14.md and the linked node-test-pull-request runs, using the listed failure signatures to group the failures. Inspect the generated details for each recurring failure and verify that the affected CI jobs no longer reproduce them; the issue is done when the listed reliability problems are resolved.

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.