Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
6.0
-
None
Description
This error occurs in Ubuntu 18.04
http://coin/coin/api/results/qt/qtvirtualkeyboard/a5f6a84768f00e321300612b48505e76da7befda/LinuxUbuntu_18_04x86_64LinuxUbuntu_18_04x86_64GCCqtci-linux-Ubuntu-18.04-x86_64-d4fa8dDocumentation_OutOfSourceBuild_UseLegacyInstructions/a64d2a69e7ed411d4dab8b16ce868e33ae21e279/test_1580978159/log.txt.gz http://coin/coin/integration/qt/qtdeclarative/tasks/1581673896
agent:2020/02/14 12:10:55 build.go:220: FAIL! : qmltestrunner::AnimatedImage::test_crashRaceCondition_replyFinished() property active agent:2020/02/14 12:10:55 build.go:220: Actual (): true agent:2020/02/14 12:10:55 build.go:220: Expected (): false agent:2020/02/14 12:10:55 build.go:220: Loc: [/home/qt/work/qt/qtdeclarative/tests/auto/qmltest/animatedimage/tst_animatedimage.qml(269)] agent:2020/02/14 12:10:55 build.go:220: PASS : qmltestrunner::AnimatedImage::test_imageSource(local) agent:2020/02/14 12:10:55 build.go:220: PASS : qmltestrunner::AnimatedImage::test_imageSource(local not found) agent:2020/02/14 12:10:55 build.go:220: SKIP : qmltestrunner::AnimatedImage::test_imageSource(remote) Remote solution not yet complete agent:2020/02/14 12:10:55 build.go:220: Loc: [/home/qt/work/qt/qtdeclarative/tests/auto/qmltest/animatedimage/tst_animatedimage.qml(210)] agent:2020/02/14 12:10:55 build.go:220: PASS : qmltestrunner::AnimatedImage::test_noSource() agent:2020/02/14 12:10:55 build.go:220: QWARN : qmltestrunner::AnimatedImage::test_noSource() file:///home/qt/work/qt/qtdeclarative/tests/auto/qmltest/animatedimage/inline:1:21: QML AnimatedImage: Error Reading Animated Image File http://127.0.0.1:14445/stickman.gif agent:2020/02/14 12:10:56 build.go:220: PASS : qmltestrunner::AnimatedImage::test_resized() agent:2020/02/14 12:10:56 build.go:220: PASS : qmltestrunner::AnimatedImage::test_smooth() agent:2020/02/14 12:10:56 build.go:220: PASS : qmltestrunner::AnimatedImage::test_tileModes() agent:2020/02/14 12:10:56 build.go:220: PASS : qmltestrunner::AnimatedImage::cleanupTestCase() agent:2020/02/14 12:10:56 build.go:220: Totals: 9 passed, 1 failed, 1 skipped, 0 blacklisted, 10757ms agent:2020/02/14 12:10:56 build.go:220: ********* Finished testing of qmltestrunner ********* agent:2020/02/14 12:10:56 build.go:220: Makefile:336: recipe for target 'check' failed agent:2020/02/14 12:10:56 build.go:220: make: *** [check] Error 1 agent:2020/02/14 12:10:56 build.go:253: Process finished with error: exit status 2 agent:2020/02/14 12:10:56 build.go:223: Error reading from stdout/err: exit status 2 agent:2020/02/14 12:10:56 build.go:471: Executing scheduled instruction 1 of 2 - Upload all core dumps if there are some agent:2020/02/14 12:10:56 build.go:384: Skip uploading core files because CORE_FILES_PATH is not set in the environment agent:2020/02/14 12:10:56 build.go:473: agent:2020/02/14 12:10:56 build.go:471: Executing scheduled instruction 2 of 2 - Upload test results agent:2020/02/14 12:10:56 storageclient.go:451: Collecting test results, archiving and uploading them agent:2020/02/14 12:10:56 result.go:177: Collecting 171 test results ...
external log:
https://testresults.qt.io/ coin/api/results/qt/qtdeclarative/dc833185ceeed18dc86f1b4d8438c3c76b5cfbda/LinuxUbuntu_18_04x86_64LinuxQEMUarmv7GCCqtci-linux-Ubuntu-18.04-x86_64-d4fa8dUseLegacyInstructions/be6fd55b483daa91a0122b0043dc85e95372aeac/test_1581673972/log.txt.gz
The wanted action
- Fix the autotest flakiness in all affected versions, not just one.
- Please delegate this task to a suitable developer
Guidelines for debugging
Please see the internal page https://intranet.qt.io/display/QTRD/Metrics+Guidelines+for+Grafana+Tool+for+Autotests+with+Issues
How to locate the failed flaky test:
Please open the link to the Grafana dashboard showing the failure history of the test:
Please see the panel List of the recent flaky tests (both passed and failed). Sort it based on the results to see the failed instances.
Please open the links to the Coin tasks containing the logs. Please see the test section containing state "Error" and open corresponding logs. There are two versions of the links. The first one is for the Qt company internal use allowing you to re-schedule build for debugging. The second one is public, allowing only to browse the logs.
List of the incidents:
- Incident 2: Qt dev: Host Ubuntu 18.04, GCC compiler
The Coin log shows details and the location of the error message in it. At need, the raw log can be opened to see the entire log at once.