CI not responding to test retry commands

[wlynch]

Expected Behavior

Using the /test command CI suggests should rerun the tests.

Actual Behavior

CI doesn't recognize the command it suggests, saying The specified target(s) for /test were not found.

Examples of this happening:

• Bump github.com/golangci/golangci-lint from 1.53.2 to 1.53.3 in /tools pipeline#6833 (comment)
• Bump k8s.io/client-go from 0.25.4 to 0.27.2 in /tekton/ci/custom-tasks/pr-status-updater #1437 (comment)

[afrittoli]

The message comes from Prow and it's a spurious one. The CI check in question is managed by Tekton so Prow does not know about it, and we haven't found an easy way to prevent Prow from commenting like that.
The only easy solution would be to use a different command e.g. /tekton for Tekton based CI jobs, but that would push the problem to users as they'd need to know which job is managed by Prow and which by Tekton

[wlynch]

A /tekton command or similar would be great!
The larger problem is these tests are failing fairly regularly and there's no easy way to retry them. 🥲

[afrittoli]

There is a way to retry them, which is the usual /test command. Using that for Tekton jobs does work, only prow complains with a spurious error message because he does not know about those jobs.

But yeah, the problem of the frequent failure should be solved. The job themselves actual do not fail, what fails is the notification back to GitHub, which leaves the job in pending state

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
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 with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.