Open GoogleCodeExporter opened 9 years ago
Hello,
This issue has appeared on our environment as well since 15th October. It seems
that the problem is related to the new Chrome version.
The issue is reproducible with the following chromedriver versions - 7 / 8 / 9
/ 10 /11. I haven`t tried with the ones before 7.
I have tried with the latest Chrome Beta version (39....) and the issue is
reproducible as well.
Selenium Hub / Nodes are setup as a windows service. The following guide was
followed -
http://brantleytec.blogspot.com/2012/11/selenium-hub-and-node-as-windows-service
.html.
Workaround - stop the service / create autologin / add a bat script which will
start the selenium node on startup.
Original comment by Stanoev....@gmail.com
on 20 Oct 2014 at 4:44
[deleted comment]
Hello and thanks for your feedback.
I'm not running Selenium Hub / Nodes as a windows service, but as a task
scheduled by Windows Task Scheduler with option "run whether user is logged in
or not" checked up. I guess, still, the root cause is the same: in both cases
it tries to run Chrome in non-interactive way. And it fails.
I cannot turn on autologin because in my Windows 7 Enterprise there is no such
option for security reasons (the machine is on a domain):
http://answers.microsoft.com/en-us/windows/forum/windows_7-security/windows-7-au
to-login-without-the-users-must-enter/d8a23f48-6333-4def-9d5c-8dae444f8093
The workaround I found is to register a task to be scheduled on user logon (not
on system startup) and check up the "run when user is logged in" option. This
is far from perfect because it requires an additional manual step (log in) each
time a machine is restarted but it works.
Original comment by mgawine...@gmail.com
on 21 Oct 2014 at 2:46
Hello,
Today I got latest version of Chrome exe V 2.12 and Standalone server 2.44, and
we started facing same issue. Everything works when we run Standalone Hub and
Node manually but when we run them using task scheduler then nothing works.
Please update if someone found solution related to this issue.
Original comment by praveent...@gmail.com
on 31 Oct 2014 at 11:00
Hello,
I am also facing the same issue, when I try to run my Selenium tests from the
task scheduler. It works perfectly fine when I run them manually. Can any one
suggest a older version of chrome that might work.. ?
Thanks,
Barkha
Original comment by mbar...@gmail.com
on 31 Oct 2014 at 9:16
Hi all,
I'm experiencing the exact same issues!
Successful:
- Executed Selenium node manually (node command process in foreground)
- Run parallel tests in Chrome
- All tests run without issues
Fail:
- Executed Selenium node remotely (node command process in BACKGROUND)
- Run parallel tests in Chrome
- Tests hang and then eventually fail
- HOWEVER
- This only happens when I try to run more than TWO tests in parallel
- If I run 1 or 2 tests in parallel, the tests execute without any issues
- If I so much as run 3 tests in parallel, the tests hang and fail...
Bit of a frustrating issue, this...
Any ideas or temporary workarounds?
Thanks,
Nathan
Original comment by tnfola...@gmail.com
on 7 Jan 2015 at 6:30
Original comment by samu...@chromium.org
on 21 Feb 2015 at 12:18
issue looks similar to
https://code.google.com/p/chromium/issues/detail?id=422218#c39.
This issue is not reproducible with latest chrome version '41.0.2272.89'.
please try with latest version and let us know if we differ from what you are
doing.
Original comment by ssudunag...@chromium.org
on 12 Mar 2015 at 6:42
Attachments:
Original comment by ssudunag...@chromium.org
on 26 Mar 2015 at 6:30
Original issue reported on code.google.com by
mgawine...@gmail.com
on 20 Oct 2014 at 11:51