-
Notifications
You must be signed in to change notification settings - Fork 572
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
[DROOLS-6874] investigating flaky HACEP test #2735
Conversation
thanks @tkobayas for looking at these flaky tests |
Retry is effective:
|
kafkaServerTest.startServer(); | ||
KafkaServer server = kafkaServerTest.startServer(); | ||
for (int i = 0; i < MAX_RETRY; i++) { | ||
if (server.kafkaController().kafkaScheduler().isStarted()) { |
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.
Even if kafkaServerTest.startServer()
returns, kafkaController's initialization is running in a different thread so it may finish slightly later that leads to the issue in a slow Jenkins. kafkaScheduler().isStarted()
seems to be a suitable flag to check.
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@mareknovotny Please review and merge, thanks! |
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.
lgtm
please back port this to 7.67.x too |
JIRA:
https://issues.redhat.com/browse/DROOLS-6874
How to replicate CI configuration locally?
Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.
How to retest this PR or trigger a specific build:
a pull request please add comment: Jenkins retest this
a full downstream build please add comment: Jenkins run fdb
a compile downstream build please add comment: Jenkins run cdb
a full production downstream build please add comment: Jenkins execute product fdb
an upstream build please add comment: Jenkins run upstream