-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Description
Several of the tests (especially in the queue test suite) fail quite frequently. This is due to setTimeout
timing issues. We could sort of address this by increasing the delays but that isn't a proper solution. These tests probably just need rewrites.
These issues have been observed several times in the past
- Browser CI Setup #1152 (blocking sauce integration)
- CITGM test failing on s390 #1303, Asyc failing with citgm on linux #1311 (citgm fails intermittently)
- frequently in travis build failures where we have to manually retrigger the build
I created PR #1321 as a stopgap, to alleviate some of the issues a bit by retrying the flakier tests when they fail. All retries
we implement should be removed along with this fix for this issue as retries in unit tests are really ugly and may be masking other issues with the library.
Note: this may be difficult to reproduce on your local system. I've mainly noticed it in simulated environments with slower systems causing setTimeout
calls to be delayed. Systems like travis/sauce fail quite frequently