-
Notifications
You must be signed in to change notification settings - Fork 1k
flaky test: application failover with purgeMode gracefully when the GracePeriodSeconds is reach out #6917
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
Conversation
Summary of ChangesHello @zhzhuang-zju, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request aims to resolve a flakiness issue in an end-to-end test for application failover. The changes improve the test's stability by introducing an explicit wait mechanism to ensure that deployments are fully provisioned and ready on the designated target clusters before the test proceeds, thereby mitigating potential race conditions that could lead to intermittent failures. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
This pull request addresses a flaky test by introducing a wait condition to ensure the deployment is fully ready before proceeding with the test logic. The refactoring to use a targetClusters variable also improves code readability. The approach is sound and effectively enhances test stability. I've added one suggestion to further improve the robustness of the deployment readiness check by using a more comprehensive helper function that is already available in the test framework.
0e044ff to
6693fda
Compare
|
Thanks~ |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #6917 +/- ##
=======================================
Coverage 46.38% 46.38%
=======================================
Files 697 697
Lines 47751 47751
=======================================
+ Hits 22149 22150 +1
+ Misses 23933 23932 -1
Partials 1669 1669
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…racePeriodSeconds is reach out Signed-off-by: zhzhuang-zju <[email protected]>
6693fda to
77239f2
Compare
XiShanYongYe-Chang
left a comment
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.
Thanks
/lgtm
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: XiShanYongYe-Chang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind flake
What this PR does / why we need it:
ref to #6868 (comment)
Which issue(s) this PR fixes:
Parts of #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: