nodejs / nodejs/reliability

CI Reliability 2025-01-11

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-01-11 00:10 1 14 25 6 54 15.05%

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

Progress
  • sequential/test-http-server-request-timeouts-mixed (11)
  • parallel/test-file-write-stream4 (5)
  • parallel/test-net-write-fully-async-hex-string (5)
  • parallel/test-buffer-tostring-rangeerror (3)
  • parallel/test-net-write-fully-async-buffer (3)
  • sequential/test-performance-eventloopdelay (3)
  • sequential/test-worker-prof (3)
  • es-module/test-wasm-web-api (2)
  • parallel/test-module-loading-globalpaths (2)
  • pummel/test-hash-seed (2)
  • Failed to create a temp file on /Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64 (2)
  • ERROR: Error fetching remote repo 'origin' (3)
  • fatal: No rebase in progress? (5)
  • Error: - process terminated with status 1, expected 0 (3)

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/2025-01-11.md at the linked reliability report and review the failures listed in the issue, beginning with the repeated test names and CI errors. Trace each failure to its relevant Node.js test or CI setup; done means the listed recurring failures are diagnosed and addressed, with the affected jobs returning to green.

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.