tests: Use tk.MustHavePlan and tk.MustNotHavePlan instead of tk.HasPlan#46947
tests: Use tk.MustHavePlan and tk.MustNotHavePlan instead of tk.HasPlan#46947ti-chi-bot[bot] merged 26 commits intopingcap:masterfrom
tk.MustHavePlan and tk.MustNotHavePlan instead of tk.HasPlan#46947Conversation
|
Hi @Defined2014. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #46947 +/- ##
================================================
- Coverage 73.2424% 72.7016% -0.5408%
================================================
Files 1332 1356 +24
Lines 397659 404014 +6355
================================================
+ Hits 291255 293725 +2470
- Misses 87750 91644 +3894
+ Partials 18654 18645 -9
Flags with carried forward coverage won't be shown. Click here to find out more.
|
|
/test check-dev |
|
@Defined2014: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
tk.MustHasPlan and tk.MustNotHasPlan instead of tk.HasPlantk.MustHasPlan and tk.MustNotHasPlan instead of tk.HasPlan
mjonss
left a comment
There was a problem hiding this comment.
Suggestion to change the function name.
With 'Must' it changes the English grammar, so 'Must Have' is the correct form.
tk.MustHasPlan and tk.MustNotHasPlan instead of tk.HasPlantk.MustHavePlan and tk.MustNotHavePlan instead of tk.HasPlan
mjonss
left a comment
There was a problem hiding this comment.
LGTM with some suggestions and questions. Feel free to ignore them, since the PR is improving the situation anyway.
| { | ||
| // 3 table scans | ||
| "a < 2 or a < 10 or a > 11", []string{"1", "100"}, | ||
| }, | ||
| { | ||
| // 3 index scans | ||
| "c < 10 or c < 11 or c > 50", []string{"1", "10", "100"}, | ||
| }, |
There was a problem hiding this comment.
Should these return "TableFullScan" or something else? Maybe the cases struct could be extended with matching MustHavePlan/MustNotHavePlan?
There was a problem hiding this comment.
Yes, it's TableFullScan. Not sure it should be checked in this test or not.
|
/test unit-test |
|
@Defined2014: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bb7133, mjonss The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@Defined2014: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/test check-dev |
|
@Defined2014: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What problem does this PR solve?
Issue Number: close #46945
Problem Summary:
What is changed and how it works?
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.