-
Notifications
You must be signed in to change notification settings - Fork 261
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
Skip non modified event first while waiting for ready #1390
Skip non modified event first while waiting for ready #1390
Conversation
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.
@cardil: 0 warnings.
In response to this:
Description
Allow using wait for ready with dynamic kube client, as before this change, an error was received on Added event with unstructured object, which by default doesn't have
.status
field.Changes
- 🐛 Bug fix of WaitForReady should check for event type before trying to read generation number #1389 - Skipping on non-modified event while waiting for ready
Reference
Fixes #1389
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.
Codecov Report
@@ Coverage Diff @@
## main #1390 +/- ##
==========================================
+ Coverage 76.51% 78.20% +1.68%
==========================================
Files 160 160
Lines 8234 8234
==========================================
+ Hits 6300 6439 +139
+ Misses 1229 1104 -125
+ Partials 705 691 -14
Continue to review full report at Codecov.
|
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-to-test
lgtm, but to pass the code cov test, the lines that were changed need to have more than 76.51 % coverage. |
@cardil can you please take a look at the coverage? We've discussed on WG call that if it's too cumbersome to reach some of the statements it can be even merged without reaching the required number, just let us know please. :) |
func peUnstructured(tb testing.TB) func(name string) ([]watch.Event, int) { | ||
return func(name string) ([]watch.Event, int) { |
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.
Neat! :)
The following is the coverage report on the affected files.
|
@itsmurugappan @dsimansk I did raise the coverage on reported method, although it's a synthetic example that shouldn't occur with duck elements, which always should have generation and observed generation. Now, this PR passes all the gates. |
/cc @itsmurugappan |
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.
/lgtm
cool, coverage also jumping by 1.68% 👍 |
/lgtm |
Since it's addressing all the review comments, imo it's good to go. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cardil, dsimansk, itsmurugappan 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 |
* Fixing the addressable resolver * Properly working address resolver * Working fake & it tests (apart those affected by knative/client#1389) * Upgrade to latest knative * Use interim fork until merge of knative/client#1390 * Allow addressable URI to be empty, and by default * Remove interim personal fork
Description
Allow using wait for ready with dynamic kube client, as before this change, an error was received on Added event with unstructured object, which by default doesn't have
.status
field.Changes
Reference
Fixes #1389