Closed
Description
Repro steps using webdriver-manager v12.1.4
$ webdriver-manager clean
[16:54:21] I/file_manager - removed chromedriver_79.0.3945.36.exe
[16:54:21] I/file_manager - removed chromedriver_79.0.3945.36.zip
[16:54:21] I/file_manager - removed geckodriver-v0.26.0.exe
[16:54:21] I/file_manager - removed geckodriver-v0.26.0.zip
[16:54:21] I/file_manager - removed selenium-server-standalone-3.141.59.jar
[16:54:21] I/file_manager - removed chrome-response.xml
[16:54:21] I/file_manager - removed gecko-response.json
[16:54:21] I/file_manager - removed standalone-response.xml
[16:54:21] I/file_manager - removed update-config.json
$ 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 update --versions.chrome 79.0.3945.36
[16:54:38] I/config_source - curl -oC:\Users\mikek\Seeq\crab\behavior\node_modules\protractor\node_modules\webdriver-manager\selenium\standalone-response.xml https://selenium-release.storage.googleapis.com/
[16:54:38] I/config_source - curl -oC:\Users\mikek\Seeq\crab\behavior\node_modules\protractor\node_modules\webdriver-manager\selenium\chrome-response.xml https://chromedriver.storage.googleapis.com/
[16:54:38] I/config_source - curl -oC:\Users\mikek\Seeq\crab\behavior\node_modules\protractor\node_modules\webdriver-manager\selenium\gecko-response.json https://github.com/api/repos/mozilla/geckodriver/releases
[16:54:39] I/downloader - curl -oC:\Users\mikek\Seeq\crab\behavior\node_modules\protractor\node_modules\webdriver-manager\selenium/selenium-server-standalone-3.141.59.jar https://selenium-release.storage.googleapis.com/3.141/selenium-server-standalone-3.141.59.jar
[16:54:39] I/downloader - curl -oC:\Users\mikek\Seeq\crab\behavior\node_modules\protractor\node_modules\webdriver-manager\selenium/chromedriver_79.0.3945.36.zip https://chromedriver.storage.googleapis.com/79.0.3945.16/chromedriver_win32.zip
[16:54:39] I/update - chromedriver: unzipping chromedriver_79.0.3945.36.zip
[16:54:40] I/downloader - curl -oC:\Users\mikek\Seeq\crab\behavior\node_modules\protractor\node_modules\webdriver-manager\selenium/geckodriver-v0.26.0.zip https://github.com/mozilla/geckodriver/releases/download/v0.26.0/geckodriver-v0.26.0-win64.zip
[16:54:41] I/update - geckodriver: unzipping geckodriver-v0.26.0.zip
$ 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
[16:54:39] I/downloader - curl -oC:\Users\mikek\Seeq\crab\behavior\node_modules\protractor\node_modules\webdriver-manager\selenium/chromedriver_79.0.3945.36.zip https://chromedriver.storage.googleapis.com/79.0.3945.16/chromedriver_win32.zip
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 see
<Contents>
<Key>79.0.3945.16/chromedriver_win32.zip</Key>
<Generation>1572451860927405</Generation>
<MetaGeneration>1</MetaGeneration>
<LastModified>2019-10-30T16:11:00.927Z</LastModified>
<ETag>"6c36e6f2c1cb7ec0f8cb4201a7fb03e1"</ETag>
<Size>4261268</Size>
</Contents>
and
<Contents>
<Key>79.0.3945.36/chromedriver_win32.zip</Key>
<Generation>1574101206976556</Generation>
<MetaGeneration>1</MetaGeneration>
<LastModified>2019-11-18T18:20:06.976Z</LastModified>
<ETag>"9665be96d739035efdf91684f406fdcf"</ETag>
<Size>4263308</Size>
</Contents>
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.
Activity
mpkuth commentedon Jul 3, 2020
Not sure how I missed them before. This is a dupe of:
#408
#424
Sorry for the noise