You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not able to reproduce this locally in my computer after 40 tries.
I don't think there is a race condition, before every test we wait that the KafkaConsumer has the partitions assigned. This is done in the @beforeeach after the comment 'Wait till consumers are ready'. Only after that, we produce new events, so consumers should be ready to consume them.
It could be a bug, but I should be able to reproduce it after so many tries.
Other possibility:
In the attached file of Daniel we can see that there are many events after the line '==========> test error()' related to the test someEventsNoAckWithOnePartition().
That is because in the test someEventsNoAckWithOnePartition() some events are not committed, so every new test execution after that is reading that events again and again, overloading a bit.
Correct me if I'm wrong but this tool we have for building is twice slow than the previous one we had. Maybe it is because of that.
For the time being I will decrease the number of events in the test so we can verify if this theory is correct or not.
Branch
master
KafkaCdiExtensionTest
fails on line 468 with timeout - as the timeout is configured to 30 seconds, this is most likely a race condition or a bug.See https://builds.helidon.io/51A9EA2726241E0093DFA5D5139F3E6B/logs/14
The text was updated successfully, but these errors were encountered: