Removing go get golint since the test image now has golint #187
Conversation
|
Lets see if the test passes :) |
|
/test pull-kubernetes-multicluster-ingress-test |
|
Cant get details again. Its failing with cc @BenTheElder @krzyzacy Any ideas why? |
|
you should check prow.k8s.io, logs won't upload if your job can't execute or something along those l ines /retest |
|
/lgtm |
|
golint failed- couldn't find golint. |
|
/retest |
|
?! no pod logs? |
|
@nikhiljindal: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
whoops |
|
sen: this isn't going to work. discussed a better route offline
with @nikhiljindal
…On Fri, Apr 6, 2018 at 5:20 PM k8s-ci-robot ***@***.***> wrote:
@nikhiljindal <https://github.com/nikhiljindal>: The following test
*failed*, say /retest to rerun them all:
Test name Commit Details Rerun command
pull-kubernetes-multicluster-ingress-test bc54927
<bc54927>
link
<https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/GoogleCloudPlatform_k8s-multicluster-ingress/187/pull-kubernetes-multicluster-ingress-test/235/> /test
pull-kubernetes-multicluster-ingress-test
Full PR test history
<https://k8s-gubernator.appspot.com/pr/GoogleCloudPlatform_k8s-multicluster-ingress/187>.
Your PR dashboard <https://k8s-gubernator.appspot.com/pr/nikhiljindal>.
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/GoogleCloudPlatform/k8s-multicluster-ingress/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/devel/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
<#187 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA4BqyADeU6iPAf27letFGtX8yuERPF5ks5tmAZJgaJpZM4TKzbc>
.
|
|
#189 is the better route. |
Ref kubernetes/test-infra#7604
cc @G-Harmon