-
Notifications
You must be signed in to change notification settings - Fork 935
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
Forked tests and System.exit #565
Comments
Thank you! |
I have an issue where SBT hangs while executing tests in forked mode if an exception is thrown during construction of the test class (using ScalaTest). Is it expected that this fix would solve that? |
Yes, this change fixes the hang. Still it doesn't address the issue that the failure to construct one test framework should not influence running tests from the others. What exception do you get? |
The stacktrace follows: |
Added a follow-up to the gist. |
In order to make sbt's behavior consistent with regards to calling System.exit after executing tests, it would be useful if we could configure to call System.exit for the child process when executing tests in forked mode.
This mailing list thread provides some extra background:
https://groups.google.com/forum/?fromgroups=#!topic/simple-build-tool/z282ZDoMq14
The text was updated successfully, but these errors were encountered: