nodejs / nodejs/reliability

CI Reliability 2024-10-22

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2024-10-22 00:09 1 16 32 2 49 16.49%

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

Progress
  • sequential/test-http-server-request-timeouts-mixed (13)
  • parallel/test-net-write-fully-async-buffer (6)
  • parallel/test-module-loading-globalpaths (5)
  • parallel/test-file-write-stream4 (3)
  • parallel/test-stream-readable-unpipe-resume (3)
  • parallel/test-async-context-frame (2)
  • parallel/test-buffer-tostring-rangeerror (2)
  • parallel/test-child-process-fork-exec-path (2)
  • parallel/test-http2-large-write-multiple-requests (2)
  • wpt/test-compression (2)
  • Error: invalid syntax (7)
  • ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? (3)
  • fatal: No rebase in progress? (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-22.md and the Jenkins range from node-test-pull-request/63145 to 63240. Review the listed test and CI failures, then investigate them individually. Done means the tracked failures are addressed and the CI reliability report no longer shows them as unresolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, shell
Domain
ci-cd, devops, testing-qa
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.