nodejs / nodejs/reliability

CI Reliability 2024-10-11

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2024-10-11 00:09 0 18 14 8 60 19.57%

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

Progress
  • node-api/test_threadsafe_function/test (7)
  • sequential/test-http-server-request-timeouts-mixed (7)
  • wpt/test-compression (5)
  • parallel/test-stream-readable-unpipe-resume (4)
  • parallel/test-net-write-fully-async-buffer (3)
  • Build timed out (after 30 minutes). Marking the build as failed. (9)
  • Cannot run program "sh" (in directory "c:\workspace\node-test-binary-windows-js-suites"): CreateProcess error=2, The system cannot find the file specified (5)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (4)
  • ERROR: Error fetching remote repo 'origin' (2)
  • Error: invalid syntax (6)
  • fatal: No rebase in progress? (4)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
  • ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (2)
  • fatal error: Killed signal terminated program cc1plus (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-10-11.md and the linked CI job range, using the listed failures to identify which problems remain reproducible. Review how the report was generated with ncu-ci walk pr --stats=true --markdown reports/2024-10-11.md; done means the selected CI failures are fixed or otherwise resolved and the report's progress is updated.

Written by the indexing model from the issue text.

Assessment

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