-
Notifications
You must be signed in to change notification settings - Fork 458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chromedriver download URLs were changed starting from chromedriver 115. Need to update bzt accordingly. #1753
Comments
@havja Hi there, could you please check this issue with the chromedriver download functionality? |
Thanks for bringing this up, we will check the issue. |
Hello Team, |
@eljivarughese the best workaround so far is to download the needed chromedriver manually corresponding to your platform from here: https://googlechromelabs.github.io/chrome-for-testing And then add to your .yml file the following section:
|
@havja any updates? Could you please assign this ticket to the appropriate team to triage? |
I contacted the appropriate team to look into this issue. |
Hi I did this
And it correctly download latest driver 116XX but when it start run -fails
showing error this version of chrome driver only support version
Please see logs
RunPerformanceTests
========================================
Running tests for pmi1
Running tests for -o settings.env.USERNAME tests/pmi1.yml
12:03:24 INFO: Taurus CLI Tool v1.16.24
12:03:24 INFO: Starting with configs:
['C:\\Users\\elji.varughese\\.bzt-rc', 'tests/pmi1.yml']
12:03:24 INFO: Configuring...
12:03:24 INFO: Proxy settings not set
12:03:24 INFO: Artifacts dir:
C:\Taursu\Harmoni.Client.PerformanceMonitoring\results\pmi
12:03:24 INFO: Preparing...
12:03:24 INFO: Using StandardLocalMonitor for engine health
monitoring*12:03:25 INFO: Latest stable version of chromedriver is
114.0.5735.90**12:03:25 INFO: Used version of chromedriver is
116.0.5845.96*
12:03:25 INFO: Latest stable version of geckodriver is 0.33.0
12:03:25 INFO: Used version of geckodriver is 0.33.0
12:03:30 WARNING: Failed to check for updates, server returned 5xx.
12:03:30 INFO: Starting...
12:03:30 INFO: Waiting for results...
DevTools listening on
ws://127.0.0.1:58711/devtools/browser/cadd8f09-e81e-42c4-b8a1-c7b71090ec64
12:03:39 WARNING: Please wait for graceful shutdown...
12:03:39 INFO: Shutting down...
12:03:40 INFO: Post-processing...
12:03:40 INFO: Test duration: 0:00:10
12:03:40 INFO: Samples count: 1, 100.00% failures
12:03:40 INFO: Average times: total 3.731, latency 0.000, connect 0.000
12:03:40 INFO: Percentiles:
+---------------+---------------+
| Percentile, % | Resp. Time, s |
+---------------+---------------+
| 0.0 | 3.73 |
| 50.0 | 3.73 |
| 90.0 | 3.73 |
| 95.0 | 3.73 |
| 99.0 | 3.73 |
| 99.9 | 3.73 |
| 100.0 | 3.73 |
+---------------+---------------+
12:03:40 INFO: Request label stats:
+----------------+--------+-------+--------+---------------------------------------------------------------------------------------------+
| label | status | succ | avg_rt | error
|
+----------------+--------+-------+--------+---------------------------------------------------------------------------------------------+
| test_dashboard | FAIL | 0.00% | 3.731 *| Message: session not
created: This version of ChromeDriver only supports Chrome version
114* |
Regards
Elji
…On Thu, Sep 7, 2023 at 8:47 PM Alex Metelytsia ***@***.***> wrote:
@eljivarughese <https://github.com/eljivarughese> the best workaround so
far is to download the needed chromedriver manually corresponding to your
platform from here: https://googlechromelabs.github.io/chrome-for-testing
And then add to your .yml file the following section:
modules:
selenium:
chromedriver:
path: /full/path/to/driver
—
Reply to this email directly, view it on GitHub
<#1753 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHJFXYHOFZUWGCJX32QCH4DXZGC3LANCNFSM6AAAAAA3VIJRZQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Regards
ELJI.T.VARUGHESE
|
please, try new taurus version 1.16.25 |
Fixed with 1.16.25 version of bzt. |
As announced on https://chromedriver.chromium.org/ :
Starting with M115 the latest Chrome + ChromeDriver releases per release channel (Stable, Beta, Dev, Canary) are available at the Chrome for Testing availability dashboard. For automated version downloading one can use the convenient JSON endpoints.
So URL https://chromedriver.storage.googleapis.com/LATEST_RELEASE is not valid anymore and will always return 114 version, while in reality, the latest stable chromedriver version is already 116.
Here is a link to the new endpoints: https://github.com/GoogleChromeLabs/chrome-for-testing#json-api-endpoints
So bzt is not able to install chromedriver 115 or higher.
Need to adjust chromedriver download logic according to new changes.
The text was updated successfully, but these errors were encountered: