-
Notifications
Y 8000 ou must be signed in to change notification settings - Fork 243
When tests fail, they leave external processes running (e.g.: hipache, redis, memcached, etcd) #195
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
Comments
Ditto for
|
Ditto for
|
Is this related to the fact that the process seems to exit right away when it hits the first error? I.e.: I don't see all the failures at once only the first one. Is there a way to get it to keep going on an error so that it can report all the test results and then clean up? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that the tests don't clean up after themselves properly? At least perhaps when they fail?
Note that after the tests fail below, they have left
hipache
andmemcached
processes running.Note that after the tests fail above, they have left
hipache
andmemcached
processes running.If I run the tests again, they will fail because of these stray processes.
The text was updated successfully, but these errors were encountered: