2014-10-17 179 views
10

我们在我们的构建服务器上安装了teamcity记者的karma。它正在通过Chrome,Firefox和IE进行单元测试,一切都很顺利。然后昨天我注意到Chrome未能报告。 IE和Firefox仍在连接并运行所有单元测试,但由于某种原因,业力无法与Chrome建立连接,因此在60秒后超时并且构建步骤失败。从团队城市运行业力。 Chrome Testrunner无法启动

真奇怪的是,我可以登录到构建服务器,并从命令行运行罚款没有问题。测试运行(并且它们非常快)。

因缘开始--reporters的TeamCity --single运行--log级错误--browsers = IE,火狐,Chrome

下面是从TeamCity的构建日志。有没有人有线索发生了什么?正如你可以看到firefox和即时报告,但铬每次都落在它的脸上。我感谢您可能提供的任何帮助。

[16:16:39][Step 2/5] [36mDEBUG [config]: [39mLoading config C:\TCBuildConf\01-OpSuiteDev\02-codebase\Website\OpSuite.MobileWeb\Client\unit_tests\karma.conf.js 
[16:16:39][Step 2/5] [36mDEBUG [config]: [39mautoWatch set to false, because of singleRun 
[16:16:39][Step 2/5] [36mDEBUG [plugin]: [39mLoading karma-* from C:\Users\administrator.OPSUITE\AppData\Roaming\npm\node_modules 
[16:16:39][Step 2/5] [36mDEBUG [plugin]: [39mLoading plugin C:\Users\administrator.OPSUITE\AppData\Roaming\npm\node_modules/karma-chrome-launcher. 
[16:16:39][Step 2/5] [36mDEBUG [plugin]: [39mLoading plugin C:\Users\administrator.OPSUITE\AppData\Roaming\npm\node_modules/karma-firefox-launcher. 
[16:16:39][Step 2/5] [36mDEBUG [plugin]: [39mLoading plugin C:\Users\administrator.OPSUITE\AppData\Roaming\npm\node_modules/karma-ie-launcher. 
[16:16:39][Step 2/5] [36mDEBUG [plugin]: [39mLoading plugin C:\Users\administrator.OPSUITE\AppData\Roaming\npm\node_modules/karma-jasmine. 
[16:16:39][Step 2/5] [36mDEBUG [plugin]: [39mLoading plugin C:\Users\administrator.OPSUITE\AppData\Roaming\npm\node_modules/karma-teamcity-reporter. 
[16:16:39][Step 2/5] [32mINFO [karma]: [39mKarma v0.12.16 server started at http://localhost:7357/ 
[16:16:39][Step 2/5] [32mINFO [launcher]: [39mStarting browser IE 
[16:16:39][Step 2/5] [36mDEBUG [temp-dir]: [39mCreating temp dir at C:\TeamCity\buildAgent\temp\buildTmp\karma-43795558 
[16:16:39][Step 2/5] [36mDEBUG [launcher]: [39mC:\Program Files\Internet Explorer\iexplore.exe -extoff http://localhost:7357/?id=43795558 
[16:16:39][Step 2/5] [32mINFO [launcher]: [39mStarting browser Firefox 
[16:16:39][Step 2/5] [36mDEBUG [temp-dir]: [39mCreating temp dir at C:\TeamCity\buildAgent\temp\buildTmp\karma-44455821 
[16:16:39][Step 2/5] [36mDEBUG [launcher]: [39mC:\Program Files (x86)\Mozilla Firefox\firefox.exe http://localhost:7357/?id=44455821 -profile C:\TeamCity\buildAgent\temp\buildTmp\karma-44455821 -no-remote 
[16:16:39][Step 2/5] [32mINFO [launcher]: [39mStarting browser Chrome 
[16:16:39][Step 2/5] [36mDEBUG [temp-dir]: [39mCreating temp dir at C:\TeamCity\buildAgent\temp\buildTmp\karma-28976911 
[16:16:39][Step 2/5] [36mDEBUG [launcher]: [39mC:\Program Files (x86)\Google\Chrome\Application\chrome.exe --user-data-dir=C:\TeamCity\buildAgent\temp\buildTmp\karma-28976911 --no-default-browser-check --no-first-run --disable-default-apps --disable-popup-blocking --disable-translate http://localhost:7357/?id=28976911 
[16:16:39][Step 2/5] [36mDEBUG [watcher]: [39mResolved files: 
[16:16:42][Step 2/5] [36mDEBUG [karma]: [39mA browser has connected on socket WNLvjHxwETp4In9uP7A6 
[16:16:42][Step 2/5] [32mINFO [IE 11.0.0 (Windows 7)]: [39mConnected on socket WNLvjHxwETp4In9uP7A6 with id 43795558 
[16:16:42][Step 2/5] [36mDEBUG [launcher]: [39mIE (id 43795558) captured in 2.943 secs 
[16:16:42][Step 2/5] [36mDEBUG [launcher]: [39mKilled extra IE process 652 
[16:16:42][Step 2/5] [36mDEBUG [launcher]: [39mProcess IE exited with code 0 
[16:16:42][Step 2/5] [36mDEBUG [temp-dir]: [39mCleaning temp dir C:\TeamCity\buildAgent\temp\buildTmp\karma-43795558 
[16:16:59][Step 2/5] [36mDEBUG [karma]: [39mA browser has connected on socket 4O99QMVW24pEsJBGP7A7 
[16:16:59][Step 2/5] [32mINFO [Firefox 32.0.0 (Windows 7)]: [39mConnected on socket 4O99QMVW24pEsJBGP7A7 with id 44455821 
[16:16:59][Step 2/5] [36mDEBUG [launcher]: [39mFirefox (id 44455821) captured in 20.586 secs 
[16:17:00][Step 2/5] [36mDEBUG [launcher]: [39mProcess Firefox exited with code 0 
[16:17:00][Step 2/5] [36mDEBUG [temp-dir]: [39mCleaning temp dir C:\TeamCity\buildAgent\temp\buildTmp\karma-44455821 
[16:17:39][Step 2/5] [33mWARN [launcher]: [39mChrome have not captured in 60000 ms, killing. 
[16:17:39][Step 2/5] [36mDEBUG [launcher]: [39mProcess Chrome exited with code 0 
[16:17:39][Step 2/5] [36mDEBUG [temp-dir]: [39mCleaning temp dir C:\TeamCity\buildAgent\temp\buildTmp\karma-28976911 
[16:17:39][Step 2/5] [32mINFO [launcher]: [39mTrying to start Chrome again (1/2). 
[16:17:39][Step 2/5] [36mDEBUG [launcher]: [39mRestarting Chrome 
[16:17:39][Step 2/5] [36mDEBUG [temp-dir]: [39mCreating temp dir at C:\TeamCity\buildAgent\temp\buildTmp\karma-28976911 
[16:17:39][Step 2/5] [36mDEBUG [launcher]: [39mC:\Program Files (x86)\Google\Chrome\Application\chrome.exe --user-data-dir=C:\TeamCity\buildAgent\temp\buildTmp\karma-28976911 --no-default-browser-check --no-first-run --disable-default-apps --disable-popup-blocking --disable-translate http://localhost:7357/?id=28976911 
[16:18:39][Step 2/5] [33mWARN [launcher]: [39mChrome have not captured in 60000 ms, killing. 
[16:18:39][Step 2/5] [36mDEBUG [launcher]: [39mProcess Chrome exited with code 0 
[16:18:39][Step 2/5] [36mDEBUG [temp-dir]: [39mCleaning temp dir C:\TeamCity\buildAgent\temp\buildTmp\karma-28976911 
[16:18:40][Step 2/5] [32mINFO [launcher]: [39mTrying to start Chrome again (2/2). 
[16:18:40][Step 2/5] [36mDEBUG [launcher]: [39mRestarting Chrome 
[16:18:40][Step 2/5] [36mDEBUG [temp-dir]: [39mCreating temp dir at C:\TeamCity\buildAgent\temp\buildTmp\karma-28976911 
[16:18:40][Step 2/5] [36mDEBUG [launcher]: [39mC:\Program Files (x86)\Google\Chrome\Application\chrome.exe --user-data-dir=C:\TeamCity\buildAgent\temp\buildTmp\karma-28976911 --no-default-browser-check --no-first-run --disable-default-apps --disable-popup-blocking --disable-translate http://localhost:7357/?id=28976911 
[16:19:40][Step 2/5] [33mWARN [launcher]: [39mChrome have not captured in 60000 ms, killing. 
[16:19:40][Step 2/5] [36mDEBUG [launcher]: [39mProcess Chrome exited with code 0 
[16:19:40][Step 2/5] [36mDEBUG [temp-dir]: [39mCleaning temp dir C:\TeamCity\buildAgent\temp\buildTmp\karma-28976911 
[16:19:40][Step 2/5] Process exited with code 1 
+0

我看到我们的构建服务器上的一个类似的问题,虽然我们使用哈德森。当我尝试本地构建时,Chrome没有启动问题,但最终在测试和源文件上失败了一年多。本地构建中的错误遵循以下模式:'TypeError:无法分配给只读属性...' 如果我使用Firefox而不是Chrome,则不会发生这种情况。 – 2014-10-17 19:44:37

+1

我们最近在团队城市也看到了这个问题。我们将尝试在此处验证旧版本:http://www.oldapps.com/google_chrome.php – 2014-10-21 17:35:35

+0

我们决定无路可走,转而使用PhantomJS。 – 2014-10-21 18:59:00

回答

0

这是铬合金的最新版本的铬错误。 问题似乎是从服务启动chrome。 铬球队有固定的问题,它会被包含在下一版本中这大约是11月20日预计2014年

issue tracker