Merged
Conversation
The Docker test test_runIndexTask_andKillData has been quite flaky, often requiring multiple re-runs. So bump up the timeout to see if it helps.
Contributor
Author
|
With a 3 minute timeout, the Docker test has been successful for five consecutive runs |
kfaraz
approved these changes
Dec 17, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The
test_runIndexTask_andKillDataDocker test has been quite flaky due to timeouts, often requiring multiple re-runs.We’ll need to inspect the Docker logs to identify the source of timeout/flakiness, but the logs appear to be missing because they get cleaned up after the test completes? In the meantime, try increasing the timeout from 2 minutes to 3 minutes to see if it reduces or eliminates the flakiness.