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
Process forking causing cuprite/ferrum to never exit #231
Comments
Same thing happens to me.. Here's what I did to kill the pid at least until we can figure out what needs to get updated in cuprite. Capybara / Cuprite / RSpec
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here's a scenario where cuprite/ferrum does not exit and the test hangs indefinitely. We've written some concurrency/race-condition tests in our application that involves forking processes. This is resulting in our test suite hanging, and it looks like it may be related to cuprite/ferrum not stopping the browser process. Here is a simple reproduction case:
When run this will not exit. I can see that the Chrome browser process is still active in my activity monitor. If I kill the browser, the runner exits.
Note this repro case is in test-unit, but we're seeing this issue in RSpec with the process forking happening in a model spec entirely separate from any cuprite-driven feature specs.
The text was updated successfully, but these errors were encountered: