CI Reliability 2026-03-10
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/71547 to node-test-pull-request/71646 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-03-10.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-03-10 00:13 | 0 | 19 | 20 | 4 | 57 | 19.79% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-03-10.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(2) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
ERROR: fetch failed(2) -
fatal: No rebase in progress?(2) -
sh: line 12: [: -gt: unary operator expected(2) -
parallel/test-debugger-heap-profiler(5) -
parallel/test-inspector-exit-worker-in-wait-for-connection(4) -
sequential/test-performance-eventloopdelay(4) -
test-runner/test-run-watch-run-duration(4) -
parallel/test-blob(3) -
parallel/test-http2-compat-serverresponse-createpushresponse(3) -
parallel/test-http2-compat-serverresponse-writehead(3) -
parallel/test-zlib-brotli-16GB(3) -
async-hooks/test-httpparser-reuse(2) -
client-proxy/test-http-proxy-fetch(2) -
client-proxy/test-https-proxy-request-malformed-response(2) -
client-proxy/test-https-proxy-request-tunnel-timeout-agent(2) -
client-proxy/test-use-env-proxy-precedence(2) -
es-module/test-esm-type-field-errors(2) -
es-module/test-vm-contextified-script-leak(2) -
parallel/test-async-hooks-execution-async-resource-await(2) -
parallel/test-cluster-fork-stdio(2) -
parallel/test-domain-error-types(2) -
parallel/test-fs-watch-recursive-delete(2) -
parallel/test-http-server-options-highwatermark(2) -
parallel/test-http2-close-while-writing(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-max-headers-count(2) -
parallel/test-net-connect-reset-after-destroy(2) -
parallel/test-net-dns-lookup(2) -
parallel/test-net-socket-write-after-close(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-runner-run(2) -
parallel/test-timers-socket-timeout-removes-other-socket-unref-timer(2) -
parallel/test-tls-set-default-ca-certificates-reset-fetch(2) -
sea/test-build-sea(2) -
sea/test-build-sea-already-exists(2) -
sea/test-build-sea-custom-argv0(2) -
sea/test-build-sea-executable-field(2) -
sea/test-build-sea-missing-output(2) -
sea/test-single-executable-application-asset-keys(2) -
sea/test-single-executable-application-asset-keys-empty(2) -
sea/test-single-executable-application-assets-raw(2) -
sea/test-single-executable-application-disable-experimental-sea-warning(2) -
sea/test-single-executable-application-empty(2) -
sea/test-single-executable-application-esm(2) -
sea/test-single-executable-application-exec-argv(2) -
sea/test-single-executable-application-exec-argv-empty(2) -
sea/test-single-executable-application-exec-argv-extension-cli(2) -
sea/test-single-executable-application-exec-argv-extension-env(2) -
sea/test-single-executable-application-inspect(2) -
sea/test-single-executable-application-inspect-in-sea-flags(2) -
sea/test-single-executable-application-snapshot(2) -
sea/test-single-executable-application-snapshot-worker(2) -
sequential/test-http-keepalive-maxsockets(2) -
sequential/test-net-reconnect-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-emit-restarted(2) -
test-runner/test-run-watch-repeatedly(2) -
test-runner/test-run-watch-without-file(2) -
wasi/test-wasi-poll(2) -
wpt/test-hr-time(2) -
wpt/test-webcrypto(2)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the generated report at reports/2026-03-10.md and the linked node-test-pull-request jobs, using the listed repeated failures as the initial investigation targets. Review how ncu-ci walk pr --stats=true --markdown produces the report, then determine which failures are actionable and what evidence shows the corresponding CI failures have been resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100