nodejs / nodejs/reliability

CI Reliability 2026-03-11

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-03-11 00:14 2 21 13 4 60 22.34%

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

Progress
  • ERROR: Error fetching remote repo 'origin' (2)
  • fatal: No rebase in progress? (4)
  • ERROR: fetch failed (2)
  • sh: line 12: [: -gt: unary operator expected (2)
  • parallel/test-debugger-heap-profiler (8)
  • parallel/test-inspector-exit-worker-in-wait-for-connection (4)
  • sequential/test-performance-eventloopdelay (4)
  • test-runner/test-run-watch-run-duration (4)
  • es-module/test-vm-contextified-script-leak (3)
  • parallel/test-blob (3)
  • parallel/test-http2-compat-serverresponse-createpushresponse (3)
  • parallel/test-http2-compat-serverresponse-writehead (3)
  • async-hooks/test-httpparser-reuse (2)
  • client-proxy/test-http-proxy-fetch (2)
  • client-proxy/test-http-set-global-proxy-from-env-override-http (2)
  • client-proxy/test-https-proxy-request-malformed-response (2)
  • client-proxy/test-https-proxy-request-tunnel-timeout-agent (2)
  • client-proxy/test-https-request-proxy-post (2)
  • client-proxy/test-use-env-proxy-precedence (2)
  • es-module/test-esm-type-field-errors (2)
  • parallel/test-async-hooks-execution-async-resource-await (2)
  • parallel/test-heapsnapshot-near-heap-limit-worker (2)
  • parallel/test-http-chunked-smuggling (2)
  • parallel/test-http-pipeline-assertionerror-finish (2)
  • parallel/test-http-server-options-highwatermark (2)
  • parallel/test-http2-close-while-writing (2)
  • parallel/test-http2-compat-serverrequest-end (2)
  • parallel/test-http2-compat-write-head-destroyed (2)
  • parallel/test-http2-date-header (2)
  • parallel/test-http2-goaway-opaquedata (2)
  • parallel/test-http2-misbehaving-multiplex (2)
  • parallel/test-http2-multi-content-length (2)
  • parallel/test-http2-no-more-streams (2)
  • parallel/test-http2-perf_hooks (2)
  • parallel/test-http2-raw-headers (2)
  • parallel/test-http2-request-remove-connect-listener (2)
  • parallel/test-http2-single-headers-validation (2)
  • parallel/test-http2-trailers (2)
  • parallel/test-https-agent-additional-options (2)
  • parallel/test-https-client-renegotiation-limit (2)
  • parallel/test-https-max-headers-count (2)
  • parallel/test-inspector-not-blocked-on-idle (2)
  • parallel/test-net-after-close (2)
  • parallel/test-net-bytes-read (2)
  • parallel/test-net-bytes-stats (2)
  • parallel/test-net-connect-reset-after-destroy (2)
  • parallel/test-net-connect-reset-until-connected (2)
  • parallel/test-net-dns-lookup (2)
  • parallel/test-net-server-max-connections (2)
  • parallel/test-net-socket-write-after-close (2)
  • parallel/test-net-stream (2)
  • parallel/test-net-write-fully-async-buffer (2)
  • parallel/test-perf-hooks-eventlooputilization (2)
  • parallel/test-process-getactiveresources-track-active-handles (2)
  • parallel/test-snapshot-reproducible (2)
  • parallel/test-timers-socket-timeout-removes-other-socket-unref-timer (2)
  • parallel/test-tls-set-default-ca-certificates-reset-fetch (2)
  • parallel/test-tls-use-after-free-regression (2)
  • sequential/test-http-keepalive-maxsockets (2)
  • sequential/test-net-reconnect-error (2)
  • sequential/test-watch-mode-restart-esm-loading-error (2)
  • sequential/test-worker-eventlooputil (2)
  • test-runner/test-run-watch-cwd-isolation-none (2)
  • test-runner/test-run-watch-dependency-repeatedly (2)
  • test-runner/test-run-watch-repeatedly (2)
  • wasi/test-wasi-poll (2)
  • wpt/test-webcrypto (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-03-11.md and the linked CI runs, using the listed failures to identify which errors or tests remain reproducible. Review the corresponding test names, such as parallel/test-debugger-heap-profiler and test-runner/test-run-watch-run-duration. Done means the reported recurring failures have been investigated and the relevant CI 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
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.