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.

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

Make Chromedriver escript Compatible #496

Conversation

alecho
Copy link

@alecho alecho commented Dec 15, 2019

Thanks to @aaronrenner for the solution in #193 which is being used again here.

Fixes #495

@alecho alecho force-pushed the 495-make-chromedriver-escript-compatible branch from 8b9936a to b17b3bc Compare December 15, 2019 14:50
@aaronrenner
Copy link
Member

@alecho Thanks so much for the PR! ❤️

Unfortunately, I just tested this on Mac OS 10.14.6 and it doesn't seem to close the chromedriver OS process when the test suite is finished. You can recreate this issue by:

  1. Open Activity monitor and search for ChromeDriver
  2. Run WALLABY_DRIVER=chrome mix test
  3. Either let the test suite finish, or press Ctrl+C Ctrl+C to kill it
  4. Note that the chromedriver process is still running

This is an issue we've had with phantom as well and may need to revisit it. If you have ideas in this area, we'd certainly appreciate the help.

@alecho
Copy link
Author

alecho commented Dec 16, 2019

Just checked my machine and I see that behavior as well. I'll take a look into this. The other times I've used Port I was able to rely on the OS process responding to STDIN closing.

@mhanberg mhanberg closed this Dec 4, 2020
@mhanberg mhanberg deleted the branch elixir-wallaby:master December 4, 2020 05:34
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.

Make Chromedriver escript Compatible
3 participants