Skip to content

devops: run Windows CI tests at normal I/O priority - #2026

Merged
Pavel Feldman (pavelfeldman) merged 1 commit into
microsoft:mainfrom
yury-s:windows-normal-io
Oct 28, 2026
Merged

Pavel Feldman (pavelfeldman) merged 1 commit into
microsoft:mainfrom
yury-s:windows-normal-io

Conversation

@yury-s

@yury-s Yury Semikhatsky (yury-s) commented Oct 28, 2026 •

Copy link
Copy Markdown
Member

Summary

The Windows Firefox job on main passed after #2025 only because of retries. It had 11 flaky tests, most of them 30s timeouts in cookies, credentials, proxy and context tests (run).

-D junit.parallel.factor=0.25 on Windows stays for now. It may be possible to raise it once this lands.

Verification

On this PR's run, every Windows test step logs Test launcher I/O priority: 1 -> 2 (Normal). dev (server2025, firefox) ran 5312 tests with 0 failures and 0 flakes. stable (server2025, msedge) fails on TestClick.shouldClickOffscreenButtons: a Failed to load resource ... 404 console message shows up among the click messages. The same test failed the same way on main on the 10-26 windows-latest run, before this change.

The Windows runner starts steps at I/O priority Low. The driver and the
browsers inherit it, and Firefox storage flushes stall until tests time out.
Reset the test steps to Normal, as microsoft/playwright#43707 does upstream.
@pavelfeldman
Pavel Feldman (pavelfeldman) merged commit 491e9b0 into microsoft:main Oct 28, 2026
10 of 15 checks passed
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.

2 participants