-
Notifications
You must be signed in to change notification settings - Fork 431
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
Update Go, CAPI, controller-runtime, k8s, controller-tools and go-logr/logr #1951
Update Go, CAPI, controller-runtime, k8s, controller-tools and go-logr/logr #1951
Conversation
@CecileRobertMichon: The label(s) In 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. |
9d986df
to
42717a2
Compare
Needs kubernetes/test-infra#24815 to merge to be able to run tests |
/retest jobs updated |
42717a2
to
1aceeaf
Compare
4ac03b4
to
bdb30dd
Compare
/retest |
92e0672
to
44700e8
Compare
@devigned I'm still working through the upgrade e2e tests that were deprecated in CAPI 1.1 but I would appreciate your early review on c2f66d5 I'm especially unsure of the WithCallDepth function c2f66d5#diff-62963db075cb6f1b2e13f658ea3d053f83cc5623ab160ee2fbbc1b1378970057R48 and whether we should be using the |
/test ls |
@CecileRobertMichon: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
In 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. |
/retest |
/test pull-cluster-api-provider-azure-e2e-workload-upgrade-1-21-1-22 |
8a4c7c9
to
bbe1929
Compare
4dfd3d3
to
cbad552
Compare
/test pull-cluster-api-provider-azure-e2e-workload-upgrade-1-21-1-22 |
logs are looking good now
|
/retest exp test flake |
/retest |
func (c *compositeLogger) Info(msg string, keysAndValues ...interface{}) { | ||
c.iter(func(l logr.Logger) { | ||
l.Info(msg, keysAndValues...) | ||
func (c *compositeLogSink) Info(level int, msg string, keysAndValues ...interface{}) { |
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.
is this meant to replace log.V(n).Info(msg) with log.Info(n,msg)
? Should we do a followup for such replacements?
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.
No. The Logger struct still has a V(n)
function. It's only the LogSink interface that has Info(n, msg).
For an example of how this works, this the example logger implementation here and example usage here and here.
6a256c3
to
fc4d152
Compare
/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.
Just a couple questions and bit of feedback on the logger correlation func. Nice work!
fc4d152
to
3b48466
Compare
@devigned I've addressed your comments, PTAL |
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
/approve
Awesome work, @CecileRobertMichon!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: devigned 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 |
/retest |
/retest different flake, web-elb not reachable timeout |
:( :( running into all the possible flakes here.... /retest |
@CecileRobertMichon: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
What type of PR is this?
/kind other
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
TODOs:
Release note: