-
Notifications
You must be signed in to change notification settings - Fork 15
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
[FEAT] System exit #122
[FEAT] System exit #122
Conversation
Merging and releasing. |
Thanks a lot @danglotb ! |
Hum, I have issue releasing, since the release goal of maven launches an inside maven command, without the option for testing and avoiding the I'll investigate to find a solution but might have revert this commit |
ok! |
You can use https://github.com/stefanbirkner/system-rules. We use it in Flacoco: |
In the meantime, you can try on the SNAPSHOT, which is deployed on Nexus Repository. |
great, thanks, I will try 3.1.1-SNAPSHOT. |
@andre15silva Awesome! Thank you very much for the resources. I'll fix the test and release, thank you! 😄 |
test-runner-3.1.1 is out 🎊 |
Thanks @danglotb ! I'll merge ASSERT-KTH/flacoco#117 once it is green @martinezmatias |
I confirm |
Great job @danglotb @andre15silva !! I confirm that the issue is solved on the CI for Math-5, Math-8 and Math-28!! see here. |
nice!
|
We call now a
System.exit()
at the end of the main methods of the runner classes. I recall that these classes should never be used directly, but only called by theEntryPoint
, which will use a newjava
command line to run the main of the runner classes.@martinezmatias @andre15silva
This should solve the issue on Math2, since the process was not ending properly. I guess that the
System.exit()
is a bit rough but IMO, it is a valid workaround.The tests is executing directly the main methods of the runner classes, this is why we must now use a special flag when running the test:
mvn clean test -DnoExitForTesting=true
.