-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Bump GRPC to v1.27.0 #4191
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
Bump GRPC to v1.27.0 #4191
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4191 +/- ##
=======================================
Coverage 40.91% 40.91%
=======================================
Files 111 111
Lines 9614 9614
=======================================
Hits 3934 3934
Misses 5301 5301
Partials 379 379 |
|
/retest |
2 similar comments
|
/retest |
|
/retest |
|
LGTM |
|
/retest |
1 similar comment
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mrunalp, saschagrunert 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 |
|
@fidencio Can you check that this keeps kata happy? |
|
Sure, gimme an hour or two and I'll get to this. |
|
I've just tested this and it doesn't break anything on kata. Based on this ... |
|
Thank you @fidencio ❤️ |
|
/retest |
1 similar comment
|
/retest |
|
Rebase needed for test fixes |
This fixes the build of the release-note tool, which previously failed with: ``` vendor/google.golang.org/api/internal/conn_pool.go:29:2: undefined: grpc.ClientConnInterface ``` Signed-off-by: Sascha Grunert <[email protected]>
|
Rebased on top of the latest master branch. |
|
/lgtm |
|
/retest |
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
This fixes the build of the release-note tool, which previously failed
with:
Which issue(s) this PR fixes:
Refers to 15aa81b
Forward-port of #4190
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?