Skip to content

ci(windows): cache GOCACHE and raise Go test timeouts#297

Open
flightlesstux wants to merge 1 commit intomksglu:nextfrom
flightlesstux:fix/windows-ci-go-cold-build
Open

ci(windows): cache GOCACHE and raise Go test timeouts#297
flightlesstux wants to merge 1 commit intomksglu:nextfrom
flightlesstux:fix/windows-ci-go-cold-build

Conversation

@flightlesstux
Copy link
Copy Markdown
Contributor

Summary

  • Windows CI fails intermittently with Test timed out in 30000ms on tests/executor.test.ts > Go Execution > Go: hello world — cold GOCACHE on the Windows runner blows past vitest's default 30s.
  • Cache GOCACHE + GOMODCACHE across runs via actions/cache, keyed per matrix OS. Paths resolved with go env so it works on all three OSes.
  • Raise the two Go execution tests to a 90s timeout as a safety net for fresh caches / new runner images.

Test plan

  • CI green on ubuntu / macos / windows
  • Re-run Windows job with cache hit — Go tests complete well under 90s
  • Cold-cache run (key miss) — still passes via the raised timeout

Windows runners hit `Test timed out in 30000ms` on
`tests/executor.test.ts > Go Execution > Go: hello world` because the
first Go compile on a cold runner exceeds vitest's default 30s timeout.

- Cache GOCACHE + GOMODCACHE with actions/cache, keyed per matrix OS.
  Paths resolved via `go env` so it works on ubuntu/macos/windows.
- Raise the two Go execution tests to a 90s timeout as a safety net for
  the first run on a fresh cache or a new runner image.
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