Test-infra: Prow postsubmit job does not have proper gubernator link

[krzyzacy]

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/test-infra/ci-test-infra-bazel/57131/

should be

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-test-infra-bazel/57131/

[fejta]

/area prow

What do you mean by "prow postsubmit job?" Where did you get the incorrect link?

[krzyzacy]

http://prow.k8s.io/?type=postsubmit, click on one of the job name.

/assign @spxtr

[spxtr]

I clicked on one and it took me here which was right...

[krzyzacy]

the test-infra one is not right :-)

[spxtr]

Feel free to submit a patch to fix this template :)

[krzyzacy]

ouch... I feel dizzy reading through the template... and presubmit/postsubmit works differently... ahhh :disappointed:

[fejta]

yeah that line in the config is intense

[spiffxp]

would the template be easier if there was a /logs equivalent of the /pr/org/repo/1234 mapping added to gubernator in https://github.com/kubernetes/test-infra/pull/3797 ?

[sebastienvas]

It does not seem to be a template issue. The url is not right when the job is pending not when the job is complete.

[sebastienvas]

Nevermind - does not seem to be the same issue.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[krzyzacy]

@BenTheElder does your bootstrap hack also helped this one?

[BenTheElder]

I think it may have, not sure.

On Fri, Feb 9, 2018 at 10:28 AM, Sen Lu [e-mail] wrote:

@BenTheElder https://github.com/bentheelder does your bootstrap hack
also helped this one?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/test-infra/issues/3798#issuecomment-364517408,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4Bq1RQrLTpaOgQmLfUTwD00aIWEjdpks5tTI5UgaJpZM4On597
.

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[spiffxp]

/reopen
/remove-lifecycle rotten
/help
this is still an issue and seems like it would be an easy fix for a new contributor

clicking through random jobs on http://prow.k8s.io/?type=postsubmit the problem doesn't happen for kubernetes/kubernetes nor kubeflow/*, but does happen for kuberentes/test-infra

[k8s-ci-robot]

@spiffxp: you can't re-open an issue/PR unless you authored it or you are assigned to it.

In response to this:

/reopen
/remove-lifecycle rotten
/help
this is still an issue and seems like it would be an easy fix for a new contributor

clicking through random jobs on http://prow.k8s.io/?type=postsubmit the problem doesn't happen for kubernetes/kubernetes nor kubeflow/*, but does happen for kuberentes/test-infra

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.

[k8s-ci-robot]

@spiffxp:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/reopen
/remove-lifecycle rotten
/help
this is still an issue and seems like it would be an easy fix for a new contributor

clicking through random jobs on http://prow.k8s.io/?type=postsubmit the problem doesn't happen for kubernetes/kubernetes nor kubeflow/*, but does happen for kuberentes/test-infra

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.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[nikhita]

/remove-lifecycle stale

[nikhita]

this is still an issue and seems like it would be an easy fix for a new contributor

can we call this good-first-issue? :)

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[BenTheElder]

the pod-utils should help with this, cc @stevekuznetsov

[stevekuznetsov]

Is this an issue with the report template that you guys have in your config?

[BenTheElder]

I think so, switching to decorating the upload location and then having a reporter component leverage that should fix this reliably instead of trying to keep "fixing" that horrible template.

[fejta]

Can we please simplify the path logic to be gs://prefix/ORG/REPO/suffix rather than a bunch of weirdness depending on whether the org is kubernetes?

There will still be weirdness around whether its a presubmit, but this will be better and simpler

[stevekuznetsov]

@fejta +10000 -- that intent is why I called that optional org/repo segment the "legacy" approach in the pod utilities, thinking we'd move to a more sane one in the future sometime...

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.