nodejs / nodejs/reliability

CI Reliability 2024-12-04

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2024-12-04 00:11 7 11 21 1 60 11.96%

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

Progress
  • ERROR: Error fetching remote repo 'origin' (4)
  • fatal: No rebase in progress? (3)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
  • Error: - process terminated with status 1, expected 0 (2)
  • fatal error: 'ranges' file not found (2)
  • sequential/test-http-server-request-timeouts-mixed (15)
  • parallel/test-file-write-stream4 (5)
  • parallel/test-net-write-fully-async-buffer (2)
  • parallel/test-runner-run (2)
  • parallel/test-stream-readable-unpipe-resume (2)
  • parallel/test-timers-immediate-queue (2)
  • parallel/test-watch-file-shared-dependency (2)
  • sequential/test-tls-session-timeout (2)
  • wpt/test-compression (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 runs and the 2024-12-04.md report in the nodejs/reliability repository, then group the listed failures by error or test. Investigate the affected CI jobs and tests, and consider the work done when the listed recurring failures are resolved or otherwise accounted for and the CI results improve.

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
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.