nodejs / nodejs/reliability

CI Reliability 2024-12-02

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2024-12-02 00:11 0 11 23 1 65 11.11%

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

Progress
  • sequential/test-http-server-request-timeouts-mixed (14)
  • parallel/test-file-write-stream4 (5)
  • parallel/test-watch-file-shared-dependency (5)
  • parallel/test-net-write-fully-async-buffer (3)
  • parallel/test-stream-readable-unpipe-resume (3)
  • wpt/test-compression (3)
  • parallel/test-runner-run (2)
  • parallel/test-watch-mode-files_watcher (2)
  • sequential/test-tls-session-timeout (2)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (2)
  • Build timed out (after 60 minutes). Marking the build as failed. (2)
  • ERROR: Error fetching remote repo 'origin' (6)
  • fatal: No rebase in progress? (4)
  • fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository (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)

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-02.md and the linked node-test-pull-request jobs to review the failure details. Compare the listed test and infrastructure failures, beginning with sequential/test-http-server-request-timeouts-mixed and parallel/test-file-write-stream4. Done means the applicable failures are investigated and the progress items are resolved or updated with their status.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
ci-cd
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.