rspec users - Jul 2011 - does anyone's rspec actually exit on the first ^C?

So, you start running your (full and long) rspec suite (before a checkin),
and you realize you [forgot to migrate test|didn''t add some config
value|missed a curly brace].

You hit Ctrl+C and get this mesage
Exiting... Interrupt again to exit immediately.
Then the tests march on.

My question is, does anyone''s rspec actually exit after that?  I
invariably
have to hit Ctrl+C a second time to get it to exit.  If I don''t, rspec
will
finish the suite.  It does not appear to be exiting.

I guess I''m asking if this is abnormal?  Will rspec actually exit on
its own
on some conditions after the first Ctrl+C?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/rspec-users/attachments/20110729/527ba6b6/attachment.html>

On Jul 29, 2011, at 11:52 AM, John Hinnegan wrote:
> So, you start running your (full and long) rspec suite (before a checkin),
and you realize you [forgot to migrate test|didn''t add some config
value|missed a curly brace].
> 
> You hit Ctrl+C and get this mesage
> Exiting... Interrupt again to exit immediately.
> Then the tests march on.
When you hit CTRL-C the first time, it removes all examples that
haven''t yet run from the queue, but lets the currently running example
finish out. That way all the after hooks run so files are cleaned up,
transactions rolled back, etc. i.e. you leave the system in a good state.

The 2nd time it just exits, but then you risk leaving things in a bad state.

Are you sure it''s running more examples after the initial CTRL-C? Is it
possible that you''re just hitting it on a long-running example?
> My question is, does anyone''s rspec actually exit after that?  I
invariably have to hit Ctrl+C a second time to get it to exit.  If I
don''t, rspec will finish the suite.  It does not appear to be exiting.
> 
> I guess I''m asking if this is abnormal?  Will rspec actually exit
on its own on some conditions after the first Ctrl+C?