N.b. we're intermittently seeing issues with timeouts/races in the following tests, likely for similar reasons:
2.0:
2.0-UCBasicUsage2,
2.0-UCBasicUsage1
1.2:
AOpensBMultipleListen,
UCFilteredUsage3,
UCBasicUsage1,
TargetdResolve1
Only happens occasionally and only on CI (Github actions), but is confined to this set of tests (we are continuing to observe for others). The runners are virtualized and low-spec - they've never been observed to do this on a local machine. But that probably just means we are relying on winning a race.
N.b. we're intermittently seeing issues with timeouts/races in the following tests, likely for similar reasons:
Only happens occasionally and only on CI (Github actions), but is confined to this set of tests (we are continuing to observe for others). The runners are virtualized and low-spec - they've never been observed to do this on a local machine. But that probably just means we are relying on winning a race.