Closed GoogleCodeExporter closed 9 years ago
Yes me too facing same issue..
From past 2-3 days it was working fine, suddenly its start failing, throwing
exception:
[testng] E:\work\Workforce\SECURITY_ADMIN_Test_Suite.xml
[testng]
[testng] Starting ChromeDriver (v2.9.248315) on port 5335
[testng] log4j:WARN No appenders could be found for logger (org.apache.http.client.protocol.RequestAddCookies).
[testng] log4j:WARN Please initialize the log4j system properly.
[testng] [21.197][SEVERE]: Unable to receive message from renderer
[testng] Starting ChromeDriver (v2.9.248315) on port 27560
[testng] [601.633][SEVERE]: Timed out receiving message from renderer: 600.000
[testng] Starting ChromeDriver (v2.9.248315) on port 35183
Original comment by rock.ban...@gmail.com
on 29 Oct 2014 at 11:25
Were you using RemoteWebdriver or Chromedriver ?
Original comment by gibralto...@gmail.com
on 29 Oct 2014 at 11:53
[deleted comment]
I am using chromedriver.
Original comment by rock.ban...@gmail.com
on 29 Oct 2014 at 1:41
I am experencing the issue, when I run my tests from my local box (MAC) using
my grid box (MAC), there are no issues; however, when I use the same
setup/tests from Jenkins to the same grid box, the browser opens then nothing
happens (no url) then closes.
Chrome Browser 38
Chromedriver 12
Selenium version 2.44.0
Jenkins Server - Linux
Jenkins ver. 1.585
Original comment by shawnkni...@gmail.com
on 30 Oct 2014 at 3:11
Could confirm. Tests started to fail with message similar as in OP's
Chrome 38.0.2125.111
Chromedriver 2.12
Selenium 2.42.1
Jenkins 1.587
Windows 7 x64
Original comment by azamal...@gmail.com
on 1 Nov 2014 at 7:52
Original comment by andrewch...@chromium.org
on 1 Dec 2014 at 10:46
During these period, any update of either chrome or chromedriver?
Original comment by andrewch...@chromium.org
on 1 Dec 2014 at 10:47
I believe this has already been resolved by the fix in
https://code.google.com/p/chromium/issues/detail?id=422218
Original comment by azamal...@gmail.com
on 2 Dec 2014 at 12:52
Original comment by andrewch...@chromium.org
on 2 Dec 2014 at 1:57
Original comment by samu...@chromium.org
on 21 Feb 2015 at 12:26
Original issue reported on code.google.com by
gibralto...@gmail.com
on 21 Oct 2014 at 5:04