Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Travis suddenly requires Chrome v72 in order to run Dusk #219

Closed
range-of-motion opened this issue Jul 23, 2020 · 3 comments
Closed

Travis suddenly requires Chrome v72 in order to run Dusk #219

range-of-motion opened this issue Jul 23, 2020 · 3 comments
Milestone
v0.7

Comments

@range-of-motion
Copy link
Owner

I have no idea why, nothing changed on our end.
@range-of-motion
Copy link
Owner Author

There are multiple solutions, but I guess using the recommended settings from the Laravel documentation work best here. Also, let's upgrade to PHP 7.3.

@range-of-motion range-of-motion added this to the v0.7 milestone Jul 23, 2020
@range-of-motion
Copy link
Owner Author

Quick recap: Travis CI is weird.

The same configuration works one day, and fails another. ChromeDriver v85 worked fine half an hour ago, and now I have to use v84 all of a sudden. Whatever, it works.

@range-of-motion
Copy link
Owner Author

Fixed in #220.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v0.7
Development

No branches or pull requests
1 participant
@range-of-motion