-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Avoid adding test flags when using the null logger #82
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
Avoid adding test flags when using the null logger #82
Conversation
LGTM |
d5c3ebb
to
455d0ad
Compare
This should fix the lint issues. I always forget to run gometalinter, since it's not written anywhere (that I've seen). Maybe we should add it to CONTRIBUTING.md or have a makefile target for it, or something? |
Yeah, we can add a section in Linter is still complaining. |
whoops, typo. Yeah, I found test.sh (it does run all the tests though, and sometimes you just want to run the linter). |
I'll push a PR later today around that. |
The null logger from logr is in the same package as the testing logger, which means it accidentally adds testing flags to all binaries that import it. Copy the null logger into the pkg/runtime/log package to avoid this.
455d0ad
to
434aee9
Compare
there, that should fix it. actually remembered to run the right linter command this time ;-) |
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
…lly-testing Avoid adding test flags when using the null logger
fixed build artifact path for gsutil copy command
The null logger from logr is in the same package as the testing logger,
which means it accidentally adds testing flags to all binaries that
import it. Copy the null logger into the pkg/runtime/log package
to avoid this.