ci: exclude Go caches from Defender on Windows test job - #87
Merged
Conversation
The Windows test matrix spends ~10m almost entirely in Microsoft Defender real-time scanning of the small files the Go toolchain emits. Add a Windows-only step that excludes GOCACHE/GOMODCACHE/workspace and go.exe before setup-go, mirroring the upstream monorepo's shared go-setup action.
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
1 participant
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.
Why
The Windows leg of the
testmatrix runs ~10m while Linux/macOS finish in acouple of minutes.
setup-goalready caches; the dominant remaining cost isMicrosoft Defender real-time scanning of the many small object/link files the Go
toolchain writes during compile/test.
What
Adds a Windows-only step (before
setup-go) that excludesGOCACHE(
%LOCALAPPDATA%\go-build),GOPATH/GOMODCACHE(%USERPROFILE%\go), theworkspace, and
RUNNER_TEMPfrom Defender, plus-ExclusionProcess go.exe.Wrapped in try/catch so it degrades gracefully if the runner denies it.
This mirrors the shared
.github/actions/go-setupaction just landed upstreamin operatorstack/intelligence-flow#147, where the equivalent monorepo Windows
job dropped from ~9m25s to ~2m. Only the
ci.ymltest job changes; no runtimeor sync-contract behavior is affected.