Details
-
Bug
-
Resolution: Invalid
-
P3: Somewhat important
-
None
-
5.14, 5.15, 6.0
-
Linux/Wayland,
macOS,
Windows
Description
This error occurs in Ubuntu 18.04, Windows 10, OpenSUSE 15, macOS 10.14 and macOS 10.12
http://coin/coin/integration/qt/qt5/tasks/1580977809
agent:2020/02/06 09:18:14 build.go:220: QWARN : inputpanel::tst_plugin::test_japaneseInputModes(row 3) qrc:/QtQuick/VirtualKeyboard/Styles/content/SelectionListItem.qml:44: TypeError: Cannot read property 'height' of null agent:2020/02/06 09:18:14 build.go:220: QWARN : inputpanel::tst_plugin::test_japaneseInputModes(row 3) qrc:/QtQuick/VirtualKeyboard/Styles/content/SelectionListItem.qml:44: TypeError: Cannot read property 'height' of null agent:2020/02/06 09:18:14 build.go:220: Makefile:328: recipe for target 'check' failed agent:2020/02/06 09:18:14 build.go:220: make: *** [check] Segmentation fault agent:2020/02/06 09:18:14 build.go:253: Process finished with error: exit status 2 agent:2020/02/06 09:18:14 build.go:223: Error reading from stdout/err: exit status 2 agent:2020/02/06 09:18:14 build.go:471: Executing scheduled instruction 1 of 2 - Upload all core dumps if there are some agent:2020/02/06 09:18:14 build.go:384: Skip uploading core files because CORE_FILES_PATH is not set in the environment agent:2020/02/06 09:18:14 build.go:473: agent:2020/02/06 09:18:14 build.go:471: Executing scheduled instruction 2 of 2 - Upload test results agent:2020/02/06 09:18:14 storageclient.go:451: Collecting test results, archiving and uploading them agent:2020/02/06 09:18:14 result.go:177: Collecting 1 test results ... agent:2020/02/06 09:18:14 build.go:473: agent:2020/02/06 09:18:14 agent.go:272: Test failed agent:2020/02/06 09:18:14 agent.go:200: ERROR building: error unmarshalling testlib xml output ('/home/qt/work/testresults/tests/auto/inputpanel018575243'): 'XML syntax error on line 2127: unexpected EOF'.
external log:
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 1: Qt 5.14: Host Windows 10, MSVC2017 compiler
- Internal link: http://coin/coin/integration/qt/qt5/tasks/1581663994
- Public link: https://testresults.qt.io /coin/integration/qt/qt5/tasks/1581663994
- Incident 2: Qt 5.14: Host Windows 10, MSVC2017 compiler
- Internal link: http://coin/coin/integration/qt/qt5/tasks/1583184959
- Public link: https://testresults.qt.io /coin/integration/qt/qt5/tasks/1583184959
More incidents can be found from:
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.