Danny Canter

Also can confirm 1.19 gets things in order again.. Believe it was this set of patches from @thanm https://github.com/golang/go/commit/0c7fcf6bd1fd8df2bfae3a482f1261886f6313c1 https://github.com/golang/go/commit/eaf21256545ae04a35fa070763faa6eb2098591d

@TBBle Sorry for not getting around to this fast Paul 😥 I'll be taking a look at this tomorrow. It's kind of a crummy situation in `computestorage` that spurred this...

We run critest internally as well and haven't seen this test (or any for that matter) fail. Our tests internally are on AZ machines so it's possible it may be...

@helsaawy This makes me think some of your work may have fixed/will fix this (also confused how we don't seem to be hitting this internally or on the periodic tests)....

@olljanat @helsaawy and I would likely be the ones on the hook here :)

Okay, peering back in after trying this quite extensively locally (over 200 iterations) with no failures.. It seems the Github actions machines are the minority here if things seem to...

I think we'd just re-run the CI if it failed so I don't have a lot of examples to show but here's one from after check-in that shows the same...

> It might be worth trying to run up the [GitHub Actions VM image](https://github.com/actions/virtual-environments) for Server 2022, and see if the problem can reproduce there. Given that it seems to...

Given the periodic tests are in their own yaml, couldn't we get away with just -ginkgo.skip {regex} on the run in ci.yml?

> > I'll probably need to shift the focus to trying to debug on the actions machines as I can't seem to get a repro locally, unless someone else is...