You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ webdriver-manager status
[16:54:30] I/status - selenium standalone is not present
[16:54:30] I/status - chromedriver is not present
[16:54:30] I/status - geckodriver is not present
[16:54:30] I/status - IEDriverServer is not present
[16:54:30] I/status - android-sdk is not present
[16:54:30] I/status - appium is not present
$ webdriver-manager status
[16:57:46] I/status - selenium standalone version available: 3.141.59 [last]
[16:57:46] I/status - chromedriver version available: 79.0.3945.36 [last]
[16:57:46] I/status - geckodriver version available: v0.26.0 [last]
[16:57:46] I/status - IEDriverServer is not present
[16:57:46] I/status - android-sdk is not present
[16:57:46] I/status - appium is not present
The problem is indicated in the following output line during the update
and the size of node_modules/protractor/node_modules/selenium/chromedriver_79.0.3945.36.zip is "4,261,268 bytes" which matches the 79.0.3945.16 entry of chrome-response.xml. I also see Driver info: chromedriver=79.0.3945.16... in test failure output. So I'm confident that the mix-up is not just in the console output.
The text was updated successfully, but these errors were encountered:
Repro steps using webdriver-manager v12.1.4
The problem is indicated in the following output line during the update
It is downloading version 79.0.3945.16 and saving it as the requested version 79.0.3945.36.
In
node_modules/protractor/node_modules/selenium/chrome-response.xml
I seeand
and the size of
node_modules/protractor/node_modules/selenium/chromedriver_79.0.3945.36.zip
is "4,261,268 bytes" which matches the 79.0.3945.16 entry ofchrome-response.xml
. I also seeDriver info: chromedriver=79.0.3945.16...
in test failure output. So I'm confident that the mix-up is not just in the console output.The text was updated successfully, but these errors were encountered: