nodejs / nodejs/reliability

CI Reliability 2025-01-09

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-01-09 00:10 0 14 22 5 59 14.74%

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

Progress
  • 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' (2)
  • fatal: No rebase in progress? (3)
  • Error: - process terminated with status 1, expected 0 (2)
  • sequential/test-http-server-request-timeouts-mixed (18)
  • parallel/test-net-write-fully-async-hex-string (6)
  • parallel/test-file-write-stream4 (5)
  • parallel/test-net-write-fully-async-buffer (5)
  • parallel/test-module-loading-globalpaths (4)
  • pummel/test-fs-readfile-tostring-fail (3)
  • es-module/test-wasm-web-api (2)
  • parallel/test-buffer-tostring-rangeerror (2)
  • sequential/test-worker-prof (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/2025-01-09.md and the linked node-test-pull-request jobs, then examine the listed failures and test names. Determine which failures are actionable and address their causes; done means the tracked CI failures have been resolved or clearly explained.

Written by the indexing model from the issue text.

Assessment

Tech stack
nodejs, 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.