CI Reliability 2026-09-10
Open
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/77096 to node-test-pull-request/77224 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-09-10.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-09-10 00:15 | 1 | 5 | 14 | 36 | 44 | 7.94% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-09-10.md to see failure details
Progress
-
parallel/test-inspector-multisession-ws(8) -
parallel/test-bench-stream(6) -
client-proxy/test-https-proxy-request-invalid-char-in-url(5) -
parallel/test-bench-cli(4) -
sea/test-single-executable-application-empty(3) -
node-api/test_worker_buffer_callback/test-free-called(2) -
parallel/test-debugger-extract-function-name(2) -
parallel/test-external-memory-reasonable-size(2) -
parallel/test-fs-stat-bigint(2) -
ERROR: Error fetching remote repo 'origin'(3) -
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(9) -
Failed to trigger fanned build(6) -
fatal: No rebase in progress?(3) -
ERROR: All mapping items must start at the same column at line 7, column 1:(2) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(2)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with reports/2026-09-10.md and the linked node-test-pull-request builds, using the listed test names and CI errors to group the failures. Run or inspect the affected tests and build steps first; done means the reported failures are addressed and the reliability report no longer shows them recurring.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, devops, testing
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100