Skip to content

ci(e2e): raise the Windows unit-test step timeout to 40m to match unit-tests.yml #1527

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Dumbris merged 1 commit into from
Oct 6, 2026
Merged

ci(e2e): raise the Windows unit-test step timeout to 40m to match unit-tests.yml #1527

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions .github/workflows/e2e-tests.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,7 @@ jobs:
# they run unguarded in the main-only stress-tests job below so coverage
# is preserved.
#
# Timeout is 20m to match the Windows sweep in unit-tests.yml. It was
# Timeout matches the Windows sweep in unit-tests.yml. It was
# 4m, which the windows-latest runner could not meet: internal/server
# took 240s and died at `panic: test timed out after 4m0s` — with a
# single test only 2s in, so cumulative slowness (Bleve index creation
Expand All @@ -106,8 +106,12 @@ jobs:
# 10m on 2026-09-12 (a74a7cf0f: 449s one push, 600s+ the next, a 4s
# test in flight), so both budgets moved to 20m. Keep them in step;
# the same code timing out in one and passing in the other is the
# signature of this bug returning.
run: go test -v -short -race -timeout 20m -skip "Binary|MCP|E2E|TestInfoEndpoint|TestGracefulShutdownNoPanic|TestSocketInfoEndpoint" ./internal/...
# signature of this bug returning. unit-tests.yml moved its Windows
# sweep to 40m when internal/server reached ~1100-1200s; this step was
# left at 20m and hit it on 6 of ~10 windows-latest main runs in
# 2026-10 (internal/server at 650s to over 1200s, no hang in the
# goroutine dumps), so it is 40m again to match.
run: go test -v -short -race -timeout 40m -skip "Binary|MCP|E2E|TestInfoEndpoint|TestGracefulShutdownNoPanic|TestSocketInfoEndpoint" ./internal/...

# Binary tests are too flaky in CI due to server startup timing issues
# All Binary tests consistently timeout waiting for server to be ready
Expand Down
Loading