Closed kay-o closed 4 years ago
I haven't noticed any issues with it last time I was running my Behat tests in Drupal VM, but I think I was using the Chrome integration and maybe not Selenium/webdriver...
Yeah, I started using headless Chrome (see https://github.com/geerlingguy/drupal-vm/issues/1598#issuecomment-370532267 )—and probably recommend that over using selenium, since the upstream role this project uses hasn't been touched since March 2018...
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.
Issue Type
Bug Report / Support Request
Your Environment
Your OS
macOS Mojave 10.14.6
Your version of Drupal-VM
cloned today; on master branch
Full console output
https://gist.github.com/kay-o/620c576457ccb092ca9f4fdc05981efd
Summary
Selenium would not start out of the box. Gist shows how I got it to start. I don't have a clear enough understanding of the various ins-and-outs to know whether this report is something that needs to be 'fixed' or if it just ends up being useful for others (me in the future) who run into it.
diff of config.yml