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 missing probe severity to info #11968
update missing probe severity to info #11968
Conversation
9cdb35a
to
3b232f2
Compare
[test] |
I would use "Info:" for the header not "Infos:" you wouldn't say On Fri, Nov 18, 2016 at 12:42 PM, Juan Vallejo notifications@github.com
|
3b232f2
to
6378793
Compare
Done! Do you think |
Hmm that would probably be OK too, I don't have a strong opinion either way. On Fri, Nov 18, 2016 at 1:05 PM, Juan Vallejo notifications@github.com
|
@@ -304,6 +304,10 @@ func (d *ProjectStatusDescriber) Describe(namespace, name string) (string, error | |||
warningMarkers := allMarkers.BySeverity(osgraph.WarningSeverity) | |||
if len(warningMarkers) > 0 { | |||
if d.Suggest { | |||
// add linebreak between Errors list and Warnings list | |||
if len(errorMarkers) > 0 { | |||
fmt.Fprintln(out, "") |
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.
nit, fmt.Fprintln(out)
if d.Suggest { | ||
// add linebreak between Warnings list and Info List | ||
if len(warningMarkers) > 0 || len(warningMarkers) > 0 { | ||
fmt.Fprintln(out, "") |
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.
Same here.
LGTM, no strong opinion about the wording. Let me know when this is good to go. |
6378793
to
55bae56
Compare
@fabianofranz thanks for the review, almost good to go, added a |
0592719
to
106c43d
Compare
integration check flaked on #9203 re[test] |
if len(infoMarkers) > 0 { | ||
if d.Suggest { | ||
// add linebreak between Warnings list and Info List | ||
if len(warningMarkers) > 0 || len(warningMarkers) > 0 { |
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.
Double-check just in case. :)
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.
:) Thanks for catching that
106c43d
to
2ce9162
Compare
LGTM [merge] |
Evaluated for origin merge up to 2ce9162 |
Evaluated for origin test up to 2ce9162 |
continuous-integration/openshift-jenkins/test Running (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/11572/) (Base Commit: f056a5b) |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/11573/) (Base Commit: 271fff8) (Image: devenv-rhel7_5387) |
continuous-integration/openshift-jenkins/test SUCCESS |
Fixes #10294
This patch changes the marker severity of missing probes (liveness and readiness) from
osgraph.WarningSeverity
toosgraph.InfoSeverity
. It also adds a linebreak betweenErrors
,Warnings
, andInfos
.Example
cc @jwforres @deads2k @fabianofranz