-
Notifications
You must be signed in to change notification settings - Fork 2.7k
ci-test-infra-triage perma failing #34863
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
Comments
We seem to be stuck on data from the 26th now |
This was passing reliably until recently: first failure:
green before that:
We don't have a diff link, but it was during 2025-04-25 that it started failing |
So maybe something that changed around ~2025-05-16, possibly more data in the CI results or some regression to the tool |
#34879 (comment) A few hours later we are currently running at https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-test-infra-triage/1928154351960854528 |
@BenTheElder i was watching the previous run, and my change did not solve the issue. i've filed another one #34882 after looking through the logs, let's try that one next. If i don't make progress, will file reverts for both. |
@dims your changes sound reasonable to keep IMHO, though I haven't had a chance to read in detail. Something recent caused this to grow pretty steadily, seems like pathological data. Haven't been able to confirm and I'm out tomorrow (back monday) |
back on its feet for now: https://prow.k8s.io/?job=ci-test-infra-triage ![]() based on temporary bump(s) for timeout: |
https://prow.k8s.io/?job=ci-test-infra-triage
cc @dims @aojea
/sig testing
timing out at 3h.
The text was updated successfully, but these errors were encountered: