nodejs / nodejs/reliability

CI Reliability 2024-12-18

Open
#1,061 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/63993 to node-test-pull-request/64079 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-12-18.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2024-12-18 00:10 10 15 15 10 50 18.75%

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

Progress
  • sequential/test-http-server-request-timeouts-mixed (12)
  • parallel/test-watch-file-shared-dependency (10)
  • parallel/test-abortsignal-drop-settled-signals (8)
  • parallel/test-file-write-stream4 (4)
  • parallel/test-module-loading-globalpaths (4)
  • parallel/test-net-write-fully-async-buffer (4)
  • parallel/test-child-process-fork-exec-path (3)
  • parallel/test-http-chunk-problem (3)
  • parallel/test-stream-readable-unpipe-resume (3)
  • parallel/test-find-package-json (2)
  • pummel/test-hash-seed (2)
  • sequential/test-worker-prof (2)
  • fatal: No rebase in progress? (4)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
  • fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository (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-12-18.md and the linked CI runs, using the listed test names to identify recurring failures. Review the generated report from ncu-ci walk pr --stats=true --markdown reports/2024-12-18.md; done means the listed CI failures and configuration errors are resolved or otherwise accounted for.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, shell
Domain
ci-cd, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.