-
Notifications
You must be signed in to change notification settings - Fork 28
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
Fix Quarkus-cli flacky test #321
Conversation
685cf0a
to
819de5e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sounds odd to me. The app.start()
should be consistent and if's flaky, it should be fixed internally.
What is happening here is that for some reason, it fails to start at first and then it retries several times until eventually it starts ok.
819de5e
to
d91f325
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This fix seems like a workaround for CLI but that now affects all the scenarios in the test framework with possible side effects.
We should investigate why this test starts behaving flacky to indeed solve the issue.
d91f325
to
7ab82f1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm ok with the changes, but add a comment with a link to the upstream issue / or pr to put some context around why this was necessary.
7ab82f1
to
f50b0ae
Compare
f50b0ae
to
135aa05
Compare
This issue could be related to commit: https://github.com/quarkusio/quarkus/pull/20998/files#diff-b4cbc080dba18bd5f82d2ece4ad078b684bfe808602e4a38e16d7de137d065dcR37