-
Notifications
You must be signed in to change notification settings - Fork 215
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
distributed-on-master failing #274
Comments
I have a fix for that in PR #253 I know, should have been a separate PR, but I was expecting that one to merge a bit sooner. |
@pohly Thanks for the speedy fix! It looks like there was one more test failure in the most recent run. |
That looks like a timing flake. Let's keep this issue open and monitor that a bit longer. /reopen |
@pohly: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hmm, occurred twice already. I'll check... |
Let's investigate as part of this issue. |
The reason for that failure was identified as problem in external-provisioner and fixed in kubernetes-csi/external-provisioner#612. We can fix the job by updating to the latest external-provisioner. |
After merging PR #280, the job started to pass: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-csi-distributed-on-kubernetes-master/1389537313842794496 |
The distributed-on-master test has been failing since April 7th.
Taking a sample error, it looks like the root cause is a missing
test-driver.yaml
:cc @msau42 @pohly
The text was updated successfully, but these errors were encountered: