You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Windows TUI streaming end-to-end tests are susceptible to timing flakes when running with a cold cache. PR #3980 exposed this in GitHub Actions job 94686562047: the test can exceed the current TUI test timeout while the Windows environment is still starting the stream and rendering the initial output.
Goal
Harden the Windows TUI streaming e2e coverage against cold-cache and startup timing variance without weakening the assertions or masking genuine hangs.
Proposed change
Update the affected Windows streaming e2e tests to use the targeted tuitest.WithTimeout(30*time.Second) timeout.
Keep the timeout scoped to the affected TUI test(s), rather than applying a broad global timeout increase.
Preserve the existing streaming/output assertions and failure diagnostics.
Consider a follow-up, if the evidence supports it, to improve CI cache behavior or reduce Windows test parallelism; that follow-up is optional and should not block the focused timeout fix.
Acceptance criteria
The affected Windows TUI streaming e2e tests use tuitest.WithTimeout(30*time.Second).
Problem
The Windows TUI streaming end-to-end tests are susceptible to timing flakes when running with a cold cache. PR #3980 exposed this in GitHub Actions job 94686562047: the test can exceed the current TUI test timeout while the Windows environment is still starting the stream and rendering the initial output.
Goal
Harden the Windows TUI streaming e2e coverage against cold-cache and startup timing variance without weakening the assertions or masking genuine hangs.
Proposed change
tuitest.WithTimeout(30*time.Second)timeout.Acceptance criteria
tuitest.WithTimeout(30*time.Second).Validation
task test,task lint, andtask build) where applicable.Context