-
Notifications
You must be signed in to change notification settings - Fork 89
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
E2E tests fail because of too many requests trying to get workflow status #324
Comments
|
I think we're going to have delete the namespace seems like there are too many workflows and the APIServer is unresponsive even to deleting individual workflows or by label. |
See: #53 (comment) |
Delete the namespace
|
Follow the instructions to create the secret.
The namespace is back up |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in one week if no further activity occurs. Thank you for your contributions. |
This issue has been closed due to inactivity. |
kubeflow/kubeflow#2557
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/kubeflow_kubeflow/2557/kubeflow-presubmit/6084/
Test is reported as success but its still a failure.
Pod probably exited with non-zero exit code
Here are the pod logs
Could this because we have too many workflows in the api server?
The text was updated successfully, but these errors were encountered: