Skip to content
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

Closed
pk11 opened this issue Oct 9, 2012 · 5 comments
Closed

Forked tests and System.exit #565

pk11 opened this issue Oct 9, 2012 · 5 comments
Labels
Milestone

Comments

@pk11
Copy link

pk11 commented Oct 9, 2012

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

@pk11
Copy link
Author

pk11 commented Oct 20, 2012

Thank you!

@ijuma
Copy link
Contributor

ijuma commented Oct 29, 2012

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?

@vigdorchik
Copy link
Contributor

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?

@ijuma
Copy link
Contributor

ijuma commented Oct 29, 2012

The stacktrace follows:

https://gist.github.com/3972753

@ijuma
Copy link
Contributor

ijuma commented Oct 29, 2012

Added a follow-up to the gist.

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

No branches or pull requests

4 participants