nodejs / nodejs/reliability

CI Reliability 2024-12-30

Open
#1,073 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/64158 to node-test-pull-request/64257 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-12-30.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2024-12-30 00:10 0 9 24 0 67 9.00%

Open https://github.com/nodejs/reliability/blob/main/reports/2024-12-30.md to see failure details

Progress
  • ERROR: Error fetching remote repo 'origin' (3)
  • fatal: No rebase in progress? (3)
  • Failed to trigger sub builds (2)
  • error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj] (2)
  • sequential/test-http-server-request-timeouts-mixed (13)
  • es-module/test-wasm-web-api (5)
  • parallel/test-file-write-stream4 (5)
  • sequential/test-worker-prof (5)
  • parallel/test-buffer-tostring-rangeerror (2)
  • parallel/test-fs-stat-bigint (2)
  • parallel/test-http-chunk-problem (2)
  • parallel/test-net-write-fully-async-buffer (2)
  • parallel/test-net-write-fully-async-hex-string (2)
  • parallel/test-stream-readable-unpipe-resume (2)
  • parallel/test-watch-file-shared-dependency (2)
  • pummel/test-heapdump-http2 (2)
  • sequential/test-perf-hooks (2)
  • sequential/test-tls-session-timeout (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/2024-12-30.md and the linked node-test-pull-request jobs. Review the listed CI errors and named tests, beginning with the failures occurring most often; the progress checklist indicates what must be investigated and tracked to completion.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.