Up until today, I have been using chromedriver to drive my watir-webdriver tests, and I have had no problems. My server still works and runs tests on the same version of the chromedriver and chrome.
I have tried updating to the latest chromedriver, which is the chromedriver 2 experimental build. This fails due to what I can only assume are still bugs being worked out of it.
I have also tried rolling back to the previous version of chromedriver with no success.
If anyone has any experience with this, I would really appreciate your expertise. I am sure it will turn out to be something simple I have overlooked.
gem versions:
watir-webdriver (0.6.2)
selenium-webdriver (2.29.0)
cucumber (1.2.1)
trace from the chromedriver below
Started ChromeDriver port=9517 version=26.0.1383.0
log=C:\Projects\oms_acceptance_tests\src\chromedriver.log
[6136:5300:0212/122320:ERROR:master_preferences.cc(110)] Failed to read master_preferences file at C:\Program Files (x86)\Google\Chrome\Application\master_preferences. Falling back to default preferences.
[6136:5300:0212/122320:ERROR:gpu_info_collector_win.cc(82)] Can't retrieve a valid WinSAT assessment.
test\automation\proxy_launcher.cc(107): error: Value of: app_launched
Actual: 5
Expected: AUTOMATION_SUCCESS
Which is: 0
Error while awaiting automation ping from browser process
[0212/122321:ERROR:proxy_launcher.cc(556)] Failed to ConnectToRunningBrowser
[0212/122321:ERROR:automation_proxy.cc(319)] Channel error in AutomationProxy.
Unable to either launch or connect to Chrome. Please check that ChromeDriver is up-to-date. Using Chrome binary at: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe (Selenium::WebDriver::Error::UnknownError)
I would trying downloading newer version of chromedriver. Worked for me when I experienced similar issues.
To get rid of the gpu winsat error, try to update your display adapter.
Related
I am trying to run automated tests on a repository forked from here. I haven't really worked with yarn or mocha before (or chromedriver) so I'm going off of what the instructions are saying.
I've set up Ubuntu 18.04 in wsl2 and installed google-chrome-stable and chromedriver both at version 99.0.4844.51 in /usr/bin/. I have yarn start running in one terminal and when I try actually run yarn test it gives me:
SessionNotCreatedError: session not created: This version of ChromeDriver only supports Chrome version 94
Current browser version is 99.0.4844.51 with binary path /usr/bin/google-chrome-stable
I've tried upgrading chromedriver from here to version 100.0.4896.20 but it gives me the same error saying it only supports Chrome version 94. I'm having a hard time trying to find Google version 94 for linux, and I'll be happy either way, either upgrading the chromedriver or downgrading chrome.
I am new to Robot Framework. I have used chrome version 93.0.4577.82 until yesterday and the code was working for that version. But, when I try to run the test today, it shows the following error message.
Can anyone help me with this? Thank you
Setup failed:
SessionNotCreatedException: Message: session not created: This version of ChromeDriver only supports Chrome version 92
Current browser version is 94.0.4606.54 with binary path C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
This message is raised when the Chrome and the Chrome driver version mismatch.
This means that your Chrome version is 94 and the Chrome Driver is 92.
Chrome has probably updated itself, so you should update the ChromeDriver version downloading (and installing) a new one (94).
Here the link
I started with python and Robot Framework.
I'm having this strange exception while trying to run a test case in Robot Framework.
WebDriverException: Message: Service chromedriver unexpectedly exited. Status code was: -1073741819
I tried changing the chromedriver versions, also checked the chrome browser it was updated to the last version.
I'm sure it's in it's place "Python27\Scripts" which is added to the environment variables as well.
Has anyone else had this issue, or know how to solve it?
I have inherited a JMeter performance testing script. There is a chromedriver section and an HTTPSampler section. The httpsampler section works fine. The chromedriver section runs into a problem. When I run it chrome pops up like this:
It does not move forward with any of the steps in the plan after that. Up until recently I've also been seeing the error
Error communicating with the remote browser. It may have died.
I am not seeing this now, so I don't know if it's just a difference in how the test is running or what.
The person I inherited this from was running it on a mac and did not get any of these problems. I saw it run with no errors at the same time I was getting them.
One solution I found was to add the --test-type flag to chromedriver. Unfortunately I cannot find a way to add that argument when running it through JMeter. I've tried adding both --test-type and -test-type to the end of the path to chromedriver.exe, but that did not work.
Does anyone have a solution for this?
The error might be due to conflict in chrome driver version. Please install the latest version of ChromeDriver from this link.
Latest version of Chrome Driver supports the browser version v56-58.
I'm having trouble running Selenium with chromeDriver on Windows 7. I'm getting the following error:
Jan 27, 2016 11:52:57 AM org.openqa.selenium.os.UnixProcess checkForError
SEVERE: org.apache.commons.exec.ExecuteException:
Execution failed (Exit value: -559038737. Caused by java.io.IOException:
Cannot run program "C:\testproject\target\resources\chromedriver.exe"
(in directory "."): CreateProcess error=193, %1 is not a valid Win32 application)
Double clicking the driver outside of eclipse gives a windows error (not a valid Win32 application)
Is there some trick to getting it to work on a 64bit Windows 7 environment?
Maybe the ChromeDriver download was corrupted by a network error or something, so the chromedriver.exe is incomplete! Try downloading ChromeDriver again from https://sites.google.com/chromium.org/driver/
Killing chromedriver.exe instances from command prompt worked for me.
Before deleting current chromedriver and installing new .exe, you can try executing
Taskkill /F /IM chromedriver.exe
After a bit of reading around, it seems the ChromeDriver executable needs to be on your PATH. It's not enough to just point webdriver.chrome.driver at it, as presumably other processes need to be able to find it.
See https://sites.google.com/a/chromium.org/chromedriver/getting-started (under "Help WebDriver find the downloaded ChromeDriver executable"), also https://splinter.readthedocs.org/en/0.1/setup-chrome.html.
I meet the same error today, before today the selenium run correctly. I find this error is caused by my computer antivirus software, after closing antivirus software all is well.
I got this error due to properties file not exists as i am using it to store ChromeDriver.exe path.