Repository navigation
fix(shard): fail when no tests match across all shards - #43173
Conversation
Since v1.31, sharding happens before the "No tests found" check, so the check was skipped for any sharded run. A bad testDir, grep or file filter passed silently. Now the check uses the test count before sharding, so an empty shard still passes while an empty run fails. Fixes: microsoft#43128
381fbf5 to
40d46e7
Compare
This comment has been minimized.
This comment has been minimized.
Test results for "tests 1"6 flaky52686 passed, 1270 skipped Merge workflow run. |
Test results for "MCP"1 failed 9034 passed, 1495 skipped Merge workflow run. |
🟢 Playwright bot: this is a pre-existing flakeThe only real failure is unrelated to this PR. The same DetailsOverall assessment This PR only changes test-runner sharding and its tests. It does not reach the MCP annotation flow, browser dashboard, or navigation path involved in the failure. The six retry-rescued tests in the Pre-existing flake / infra
Triaged by the Playwright bot - agent run |
4dd2a65
into
microsoft:main
Summary
testDir,--grepor file filter passed silently.Fixes #43128