[PR #5019] [MERGED] test(update): isolate CLI subprocess deadlines #6737

Closed
opened 2026-11-01 21:42:41 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5019
Author: @XY-code1
Created: 10/18/2026
Status: ✅ Merged
Merged: 10/21/2026
Merged by: @morluto

Base: main ← Head: fix/windows-update-command-timeout


📝 Commits (2)

  • 8d13c83 test(update): isolate CLI command deadlines
  • 894f3e2 Merge origin/main into fix/windows-update-command-timeout

📊 Changes

1 file changed (+4 additions, -1 deletions)

View changed files

📝 tests/process-global/updateMaintenance.test.ts (+4 -1)

📄 Description

Summary

Fixes #4989.

Give the two independent CLI boundary checks independent Vitest deadlines. A delayed --help launch can no longer consume the entire deadline before the removed upgrade --json command is exercised, and a future timeout identifies the affected command in the test title.

Problem and expected behavior

The existing test runs two real CLI subprocesses serially under one 30-second test deadline. Windows qualification recorded one timeout, but the combined test title and deadline did not identify which subprocess was pending. Each subprocess normally finishes in about one second and represents a separate contract.

Each command boundary should receive its own test lifecycle and timeout, while preserving the existing help-output and removed-command assertions.

Change and scope

Split the combined test into two focused cases:

  • exposes update in CLI help
  • rejects the removed upgrade CLI command

No timeout value, retry policy, assertion, subprocess implementation, or runtime behavior changed.

Follow the contribution scope.

Contract and boundary impact

  • Semantic owner and earliest changed stage: Windows process-global CLI test orchestration.
  • Contribution scope fit and linked maintainer decision: ordinary test reliability correction; maintainer scope decision not applicable.
  • CLI and MCP/tool-catalog contract: unchanged.
  • Provider, bridge, target-format, or platform compatibility: unchanged.
  • Evidence, artifact, provenance, or reconstruction contract: unchanged.
  • Target selection, authority, upstream behavior, and cleanup details: unchanged; the same two CLI subprocesses are launched and awaited.
  • Generated metadata, package, or installation impact: none.

Expected effects:

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

  • Tests updated: tests/process-global/updateMaintenance.test.ts.

  • Base evidence: #4989 records the combined test timing out at 30,009 ms on one Windows qualification run. The identical source passed other runs, so the underlying runner stall was not reproduced locally.

  • Modified Windows run: both isolated cases passed, with --help completing in 1,030 ms and removed upgrade --json completing in 993 ms.

  • User-visible CLI/MCP output: not applicable; assertions and runtime behavior are unchanged.

  • Remaining proof gaps: the original intermittent GitHub-hosted runner stall remains unexplained. This change isolates its budget and diagnostic identity rather than claiming to fix a production hang.

  • Observed, derived, and inferred claims remain distinguishable.

  • Artifact identity, source provenance, and failed attempts remain preserved.

  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

Windows x64, Node 24.18.0, npm 11.16.0:

  • npm run test:focused -- tests/process-global/updateMaintenance.test.ts — 28 passed.
  • npm run check:fast — typecheck and lint passed.
  • npm run format:check -- tests/process-global/updateMaintenance.test.ts — all 4,025 matched files passed.
  • git diff --check — passed.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: Windows process-global test executed; no provider or target workflow is affected.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: test-only change; subprocess commands and environment handling are unchanged.

Author readiness

Human owner: @XY-code1

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked.
  • Tests cover the changed test-orchestration behavior.
  • Owning docs, contracts, and generated metadata are unchanged.
  • User-visible CLI/MCP output is not applicable.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/5019 **Author:** [@XY-code1](https://github.com/XY-code1) **Created:** 10/18/2026 **Status:** ✅ Merged **Merged:** 10/21/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/windows-update-command-timeout` --- ### 📝 Commits (2) - [`8d13c83`](https://github.com/morluto/rea/commit/8d13c83777be43278cf6337b4ef677852eb478a3) test(update): isolate CLI command deadlines - [`894f3e2`](https://github.com/morluto/rea/commit/894f3e286ff241ba7cf066336486ef1639685a47) Merge origin/main into fix/windows-update-command-timeout ### 📊 Changes **1 file changed** (+4 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `tests/process-global/updateMaintenance.test.ts` (+4 -1) </details> ### 📄 Description ## Summary Fixes #4989. Give the two independent CLI boundary checks independent Vitest deadlines. A delayed `--help` launch can no longer consume the entire deadline before the removed `upgrade --json` command is exercised, and a future timeout identifies the affected command in the test title. ## Problem and expected behavior The existing test runs two real CLI subprocesses serially under one 30-second test deadline. Windows qualification recorded one timeout, but the combined test title and deadline did not identify which subprocess was pending. Each subprocess normally finishes in about one second and represents a separate contract. Each command boundary should receive its own test lifecycle and timeout, while preserving the existing help-output and removed-command assertions. ## Change and scope Split the combined test into two focused cases: - `exposes update in CLI help` - `rejects the removed upgrade CLI command` No timeout value, retry policy, assertion, subprocess implementation, or runtime behavior changed. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). ## Contract and boundary impact - Semantic owner and earliest changed stage: Windows process-global CLI test orchestration. - Contribution scope fit and linked maintainer decision: ordinary test reliability correction; maintainer scope decision not applicable. - CLI and MCP/tool-catalog contract: unchanged. - Provider, bridge, target-format, or platform compatibility: unchanged. - Evidence, artifact, provenance, or reconstruction contract: unchanged. - Target selection, authority, upstream behavior, and cleanup details: unchanged; the same two CLI subprocesses are launched and awaited. - Generated metadata, package, or installation impact: none. Expected effects: - [ ] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests updated: `tests/process-global/updateMaintenance.test.ts`. - Base evidence: #4989 records the combined test timing out at 30,009 ms on one Windows qualification run. The identical source passed other runs, so the underlying runner stall was not reproduced locally. - Modified Windows run: both isolated cases passed, with `--help` completing in 1,030 ms and removed `upgrade --json` completing in 993 ms. - User-visible CLI/MCP output: not applicable; assertions and runtime behavior are unchanged. - Remaining proof gaps: the original intermittent GitHub-hosted runner stall remains unexplained. This change isolates its budget and diagnostic identity rather than claiming to fix a production hang. - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed Windows x64, Node 24.18.0, npm 11.16.0: - `npm run test:focused -- tests/process-global/updateMaintenance.test.ts` — 28 passed. - `npm run check:fast` — typecheck and lint passed. - `npm run format:check -- tests/process-global/updateMaintenance.test.ts` — all 4,025 matched files passed. - `git diff --check` — passed. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: Windows process-global test executed; no provider or target workflow is affected. - Package or release metadata impact: none. - Security, privacy, process, or containment review: test-only change; subprocess commands and environment handling are unchanged. ## Author readiness Human owner: @XY-code1 - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked. - [x] Tests cover the changed test-orchestration behavior. - [x] Owning docs, contracts, and generated metadata are unchanged. - [x] User-visible CLI/MCP output is not applicable. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:42:41 +00:00
bsakaguchi changed title from [PR #5019] [MERGED] test(update): isolate CLI subprocess deadlines to [PR #5019] test(update): isolate CLI subprocess deadlines 2026-11-03 13:34:03 +00:00
bsakaguchi changed title from [PR #5019] test(update): isolate CLI subprocess deadlines to [PR #5019] [MERGED] test(update): isolate CLI subprocess deadlines 2026-11-03 14:35:48 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#6737
No description provided.