Before this the remaining time in the two tests 'remainingTime' and 'basic_chrono' had to be within the interval [100,200]. This relaxes that to [50,200]. This test seems to be failing a lot when staging changes in gerrit. I can reproduce some of the problem when putting a lot of load on my system and running the tests, then remaining time is very random. Also removes the blacklist of remaingTime on Windows and macOS, as basic_chrono and remaningTime tests are basically the same. The tests also fails on Linux some times in gerrit. I was also thinking one could: - blacklist both tests - remove interval requirements; just check remaining time is [0,200] - remove the tests Task-number: QTBUG-61013 Change-Id: I5c8f0754d059598e023fe8e5d511f4a50bb4bac2 Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> |
||
|---|---|---|
| .. | ||
| qcoreapplication | ||
| qdeadlinetimer | ||
| qelapsedtimer | ||
| qeventdispatcher | ||
| qeventloop | ||
| qmath | ||
| qmetaenum | ||
| qmetamethod | ||
| qmetaobject | ||
| qmetaobjectbuilder | ||
| qmetaproperty | ||
| qmetatype | ||
| qmimedata | ||
| qobject | ||
| qpointer | ||
| qsharedmemory | ||
| qsignalblocker | ||
| qsignalmapper | ||
| qsocketnotifier | ||
| qsystemsemaphore | ||
| qtimer | ||
| qtranslator | ||
| qvariant | ||
| qwineventnotifier | ||
| kernel.pro | ||