-
Notifications
You must be signed in to change notification settings - Fork 71
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
tests,backup: fix flakiness by using current timestamps #982
tests,backup: fix flakiness by using current timestamps #982
Conversation
70484ef
to
09a4d06
Compare
09a4d06
to
bfc96a2
Compare
Using some (old) fixed timestamps when producing messages was causing the messages to be automatically deleted because past message retention. I think most of the time the test was managing to complete successfully before the retention kicked in, making it fail only sometimes.
bfc96a2
to
cfc4e1a
Compare
Nice finding, I guess alternative fix could be to disable retention? (Asking because we most likely have the exact same issue in an internal project) |
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, great finding. How did you realized it?
@aiven-anton Ah yes I guess that would work too, did no think about that |
@eliax1996 The beginning offset of the topic was mysteriously changing from 0 to the 2 (end offset) after a few seconds. |
Using some (old) fixed timestamps when producing messages was causing the
messages to be automatically deleted because past message retention.
I think most of the time the test was managing to complete successfully
before the retention kicked in, making it fail only sometimes.