Still needs fixing. If there's one thing we've learnt from all these CI failures it's that 3-5 second timeouts are not enough for heavily loaded machines. We need 30-60 seconds instead.
If the test is properly written then a higher timeout costs us nothing - the timeout is never reached and the test completes sooner.
Still needs fixing. If there's one thing we've learnt from all these CI failures it's that 3-5 second timeouts are not enough for heavily loaded machines. We need 30-60 seconds instead.
If the test is properly written then a higher timeout costs us nothing - the timeout is never reached and the test completes sooner.