We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
TestWatchDelayForManualProgressNotification
I did not see any obvious error message in the test case TestWatchDelayForManualProgressNotification, but the workflow somehow failed.
Please refer to https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/post-etcd-e2e-amd64/1891157026864631808
It might related to the discussion in https://kubernetes.slack.com/archives/C3HD8ARJ5/p1739737947112529
cc @fuweid @ivanvc @jmhbnz @serathius
.
No response
The text was updated successfully, but these errors were encountered:
Came to see if I can pick this up :) But following up on the thread linked, looks like the timeout of 30m coming from here as @ivanvc pointed it out.
And also there is existing issue to reduce e2e test time
may be we can close this issue @ahrtr ?
Sorry, something went wrong.
Yes, this should have been resolved in kubernetes/test-infra#34355.
Let's watch the workflow failures. thx
No branches or pull requests
Which Github Action / Prow Jobs are flaking?
I did not see any obvious error message in the test case
TestWatchDelayForManualProgressNotification
, but the workflow somehow failed.Please refer to https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/post-etcd-e2e-amd64/1891157026864631808
It might related to the discussion in https://kubernetes.slack.com/archives/C3HD8ARJ5/p1739737947112529
cc @fuweid @ivanvc @jmhbnz @serathius
Which tests are flaking?
.
Github Action / Prow Job link
No response
Reason for failure (if possible)
No response
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: