-
Notifications
You must be signed in to change notification settings - Fork 859
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
Add e2e for remedy #5007
Add e2e for remedy #5007
Conversation
Signed-off-by: changzhen <changzhen5@huawei.com>
Signed-off-by: changzhen <changzhen5@huawei.com>
Hi @Vacant2333, can you help take a look? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #5007 +/- ##
=======================================
Coverage 53.30% 53.30%
=======================================
Files 253 253
Lines 20560 20560
=======================================
Hits 10960 10960
Misses 8875 8875
Partials 725 725
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
/assign |
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.
hi
/lgtm
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: RainbowMango, Vacant2333 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 cleanup
What this PR does / why we need it:
Add e2e for the remedy feature.
Which issue(s) this PR fixes:
Part of #4658
Special notes for your reviewer:
Does this PR introduce a user-facing change?: