Thanks for bringing this up. We've seen these tests misbehave under
load on sanitizer bots, but not in the last few weeks, and we could
never reproduce it locally. I'll disable the test for now.
Btw, we've also seen this test survive whatever buildbot does in the
case of a step timeout and consuming the CPU cycles forever after
that. Please check the bot for runaway processes.