Details
-
Bug
-
Resolution: Invalid
-
P1: Critical
-
None
-
5.15
-
None
-
macOS,
Windows
Description
This error occurs in Windows 10 and in macOS 10.14
http://coin/coin/integration/qt/qtwebengine/tasks/1581459712
agent:2020/02/12 02:08:26 build.go:220: PASS : tst_Dialogs::authenticationDialogRequested(Proxy Authentication Dialog)
agent:2020/02/12 02:08:26 build.go:220: PASS : tst_Dialogs::cleanupTestCase()
agent:2020/02/12 02:08:26 build.go:220: Totals: 10 passed, 0 failed, 0 skipped, 0 blacklisted, 5060ms
agent:2020/02/12 02:08:26 build.go:220: ********* Finished testing of tst_Dialogs *********
agent:2020/02/12 02:23:18 build.go:138: Virtual Memory Total: 16105586688, Free:0, UsedPercent:18.000000%
agent:2020/02/12 02:23:18 build.go:269: Killed process: Maximum step duration reached (timeout: 900 seconds)
agent:2020/02/12 02:23:18 build.go:223: Error reading from stdout/err: Timeout after 15m0s: Maximum duration reached
agent:2020/02/12 02:23:18 build.go:471: Executing scheduled instruction 1 of 2 - Upload all core dumps if there are some
agent:2020/02/12 02:23:18 build.go:384: Skip uploading core files because CORE_FILES_PATH is not set in the environment
agent:2020/02/12 02:23:18 build.go:473:
agent:2020/02/12 02:23:18 build.go:471: Executing scheduled instruction 2 of 2 - Upload test results
agent:2020/02/12 02:23:18 storageclient.go:451: Collecting test results, archiving and uploading them
agent:2020/02/12 02:23:18 result.go:177: Collecting 1 test results ...
agent:2020/02/12 02:23:18 build.go:473:
agent:2020/02/12 02:23:18 agent.go:272: Test failed
agent:2020/02/12 02:23:18 agent.go:200: ERROR building: Timeout after 15m0s: Maximum duration reached
INFO:workitem.py:612(31796): Agent FINISHED FAIL: testing C:/Users/qt/work/qt/qtwebengine/tests/auto/quick/dialogs: qt/qtwebengine/840d5e8d2cdb289a4748fb0a05b7c6598741ee50/WindowsWindows_10x86_64WindowsWindows_10x86MSVC2017qtci-windows-10-x86_64-15-f36aa5/362b9316e75597e6d1324bdcf98e2f7bde397f92/Test
external log:
https://testresults.qt.io /coin/api/results/qt/qtwebengine/840d5e8d2cdb289a4748fb0a05b7c6598741ee50/WindowsWindows_10x86_64WindowsWindows_10x86MSVC2017qtci-windows-10-x86_64-15-f36aa5/362b9316e75597e6d1324bdcf98e2f7bde397f92/test_1581459768/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 1: Qt dev: Host Windows 10, MSVC2017 compiler
- Incident 2: Qt dev: Host macOS 10.14, Clang compiler
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.