Skip to content

workaround for selenium standalone chrome issues #1704

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

Merged

Conversation

johnyb
Copy link
Contributor

@johnyb johnyb commented Jun 7, 2019

for some reason, using latest chrome fails the webdriver tests.
Stick to a version of selenium standalone + chrome which is known to work.

@johnyb
Copy link
Contributor Author

johnyb commented Jun 7, 2019

As requested in #1701 (comment) - this should make the pipeline green, again. I still haven't found the root cause of this nor an issue in WebDriverIO, Chromedriver or any other component to track.

for some reason, using latest Chrome fails the webdriver tests.
Stick to a version of Selenium standalone + Chrome which is known to work.
@johnyb johnyb force-pushed the workaround_chrome_update_issues branch from fb066ee to 1401615 Compare June 7, 2019 09:23
@DavertMik
Copy link
Contributor

Thank you! This should be it!

@DavertMik DavertMik merged commit 6b86538 into codeceptjs:master Jun 7, 2019
@johnyb johnyb deleted the workaround_chrome_update_issues branch October 18, 2019 23:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants