Skip to content

ci: raise the test timeout 50m -> 90m #623

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
tannevaled merged 1 commit into from
Sep 21, 2026
Merged

ci: raise the test timeout 50m -> 90m #623

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
6 changes: 4 additions & 2 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,8 +41,10 @@ jobs:
# -race roughly doubles wall-clock, and the windows runner is the slowest
# of the three OS lanes; the growing vm suite tips it past go test's 10m
# default. macOS/ubuntu finish ~20m; windows runs ~2x so needs more room.
# Bumped 30m->50m as the vm binding set keeps growing (Puppet ecosystem wave).
go test -timeout=50m -race -coverpkg="$COVERPKG" -coverprofile=cover.out ./...
# Bumped 30m->50m (Puppet ecosystem wave), then 50m->90m: the windows
# binary hit the 50m alarm at 3007s with the running test at 0s — the
# budget ran out, nothing hung — and each conformance wave adds to it.
go test -timeout=90m -race -coverpkg="$COVERPKG" -coverprofile=cover.out ./...
echo "--- functions below 100% (empty = all covered) ---"
go tool cover -func=cover.out | grep -vE '100\.0%$' || true
echo "---------------------------------------------------"
Expand Down
Loading