-
Notifications
You must be signed in to change notification settings - Fork 239
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
fix: Remove wait after SQLInstance periodic test steps #3189
Merged
google-oss-prow
merged 1 commit into
GoogleCloudPlatform:master
from
jasonvigil:remove-sql-timeouts
Nov 27, 2024
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Is this a revert to a previous const var? I like that we make this a configurable field. It is more manageable and can help future resources which needs additional delays.
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.
There are no known circumstances where we need to add additional delays. Since there are no more uses, I think we should remove the configurability, because it is now dead code.
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.
"dead code should be cleaned up" --> Right, that makes the KCC code base much better.
I consider this not a dead code but a feature that has been approved working well. For dynamic test, we do not expect the contributors can be able to fix the source code when their resource need some special treatment, the only option for them is to explore the configurables in the resource-context file. Enriching the configurable pools is always appreciated, especially if the feature does not introduce performance regression to the current test. Therefore, can we keep it?
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.
Aside from this code no longer being used, I also feel like this code is not really a desirable feature. It allowed me to miss an actual bug, which was that my direct controller was not waiting correctly for delete LRO's to complete. From this one example of a previous use, this configuration seems like more like a "foot-gun", rather than a desirable feature. If any contributors hit issues in the future where they feel like something like this is actually necessary, I think not having this configuration available would cause us to examine the situation more closely, rather than allow a "quick workaround" of extending the wait time and potentially miss a similar bug.
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.
Ok. If it is not approved to be a desired feature, agree that we should drop it .