nodejs / nodejs/reliability

CI Reliability 2024-11-06

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2024-11-06 00:09 5 10 30 2 53 10.75%

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

Progress
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (2)
  • ERROR: Error fetching remote repo 'origin' (4)
  • fatal: No rebase in progress? (6)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (3)
  • ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (3)
  • ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (2)
  • ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? (2)
  • Error: list index out of range (2)
  • fatal error: Killed signal terminated program cc1plus (2)
  • fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository (2)
  • sequential/test-http-server-request-timeouts-mixed (11)
  • parallel/test-net-write-fully-async-buffer (5)
  • parallel/test-file-write-stream4 (4)
  • benchmark/test-benchmark-http2 (2)
  • parallel/test-stream-readable-unpipe-resume (2)
  • parallel/test-util-getcallsites (2)
  • parallel/test-without-async-context-frame (2)
  • sequential/test-tls-session-timeout (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 Jenkins job range and the generated report at reports/2024-11-06.md. Review the listed failure signatures and test names, then trace each recurring failure to its relevant CI or test context. Done means the recurring failures in the progress checklist have been investigated and addressed, with subsequent CI runs confirming improved reliability.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, nodejs, shell
Domain
ci-cd, devops, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.