Closed anderseknert closed 3 months ago
I've done some digging here, it looks to me that this is (now, after some previous adjustments to this test) just a case of the timeouts being too aggressive to be reliable on GH actions.
I have been doing some testing today and found that in 300 runs the max time is around 1.8s to wait for a file's state to be consistent with the expected value.
I think that the fix here is going to be making the timeouts longer for now as I've not been able to replicate any locking behaviour that causes this test to fail in another wait other than the timeout.
I have increased the timeout in #933
This is annoying, and a bad contributor experience, as it's nothing they've caused or can address. We should fix this ASAP.