Repository navigation
ci(e2e): raise the Windows unit-test step timeout to 40m to match unit-tests.yml - #1527
Merged
Merged
Conversation
…t-tests.yml internal/server under -race on windows-latest now takes 650s to over 1200s, and the E2E workflow's 20m budget timed out on 6 of ~10 recent main runs with no hang in the goroutine dumps. unit-tests.yml already moved its Windows sweep to 40m for the same growth; bring this step back in step.
Deploying mcpproxy-docs with
|
| Latest commit: |
036a02f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://1209ff6e.mcpproxy-docs.pages.dev |
| Branch Preview URL: | https://fix-ci-windows-e2e-timeout.mcpproxy-docs.pages.dev |
Dumbris
enabled auto-merge (squash)
October 6, 2026 07:55
Contributor
📦 Build ArtifactsWorkflow Run: View Run Available Artifacts
How to DownloadOption 1: GitHub Web UI (easiest)
Option 2: GitHub CLI gh run download 37432718237 --repo smart-mcp-proxy/mcpproxy-go
|
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
Run unit testsstep ine2e-tests.ymlrunsgo test -short -race ./internal/...with a 20m budget. On windows-latest (main pushes only),internal/servernow takes 650s to over 1200s and hit the cap on 6 of the last ~10 main runs:panic: test timed out after 20m0s, with whatever test happened to be running (e.g.TestToonDetectionParity_*, unchanged since July) in flight and no deadlock in the goroutine dump.The step's own comment says its budget must stay in step with the Windows sweep in
unit-tests.yml, which already moved to 40m when the package reached ~1100-1200s. This PR raises this step to 40m to match and records why. CI-only change; no jobtimeout-minutesis set, so the 360m default still bounds the job.Not a regression from recent merges: the package was already at 913s on a green main run on 2026-09-24.