nodejs / nodejs/reliability

CI Reliability 2026-04-04

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-04-04 00:18 0 17 7 6 70 18.09%

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

Progress
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (3)
  • fatal: No rebase in progress? (5)
  • Failed to trigger node-test-commit (3)
  • Failed to trigger sub builds (3)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
  • ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ... (2)
  • ERROR: out of memory (2)
  • sh: line 12: [: -gt: unary operator expected (2)
  • sh: line 1: 429:: command not found (2)
  • wpt/test-wasm-jsapi (4)
  • parallel/test-http2-client-rststream-before-connect (2)
  • parallel/test-http2-close-while-writing (2)
  • parallel/test-http2-server-push-stream (2)
  • parallel/test-inspector-exit-worker-in-wait-for-connection (2)
  • parallel/test-net-socket-reset-send (2)
  • parallel/test-net-socket-tos (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-04-04.md and the linked node-test-pull-request jobs, using the listed failure messages to group the recurring CI failures. Review the ncu-ci walk report and corresponding job logs; done means the listed recurring failures have been investigated and the progress items are resolved or clearly tracked.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.