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
Changed glog V(1) and V(2) to V(0) #9332
Changed glog V(1) and V(2) to V(0) #9332
Conversation
Thanks @csrwng . Made the changes, squashed, and pushed again. |
lgtm |
Error pulling ruby builder in e2e (not sure if it's network flake):
[merge] |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/4928/) (Image: devenv-rhel7_4382) |
Seems like another network flake:
[merge] |
Evaluated for origin merge up to 5613fa6 |
Guys, this is way too much output that users don't need. We need to walk some of this back - end users don't (for instance) care about any of the following:
We only need 1 of "Downloading" or "Cloning", and the "pull" message is way too long. Please either revert or fix this so that normal users only get the absolute most critical information they need. |
fixes #9247
Changed glog V(1) and V(2) to log at V(0) to ensure necessary log output is captured by extended build tests.