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.

Sign up for GitHub

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

Jump to bottom

Workaround the condition that makes DefaultReadinessProcedureHealthTest fail on Oracle JDKs #325

Closed
fabiobrz opened this issue Jan 28, 2025 · 0 comments · Fixed by #326
Closed

Workaround the condition that makes DefaultReadinessProcedureHealthTest fail on Oracle JDKs #325

fabiobrz opened this issue Jan 28, 2025 · 0 comments · Fixed by #326
Assignees
@fabiobrz

Comments

@fabiobrz
Copy link
Member

We noticed that DefaultReadinessProcedureHealthTest always fails on Oracle JDKs.

This is because the maven-surefire-plugin execution order seems to be deterministically not alphabetical there, causing MultiDeploymentHealthTest being executed right before DefaultReadinessProcedureHealthTest.
This condition is the root cause for the failure, and specifically because of https://issues.redhat.com/browse/WFLY-20325, which the MultiDeploymentHealthTest creates the condition for.

A workaround, i.e. set the runOrder property of the maven-surefire-plugin to alphabetical, is needed to make the failure disappear, until https://issues.redhat.com/browse/WFLY-20325 is solved.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fabiobrz fabiobrz

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Set surefire runOrder to alphabetical for microprofile-health fabiobrz/eap-microprofile-test-suite
1 participant
@fabiobrz