On Thu, Jan 23, 2020 at 08:40:19PM +0500, ???? ??????? wrote: > those timeouts are not related to travis itself, I beleive they are mostly > related to either real failures or tests instability (race condition).
These tests are racy by nature and some rely on short delays (i.e. health checks). If tests are run on an overloaded machine I don't find it surprising that a few will fail. Often I click restart and they succeed. These ones often fail there and only there, so the environment definitely has an impact. And seeing the execution time which has become 10-30 times what it is on simple laptop really makes me feel like the VMs are seriously stressed. > the bigger is number of tests, the more we depend on those timeouts. > > however, we can try to run tests in parallel :) It would be worse! Willy
