Skip to content

ci: Windows test job gains Defender exclusions - #210

Closed
graywolf336 wants to merge 2 commits into
devfrom
chore/ci-windows-defender
Closed

graywolf336 wants to merge 2 commits into
devfrom
chore/ci-windows-defender

Conversation

@graywolf336

Copy link
Copy Markdown
Contributor

The Windows test leg takes 15.5 minutes versus 6 on Linux. Filesystem-heavy suites (repository, teams, database owner) run 4x to 15x slower there, dominated by Defender real-time scanning of temp and cache directories. This adds a best-effort exclusion step to the Windows job before tests run. It never fails the job when denied on managed runners.

The filesystem-heavy suites (repository, teams, database owner) run 4x
to 15x slower on Windows than Linux, largely from Defender real-time
scanning of the temp and cache directories. Add a best-effort exclusion
step before running tests; it never fails the job when denied.
@graywolf336

Copy link
Copy Markdown
Contributor Author

Closing as a draft with no measurable benefit. The exclusions installed cleanly but the Windows test leg showed no improvement (680s vs 620s test execution, within noise; this run also had no cargo cache hit). The actual lever is likely redb per-transaction fsync in the test path, which this step does not touch. Superseded by a targeted durability change in the test repo helper.

@graywolf336
graywolf336 deleted the chore/ci-windows-defender branch September 22, 2026 16:37
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