Skip to content
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 glogging to always set level, and to respect glog.level #8924

Merged
merged 1 commit into from
May 26, 2016

Conversation

smarterclayton
Copy link
Contributor

Fixes #8903 partially

@smarterclayton
Copy link
Contributor Author

smarterclayton commented May 18, 2016

[testonlyextended][extended:core(should allow to change build log level)]

@smarterclayton
Copy link
Contributor Author

[test]

@smarterclayton
Copy link
Contributor Author

@bparees @gabemontero fixes the failing extended test

@gabemontero
Copy link
Contributor

@smarterclayton @bparees I'll check the origin_extended_build_test job once this merges

@smarterclayton
Copy link
Contributor Author

Need a sign off

}
glog.Infof("Pushing %s image ...", pushTag)
glog.V(0).Infof("Pushing %s image ...", pushTag)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

V(1) ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Printed at 0 because it's the slowest part of the operation, so always shown.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't 1 already always shown? I was under the impression we were using 0 for warning/erring, and 1 for basic info (still always shown by default).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@@ -116,11 +116,11 @@ func (d *DockerBuilder) Build() error {
if authPresent {
glog.V(4).Infof("Authenticating Docker push with user %q", pushAuthConfig.Username)
}
glog.Infof("Pushing image %s ...", pushTag)
glog.V(1).Infof("Pushing image %s ...", pushTag)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

well you've got this push as a v(1) and the other push as a v(0)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok

@smarterclayton
Copy link
Contributor Author

[test]

On Mon, May 23, 2016 at 12:00 PM, OpenShift Bot notifications@github.com
wrote:

continuous-integration/openshift-jenkins/test FAILURE (
https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/3970/)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#8924 (comment)

@openshift-bot
Copy link
Contributor

Evaluated for origin testonlyextended up to 1b10493

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/testonlyextended SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin_extended/189/) (Extended Tests: core(should allow to change build log level))

@smarterclayton
Copy link
Contributor Author

Wtf is this:


service "database" created
You have exposed your service on an external port on all nodes in your
cluster.  If you want to expose this service to the external internet, you may
need to set up firewall rules for the service port(s) (tcp:31000) to
serve traffic.

See http://releases.k8s.io/HEAD/docs/user-guide/services-firewalls.md
for more details.
service "database-external" created

On Mon, May 23, 2016 at 3:19 PM, OpenShift Bot notifications@github.com
wrote:

continuous-integration/openshift-jenkins/test FAILURE (
https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/3984/)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#8924 (comment)

@smarterclayton
Copy link
Contributor Author

@Kargakis this does not belong here.

@smarterclayton
Copy link
Contributor Author

I'd like this patched out.

@smarterclayton
Copy link
Contributor Author

[test]

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to 1b10493

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/3993/)

@0xmichalis
Copy link
Contributor

I'd like this patched out.

I think we can have it in the factory so we won't need to carry a patch.

@smarterclayton
Copy link
Contributor Author

@Kargakis thanks.

@bparees anything else on this?

@bparees
Copy link
Contributor

bparees commented May 24, 2016

nope, lgtm.

@smarterclayton
Copy link
Contributor Author

[merge]

@openshift-bot
Copy link
Contributor

openshift-bot commented May 26, 2016

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/4099/) (Image: devenv-rhel7_4280)

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to 1b10493

@openshift-bot openshift-bot merged commit f80dcf3 into openshift:master May 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants