nodejs / nodejs/reliability

CI Reliability 2024-09-11

Open
#963 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/62166 to node-test-pull-request/62286 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-09-11.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2024-09-11 00:09 11 3 13 40 33 6.12%

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

Progress
  • fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository (6)
  • fatal error: /Library/Developer/CommandLineTools/usr/bin/libtool: can't write to output file (No space left on device) (5)
  • fatal: No rebase in progress? (4)
  • parallel/test-runner-coverage (3)
  • parallel/test-runner-coverage-thresholds (3)
  • parallel/test-runner-output (3)
  • parallel/test-async-context-frame (2)
  • parallel/test-http2-large-write-multiple-requests (2)
  • pummel/test-hash-seed (2)
  • sequential/test-http-keep-alive-large-write (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-09-11.md and the linked node-test-pull-request runs, using the listed failure messages and test names to group the failures. Review the ncu-ci walk pr --stats=true --markdown reports/2024-09-11.md output and trace each repeated failure to its CI or test entry point. Done means the listed failures are addressed and the affected pull requests no longer reproduce them.

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.