Morten Johan Sørvig d044b0b1e3 Remove timer checks from testQuitLock ... This test sets up two timers: - a 100ms recurring timer - a series of 10 200ms single-shot timers. After quitLock lets exec() return it then uses a signal spy to check if the 100ms timer fired at least 17/20 of the times it should. However there is no guarantee that the 100ms timer will fire more often than the 200ms timer. If the native timer callbacks happen at 500ms intervals then Qt will fire both timers (once) at that interval. In practice this seems to happen on macOS CI under system load and/or with the test app napping. The primary goal for the test is to verify that exec() returns when it should; we can remove the timer signal spy. Remove testQuitLock from BLACKLIST. Timely timer: 524429311.389913 runLoopTimerCallback 524429311.389979 200ms fire 524429311.389997 100ms fire 524429311.490056 runLoopTimerCallback 524429311.490130 100ms fire 524429311.589752 runLoopTimerCallback 524429311.589929 200ms fire 524429311.589976 100ms fire Delayed timer: 524429428.690887 runLoopTimerCallback 524429428.691002 100ms fire 524429428.691143 200ms fire 524429433.692103 runLoopTimerCallback 524429433.692205 100ms fire 524429433.692331 200ms fire Change-Id: Iff4faaa1de3741cf4e217949d5ed17d4e70c6af2 Task-number: QTBUG-61499 Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>		2017-08-22 05:10:48 +00:00
..
.gitignore	Moving relevant tests to corelib/kernel	2011-09-01 12:42:14 +02:00
BLACKLIST	Blacklist tst_QEventLoop:testQuitLock as it is flaky on macOS	2017-05-23 14:52:31 +00:00
qeventloop.pro	Use qtConfig throughout in qtbase	2016-08-19 04:28:05 +00:00
tst_qeventloop.cpp	Remove timer checks from testQuitLock	2017-08-22 05:10:48 +00:00