nodejs / nodejs/reliability

CI Reliability 2026-09-03

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-09-03 00:16 14 12 23 24 27 19.35%

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

Progress
  • Build timed out (after 30 minutes). Marking the build as failed. (2)
  • ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (3)
  • Failed to trigger node-test-commit (3)
  • parallel/test-http2-bidirectional-write-deadlock (3)
  • client-proxy/test-https-proxy-request-invalid-char-in-url (2)
  • parallel/test-async-context-frame (2)
  • parallel/test-buffer-tostring-rangeerror (2)
  • parallel/test-external-memory-reasonable-size (2)
  • parallel/test-permission-net-udp-handle (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 report at reliability/reports/2026-09-03.md and the CI failures from node-test-pull-request/76813 through 76905. Review the listed timeout, trigger, reporting, and Node.js test failures to identify their causes. Done means the recurring failures listed in the issue are resolved or have clear follow-up work.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
ci-cd, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.