Closed nojnhuh closed 7 months ago
/sig contribex
@nojnhuh: The label(s) sig/contribex
cannot be applied, because the repository doesn't have them.
/sig testing
21 July 2023
this is a long time, @BenTheElder @ameukam rings a bell?
21 July 2023
this is a long time, @BenTheElder @ameukam rings a bell?
Looks ghproxy is done in the cluster involved. I'll take a look next week is no one beats me to it.
@ameukam Have you had a chance to take a look at this?
@nojnhuh https://github.com/kubernetes/k8s.io/pull/6296 should hopefully fix this. Thank you for reporting this.
I see a number of green runs in a row now. Thanks!
/close
@nojnhuh: Closing this issue.
What happened:
Most of the triage-robot's jobs have been failing consistently for at least the last few weeks. I think failures go back to around 21 July 2023 based on searching all of GitHub for stale issue comments: https://github.com/issues?q=commenter%3Ak8s-triage-robot+%22After+30d+of+inactivity+since%22+
Every failure looks more or less like:
What you expected to happen:
The jobs pass.
How to reproduce it (as minimally and precisely as possible):
Please provide links to example occurrences, if any:
https://testgrid.k8s.io/sig-contribex-k8s-triage-robot
e.g. https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-k8s-triage-robot-stale-issues/1745931646969843712
Anything else we need to know?: