Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

Exiting a hydra run #46

Open
rb2k opened this issue Jun 17, 2011 · 1 comment
Open

Exiting a hydra run #46

rb2k opened this issue Jun 17, 2011 · 1 comment

Comments

@rb2k
Copy link

rb2k commented Jun 17, 2011

I'm trying to test my multi-core hydra runs locally.
Is there a way to actually exit the whole test once the worker processes have been spawned?
Using Ctrl+c will bring me back to the shell, but the spawned processes will still write logging output to stdout and the tests continue to run.

Cheers,
Marc

@ngauthier
Copy link
Owner

Hey Marc,

After you Ctrl+c the master, it closes connections to the workers. Then the
workers don't know the connection is closed until they try to read or write
from the socket. So, at the worst, they should finish up the current test.
This is the behavior in rspec too, I believe.

If the workers are continuing to run other tests, then we have a problem. If
that's the case, please run it in verbose mode (see wiki) and with only one
worker (increase to more if the problem is not occurring). Keep in mind if
you have 4 workers you will end up finishing up 4 tests after ctrl+c.

It probably makes sense for ctrl+c to be trapped in the master and have it
send shutdown notices, then wait for all the workers to shut down before
exiting. Feel free to implement :-)

-Nick

On Fri, Jun 17, 2011 at 1:12 PM, rb2k <
[email protected]>wrote:

I'm trying to test my multi-core hydra runs locally.
Is there a way to actually exit the whole test once the worker processes
have been spawned?
Using Ctrl+c will bring me back to the shell, but the spawned processes
will still write logging output to stdout and the tests continue to run.

Cheers,
Marc

Reply to this email directly or view it on GitHub:
#46

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants