-
Notifications
You must be signed in to change notification settings - Fork 51
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
Logging Cleanup - Part 3 #414
Conversation
Not sure why make presubmit keeps failing here when it passes locally. Am I missing a step?
|
Pull Request Test Coverage Report for Build 6330198666
💛 - Coveralls |
if ret != "" { | ||
return errors.New(ret) |
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.
do you mind to cleanup this error handling too?
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.
I gave this a try, but after a couple of hours of dealing with e2e test failures, reverted it for the sake of timeboxing. It seems as though we have some reliance on this error handling logic, which I'd like to keep outside the scope of the logging changes
@@ -1,64 +0,0 @@ | |||
package main |
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.
Could you add these more gomock_reflect_
in the gitignore in passing?
aws-application-networking-k8s/.gitignore
Line 18 in 3f89fd8
pkg/aws/services/gomock_reflect_* |
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.
This shouldn't exist at all, it was an artifact from a previous build issue that accidentally got checked in
What type of PR is this?
cleanup
Which issue does this PR fix:
#126 partially
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs from aws-gateway-controller showing the issue:
Testing done on this change:
Automation added to e2e:
Will this PR introduce any new dependencies?:
No
Will this break upgrades or downgrades. Has updating a running cluster been tested?:
No
Does this PR introduce any user-facing change?:
Only logging changes
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.