nodejs / nodejs/reliability

CI Reliability 2025-02-13

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2025-02-13 00:09 7 15 12 18 48 20.00%

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

Progress
  • Build timed out (after 30 minutes). Marking the build as failed. (5)
  • Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 2228979, exit value: 1 (2)
  • ERROR: Error fetching remote repo 'origin' (2)
  • sh: line 9: [: -gt: unary operator expected (5)
  • fatal: No rebase in progress? (2)
  • fatal: detected dubious ownership in repository at 'C:/workspace/node-test-binary-windows-native-suites/build' (2)
  • parallel/test-assert-fail (10)
  • parallel/test-runner-run-watch (7)
  • parallel/test-file-write-stream4 (5)
  • parallel/test-net-write-fully-async-buffer (4)
  • parallel/test-net-write-fully-async-hex-string (4)
  • benchmark/test-benchmark-http2 (3)
  • sequential/test-perf-hooks (3)
  • wpt/test-compression (3)
  • parallel/test-runner-output (2)
  • sequential/test-vm-timeout-escape-promise-module-2 (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 the linked CI job range and the generated report at reports/2025-02-13.md, then group the listed infrastructure and Node.js test failures by cause. Reproduce the affected jobs or tests and determine which failures remain actionable; done means the reported recurring CI failures are resolved or tracked with evidence.

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.