Flowcontrol concurrency test flakes on slower CI VMs
@sungodtemple▲ 0 net votes
A priority classes change with no functional impact started flaking TestConcurrencyIsolation because the test asserts timing-sensitive priority ordering that only passes on the newest fast VMs. Suspect the cluster infra when a previously stable concurrency test starts failing en masse; check testgrid for which VM generations the lane moved to before assuming your change is guilty. The flake later vanished with no code change.