-
Notifications
You must be signed in to change notification settings - Fork 561
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
Guard/Spork error in Simplecov 0.8.1 and up #262
Comments
I have this issue too. |
Oh boy, development is hard :( |
I have this issue too; Coverage report generated for RSpec to /home/aysar/Downloads/gowashly/tmp/coverage. 218 / 618 LOC (35.28%) covered. |
…error no longer appears in guard
👍 just ran into this.
|
Is this still an issue in the |
The following issue seems to have been introduced for me in the changes to the
at_exit block
in PR #213. Previously the old code would assign@exit_status
tonil
if neitherSimpleCov::ExitCodes::MINIMUM_COVERAGE
orSimpleCov::ExitCodes::MAXIMUM_COVERAGE_DROP
were set. This meant that theexit
call at the bottom would not be called.Now since
@exit_status
is always set it will always callexit
which is causing the below exception when run using guard/spork. No errors are thrown when run normally from the consoleIm not sure wether this is a simplecov issue or one of the other gems but should simplecov call
exit!
instead at the end to terminate the process immediately or not callexit
again if the status hasn't changed from the one passed in so theat_exit
continues on with the original code.A quick test locally of calling
exit!
prevents the error in guard/spork and still leaves all the tests passing, im just not sure if this would have any implications on other gems so iv put it out there for some smarter minds to weigh in on..Gems
spork (1.0.0rc3)
guard-rspec (= 2.5.0)
guard-spork (= 1.5.0)
guard (2.2.3)
rspec (2.14.1)
The text was updated successfully, but these errors were encountered: