-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Consistently print errors to stderr and add newlines to cordon #68656
Consistently print errors to stderr and add newlines to cordon #68656
Conversation
smarterclayton
commented
Sep 14, 2018
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: smarterclayton The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@kubernetes/sig-cli-bugs |
Wow, the drain test cases are a bit of a horror show of internal types and using the wrong codecs. Going to have to fix that. |
6fedcaa
to
f816452
Compare
I unfortunately had to work around the scheme problem, it was more involved than I expected. @juanvallejo looks like the drain tests were broken when we switched to external types, but no one noticed because we never printed the error output. We need to fix drain to work with an external scheme that doesn't use legacy, but it's more involved. Can you make sure there is a sig-cli work item to cover this test? I can file an issue. |
/uncc |
f816452
to
c83327b
Compare
bazel i hate you |
LOL, this time it's not bazel's fault :) need to update drain_test.go i think |
c83327b
to
2e5fb54
Compare
It was Bazel's fault, the way we build inside bazel is slightly different than the way outside, which causes different error messages to show up |
aha! thanks @smarterclayton |
/retest |
2e5fb54
to
c291d3d
Compare
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
/retest |
/retest
…On Tue, Oct 16, 2018 at 2:03 PM k8s-ci-robot ***@***.***> wrote:
@smarterclayton <https://github.com/smarterclayton>: The following test
*failed*, say /retest to rerun them all:
Test name Commit Details Rerun command
pull-kubernetes-e2e-gce c291d3d
<c291d3d>
link
<https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/68656/pull-kubernetes-e2e-gce/56018/> /test
pull-kubernetes-e2e-gce
Full PR test history <https://k8s-gubernator.appspot.com/pr/68656>. Your
PR dashboard <https://k8s-gubernator.appspot.com/pr/smarterclayton>.
Please help us cut down on flakes by linking to
<https://git.k8s.io/community/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests>
an open issue
<https://github.com/kubernetes/kubernetes/issues?q=is:issue+is:open> when
you hit one in your PR.
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository. I understand the commands that are listed here
<https://go.k8s.io/bot-commands>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#68656 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABG_p2jVPLiK5jLQC5eLvcLeHr41-0foks5ulh9WgaJpZM4Woljg>
.
|
/retest Review the full test history for this PR. Silence the bot with an |