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
{{ message }}
This repository has been archived by the owner on Dec 17, 2024. It is now read-only.
I'm encountering an issue with the latest Chrome images (119.0 and 120.0). The tests fail both locally and in a CI environment. Below, you'll find information about the error and logs:
Setup
Local setup: MacOS (Intel)
Selenoid version: aerokube/selenoid:1.11.1
Selenoid UI version: aerokube/selenoid:1.11.1
Launch parameters: cm selenoid start --force --browsers 'chrome' --last-versions 4 (using 'force' since an older version was downloaded)
Failing on: selenoid/chrome:119.0 AND selenoid/chrome:120.0
Working on selenoid/chrome:118.0 AND older versions. Also working fine with selenoid/firefox even on latest versions
Steps to reproduce
I am using wdio v7 but I also tested it using a manual session with Selenoid UI
Curl request (browserVersion could be either 119.0 or 120.0):
Since the latest versions are not working, I have to init Selenoid with --last-versions 4 so that I can pick version 118.0 using the capabilities. This approach is not very convenient as it downloads versions that I am not using. However, it ensures that in case a new image is released in the future, the tests won't fail. I haven't found a better way to instantiate specific browsers with the cm file. Moving forward, I'm considering using the Docker Compose approach creating a browsers.json file might be a better solution. I'm still exploring best practices.
Has anyone else experienced the same issue, or is it just me? I would really appreciate it if someone could take a look.
Thanks in advance!
The text was updated successfully, but these errors were encountered:
@vania-pooh yes, it seems like a Chromedriver issue since the only change that I saw in the docker image that you are building is the Chrome/Chromedriver version. Thanks for investigate it and feel free to close it if there is nothing to do on your side
Hello Team,
I'm encountering an issue with the latest Chrome images (119.0 and 120.0). The tests fail both locally and in a CI environment. Below, you'll find information about the error and logs:
Setup
aerokube/selenoid:1.11.1
aerokube/selenoid:1.11.1
cm selenoid start --force --browsers 'chrome' --last-versions 4
(using 'force' since an older version was downloaded)selenoid/chrome:119.0
ANDselenoid/chrome:120.0
selenoid/chrome:118.0
AND older versions. Also working fine withselenoid/firefox
even on latest versionsSteps to reproduce
Request Payload
{"desiredCapabilities":{"browserName":"chrome","version":"120.0","enableVNC":true,"labels":{"manual":"true"},"sessionTimeout":"60m","name":"Manual session"},"capabilities":{"alwaysMatch":{"browserName":"chrome","browserVersion":"120.0","selenoid:options":{"enableVNC":true,"sessionTimeout":"60m","labels":{"manual":"true"}}},"firstMatch":[{}]}}
Status Code:
500 Internal Server Error
Response
Container Logs
Since the latest versions are not working, I have to init Selenoid with
--last-versions 4
so that I can pick version 118.0 using the capabilities. This approach is not very convenient as it downloads versions that I am not using. However, it ensures that in case a new image is released in the future, the tests won't fail. I haven't found a better way to instantiate specific browsers with thecm
file. Moving forward, I'm considering using the Docker Compose approach creating abrowsers.json
file might be a better solution. I'm still exploring best practices.Has anyone else experienced the same issue, or is it just me? I would really appreciate it if someone could take a look.
Thanks in advance!
The text was updated successfully, but these errors were encountered: