nodejs / nodejs/reliability

CI Reliability 2025-06-11

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-06-11 00:11 1 6 39 1 53 6.12%

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

Progress
  • parallel/test-buffer-tostring-range (9)
  • sequential/test-performance-eventloopdelay (7)
  • parallel/test-runner-run-watch (3)
  • sequential/test-perf-hooks (3)
  • sequential/test-tls-session-timeout (3)
  • parallel/test-config-file (2)
  • parallel/test-debugger-break (2)
  • parallel/test-net-autoselectfamily (2)
  • parallel/test-stream-readable-to-web (2)
  • parallel/test-without-async-context-frame (2)
  • wpt/test-streams (2)
  • wpt/test-wasm-webapi (2)
  • wpt/test-webcrypto (2)
  • Build timed out (after 30 minutes). Marking the build as failed. (8)
  • Failed to trigger node-test-commit (3)
  • fatal error: Killed signal terminated program cc1plus (2)
  • fatal: No rebase in progress? (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 by reading reports/2025-06-11.md and inspecting the linked node-test-pull-request jobs for the listed recurring failures. Reproduce the relevant failures and trace each one to its cause; the work is done when the listed CI failures are resolved and the progress checklist can be updated.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.