We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
QuarkusMainLauncher
Since Quarkus 3.13.0, QuarkusMainLauncher always returns exit code 0 for integration tests and not the actual exit code.
0
No response
Looks like this change via #41726 made QuarkusMainLauncher always return exit code 0, because of this check in StartupActionImpl.runMainClassBlocking()
StartupActionImpl.runMainClassBlocking()
/cc @gsmet
uname -a
ver
java -version
3.13.0
mvnw --version
gradlew --version
The text was updated successfully, but these errors were encountered:
gsmet
Successfully merging a pull request may close this issue.
Describe the bug
Since Quarkus 3.13.0,
QuarkusMainLauncher
always returns exit code0
for integration tests and not the actual exit code.Expected behavior
No response
Actual behavior
Looks like this change via #41726 made
QuarkusMainLauncher
always return exit code 0, because of this check inStartupActionImpl.runMainClassBlocking()
/cc @gsmet
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
3.13.0
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: