Fix shouldUpdateTopicInKafkaWhen* test flakiness #10921
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fvaleri
force-pushed
the
to-flaky-its
branch
6 times, most recently
from
aa6135f to
9d68abc
Compare
Signed-off-by: Federico Valeri <[email protected]>
|
@see-quick I ran the CI for 10 times without issues. Can you also check and confirm? Thanks. |
I will take a look at this tomorrow. Thanks |
|
/azp run build |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Federico Valeri <[email protected]>
|
/azp run build |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run build |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run build |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run build |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run build |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run build |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
This is unrelated to previous test failures and new: 2024-12-12T15:18:58.6368702Z [ERROR] io.strimzi.operator.topic.KafkaHandlerIT.shouldDescribeTopics -- Time elapsed: 9.002 s <<< ERROR!
2024-12-12T15:18:58.6369340Z java.util.NoSuchElementException: No value present
2024-12-12T15:18:58.6369827Z at java.base/java.util.Optional.get(Optional.java:143)
2024-12-12T15:18:58.6370319Z at io.strimzi.operator.topic.KafkaHandlerIT.shouldDescribeTopics(KafkaHandlerIT.java:246)Here we fixed an ordering issue, and that's fine. But I don't understand why I think we need to enable trace level and maybe add some more logging. I also wonder if |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change
Description
Attempt to fix shouldUpdateTopicInKafkaWhen* test flakiness.
We cannot reproduce locally, so I would need to use some CI time to verify.
Checklist