Seen on #5875 (dependabot base64 bump, recreated head e2b2b49), run 34013201624 job 101432543520, windows-latest:
TIMEOUT [ 600.110s] codewhale-tui commands::tests::every_command_alias_dispatches_to_a_handler
TIMEOUT [ 600.105s] codewhale-tui commands::tests::every_registered_command_dispatches_to_a_handler
Both tests dispatch every registered command (and every alias) through the real handler table. The bump touches nothing near commands, so this is a Windows-only hang in one of the handlers under test, not a regression from the PR. It is a second family of Windows flake next to #5898 (which #5913 fixes) and it costs a full 10-minute timeout per occurrence.
Acceptance:
- Identify which command's handler blocks on Windows (run the loop with a per-command watchdog that names the offender on timeout).
- Fix or skip-with-reason that handler in the dispatch-everything tests so the suite fails fast with a name, never a bare 600 s timeout.
- Windows matrix green on three consecutive runs of the two tests.
Seen on #5875 (dependabot base64 bump, recreated head e2b2b49), run 34013201624 job 101432543520, windows-latest:
Both tests dispatch every registered command (and every alias) through the real handler table. The bump touches nothing near commands, so this is a Windows-only hang in one of the handlers under test, not a regression from the PR. It is a second family of Windows flake next to #5898 (which #5913 fixes) and it costs a full 10-minute timeout per occurrence.
Acceptance: