Bump timeout in minikube clickhouse deployment test #5966
Conversation
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
We've seen this flake in ci multiple times due to a timeout while the image pull was being retried, so let's give it longer
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.
We've seen this flake in ci multiple times due to a timeout while the image pull was being retried, so let's give it longer
Note
Low Risk
Low risk CI-only change that just extends a
kubectl waittimeout to reduce flaky minikube deployments; no production code or runtime behavior is affected.Overview
In the
minikubeGitHub Actions workflow, increases thekubectl waittimeout for the ClickHouse operator deployment to become available (120s → 300s) to reduce CI flakes during image pulls.Written by Cursor Bugbot for commit 2325107. This will update automatically on new commits. Configure here.