nodejs / nodejs/reliability

CI Reliability 2025-02-03

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-02-03 00:10 2 19 8 19 52 24.05%

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

Progress
  • fatal: No rebase in progress? (6)
  • fatal error: Killed signal terminated program cc1plus (4)
  • Error: list index out of range (2)
  • parallel/test-assert-fail (13)
  • parallel/test-runner-run-watch (10)
  • parallel/test-net-write-fully-async-buffer (9)
  • parallel/test-buffer-tostring-rangeerror (5)
  • parallel/test-pipe-file-to-http (5)
  • parallel/test-file-write-stream4 (4)
  • parallel/test-runner-output (4)
  • sequential/test-perf-hooks (4)
  • wpt/test-compression (4)
  • wpt/test-url (4)
  • parallel/test-net-write-fully-async-hex-string (3)
  • parallel/test-stream-readable-unpipe-resume (3)
  • parallel/test-child-process-bad-stdio (2)
  • parallel/test-process-threadCpuUsage-worker-threads (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-02-03.md and the linked node-test-pull-request runs to inspect the listed failures. Use the generated ncu-ci report and the unchecked Progress entries to identify which failures remain; done means the relevant CI failures have been addressed and the progress list updated.

Written by the indexing model from the issue text.

Assessment

Tech stack
nodejs, 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
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.