Details
-
Bug
-
Resolution: Invalid
-
P3: Somewhat important
-
None
-
dev, 5.13
-
None
Description
While running tests on qtbase on either macOS 10.12 or 10.13, qnetworkreply crashes the CI agent:
agent:2019/01/31 13:51:27 build.go:449: Executing instruction 645 of 1082 - RunQtUnitTest agent:2019/01/31 13:51:27 runner.go:72: Generating test results with TESTARGS=-o /Users/qt/work/testresults/tests/auto/network/access/qnetworkreply/test245222432,xml -o -,txt agent:2019/01/31 13:51:27 build.go:314: [make check -j1] 900 900 agent:2019/01/31 13:51:27 build.go:192: testserver: docker-compose version 1.20.1, build 5d8c71b 2019-01-31 13:52:06,017 WARNING: The same agent (1550312874-3309, RpcServiceAddress(hostName='10.225.251.67', port=49161)), called agentLaunched twice, that should not happen, forcefully restarting this workitem (qt/qtbase/b1ded62ec4ce8bebf7204866aae960b563d169bf/MacOSMacOS_10_12x86_64MacOSMacOS_10_12x86_64Clangqtci-macos-10.12-x86_64-9-b5aed7DeveloperBuild_NoFramework_Release_QtNamespace_NoPch/2a48a3b7dcb9652b1532a3ad14de7580b5b9b1ee/Test) 2019-01-31 13:52:06,018 INFO: Agent 1550312874-3309 running 10.225.251.67:49161 (buildKey: qt/qtbase/b1ded62ec4ce8bebf7204866aae960b563d169bf/MacOSMacOS_10_12x86_64MacOSMacOS_10_12x86_64Clangqtci-macos-10.12-x86_64-9-b5aed7DeveloperBuild_NoFramework_Release_QtNamespace_NoPch/2a48a3b7dcb9652b1532a3ad14de7580b5b9b1ee/Test) 2019-01-31 13:52:06,023 ERROR: Agent 1550312874-3309 is in an invalid state: The same agent (1550312874-3309, RpcServiceAddress(hostName='10.225.251.67', port=49161)), called agentLaunched twice, that should not happen, forcefully restarting this workitem (qt/qtbase/b1ded62ec4ce8bebf7204866aae960b563d169bf/MacOSMacOS_10_12x86_64MacOSMacOS_10_12x86_64Clangqtci-macos-10.12-x86_64-9-b5aed7DeveloperBuild_NoFramework_Release_QtNamespace_NoPch/2a48a3b7dcb9652b1532a3ad14de7580b5b9b1ee/Test), buildKey qt/qtbase/b1ded62ec4ce8bebf7204866aae960b563d169bf/MacOSMacOS_10_12x86_64MacOSMacOS_10_12x86_64Clangqtci-macos-10.12-x86_64-9-b5aed7DeveloperBuild_NoFramework_Release_QtNamespace_NoPch/2a48a3b7dcb9652b1532a3ad14de7580b5b9b1ee/Test, will try another agent 2019-01-31 13:52:06,024 WARNING: Requesting new agent since there seem to be issues with the original one.
The "agent launched twice" messages are caused by the agent catching run-time panic and being relaunched by the bootstrap agent. The error continues until running timeout is reached (9+ hours).
https://testresults.qt.io/coin/integration/qt/qt5/tasks/1550362095
https://testresults.qt.io/coin/integration/qt/qtbase/tasks/1550317769
agent:2019/02/05 09:12:10 build.go:192: PASS : tst_QNetworkRequest::cleanupTestCase() agent:2019/02/05 09:12:10 build.go:192: Totals: 89 passed, 0 failed, 0 skipped, 0 blacklisted, 15ms agent:2019/02/05 09:12:10 build.go:192: ********* Finished testing of tst_QNetworkRequest ********* agent:2019/02/05 09:12:10 build.go:655: agent:2019/02/05 09:12:10 build.go:449: Executing instruction 610 of 982 - SetExecutionPhaseName agent:2019/02/05 09:12:10 build.go:655: agent:2019/02/05 09:12:10 build.go:449: Executing instruction 611 of 982 - RunQtUnitTest agent:2019/02/05 09:12:10 runner.go:72: Generating test results with TESTARGS=-o C:\Users\qt\work\testresults\tests\auto\network\access\qnetworkreply\test630580202,xml -o -,txt agent:2019/02/05 09:12:10 build.go:314: [c:\users\qt\MSVC2017.bat jom check] 900 900 agent:2019/02/05 09:12:10 build.go:192: agent:2019/02/05 09:12:10 build.go:192: C:\Users\qt\work\qt\qtbase\tests\auto\network\access\qnetworkreply\test>call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professio nal\VC\Auxiliary\Build\vcvarsall.bat" amd64 agent:2019/02/05 09:12:11 build.go:192: ********************************************************************** agent:2019/02/05 09:12:11 build.go:192: ** Visual Studio 2017 Developer Command Prompt v15.4.0 agent:2019/02/05 09:12:11 build.go:192: ** Copyright (c) 2017 Microsoft Corporation agent:2019/02/05 09:12:11 build.go:192: ********************************************************************** agent:2019/02/05 09:12:12 build.go:192: [vcvarsall.bat] Environment initialized for: 'x64' agent:2019/02/05 09:12:12 build.go:192: agent:2019/02/05 09:12:12 build.go:192: jom 1.1.2 - empower your cores agent:2019/02/05 09:12:12 build.go:192: agent:2019/02/05 09:12:12 build.go:192: C:\Utils\Jom\jom.exe -f Makefile.Release check agent:2019/02/05 09:12:12 build.go:192: echo docker-compose version 1.20.1, build 5d8c71b2 && PowerShell -noprofile if ([String]::IsNullOrEmpty("\"C:/Users/qt/work/qt/qtba se/tests/testserver/docker-compose-for-windows.yml\"")) {Write-Error "\"Project variable 'TESTSERVER_COMPOSE_FILE' is not set\""} && PowerShell -noprofile if (!(docker-machine ls -q --filter Name=^qt-test-server$)) {Write-Error "\"Docker machine qt-test-server not found\""} && PowerShell -noprofile if (!(docker-machine ls -q --filter State=Running --filter Name=^qt-test-server$)) {docker-machine start qt-test-server; docker-machine regenerate-certs -f qt-test-server} && PowerShell -noprofile if (!(docker (docker-machine config qt-t est-server) images -aq qt-test-server-*)) {Write-Error "\"Docker image qt-test-server-* not found\""} agent:2019/02/05 09:12:12 build.go:192: docker-compose version 1.20.1, build 5d8c71b2 agent:2019/02/05 09:12:18 build.go:192: Starting "qt-test-server"... agent:2019/02/05 09:12:18 build.go:192: (qt-test-server) Check network to re-create if needed... agent:2019/02/05 09:12:18 build.go:192: (qt-test-server) Windows might ask for the permission to configure a dhcp server. Sometimes, such confirmation window is minimized in the t askbar. 2019-02-05 09:13:11,268 WARNING: The same agent (1550366700-2743, RpcServiceAddress(hostName='10.225.248.82', port=49701)), called agentLaunched twice, that should not happen, forcefully restarting this workitem (qt/qtbase/a8c298bf574aaaa24860f490a6a762f00b58047b/WindowsWindows_10x86_64WindowsWindows_10x86_64MSVC2017qtci-windows-10-x86_64-10-141e7aDebugAndRelease_Release_ForceDebugInfo_OpenGLDynamic/2a48a3b7dcb9652b1532a3ad14de7580b5b9b1ee/Test)
Attachments
Issue Links
- is duplicated by
-
COIN-237 The same agent called agentLaunched twice
- Open
- relates to
-
COIN-49 Agent takes too much time to recover from run-time panic
- Closed
-
QTQAINFRA-2801 Docker causes agent process to crash during provisioning
- Closed
- resulted in
-
QTQAINFRA-2882 Update firmware of build hosts
- Closed