Skip to content

Trace native acceptance runtime shutdown phases - #57

Open
Fectivnfy112357 wants to merge 1 commit into
fix/webui-ci-startup-diagnosticsfrom
fix/webui-shutdown-phase-diagnostics
Open

Fectivnfy112357 wants to merge 1 commit into
fix/webui-ci-startup-diagnosticsfrom
fix/webui-shutdown-phase-diagnostics

Conversation

@Fectivnfy112357

@Fectivnfy112357 Fectivnfy112357 commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Context

Related to #30. The original Windows run stopped in the harness shutdown after the sandbox reported closed. The acceptance fixture supplied no browser provider and used a no-op mcode-tools disposer. The remaining waits in the shared runtime were indistinguishable from that log.

Change

The native-browser acceptance child opts into fixed phase markers on stderr before the runtime awaits a shutdown owner. The markers identify the sandbox call, background maintenance, owner-lease release, legacy host close and database close. The existing acceptance host deadline continues to report a failed shutdown with captured stderr. Shutdown order and error propagation are retained. The source inventory and AOCI entries include the diagnostic helper.

Verification

This branch is based on #54, which passed the same WebUI CI matrix on Ubuntu, Windows and macOS. Review this PR against the #54 branch.

  • Full Linux pnpm verify passed all 26 applicable gates, including 515 browser cases.
  • In a controlled Linux failure test, the real acceptance host was started with an isolated scratch directory and its runtime-owner lease file removal was held pending. The host returned closed:false and stalledAt:harness after 20,001 ms and exited. Captured stderr ended its runtime markers at release_runtime_owner. This validates the diagnostics on the timeout path. It does not identify the owner in the original Windows incident.

Hosted WebUI CI run 44679668737 passed on Ubuntu, macOS, and Windows at 34b66747b. The Windows native terminal acceptance passed along with all 515 browser cases. The original shutdown timeout did not recur in this run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant