-
Notifications
You must be signed in to change notification settings - Fork 592
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
CI Failure (assert offset == o
) in TimeQueryTest.test_timequery
#17201
Comments
Note to developer: please provide a message with the assertion when addressing this issue |
TimeQueryTest.test_timequery
assert offset == o
) in TimeQueryTest.test_timequery
1 similar comment
Without going into the details of the CI failure itself, whats interesting about this is that it has only been triggered in CDT over the last few months, and every report of it failing also has a number of other failed ducktapes with it- usually node operation or partition moving tests. Most specifically, this seems to fail quite often with So, that leads me to ask the question, is ducktape parallelization and the interaction of these tests responsible for the failures seen in the Timequeries seem very stable on their own. |
Closing older-bot-filed CI issues as we transition to a more reliable system. |
https://buildkite.com/redpanda/vtools/builds/12363
JIRA Link: CORE-1895
The text was updated successfully, but these errors were encountered: