1bbd9d8ee5
QTimeLine appears to have very poor timing characteristics. Historical CI logs show roughly one failure in every twenty-five test runs on Windows, and less frequent failures on Mac and Linux. The root of the problem seems to be that QTimeLine's currentTime counter appears to run at a variable speed and the only guarantee is that it is slower than wall time. The frameChanged() test function waited for double the expected duration of the timeline and still found that the timeline had failed to finish in about one in every thirty test runs. The interpolation() test function also failed for the same reason, though less often. This commit makes the frameChanged test more strict so that the poor timing will be demonstrated more often, waiting only 1.5 times the duration instead of double the duration. It also makes the test fail gracefully so that this known issue won't disrupt CI when the test is made significant in a later commit. Task-number: QTBUG-24796 Change-Id: If469d43abb662e24445a9da619052eea9cf7c581 Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| qtimeline.pro | ||
| tst_qtimeline.cpp | ||