-
Notifications
You must be signed in to change notification settings - Fork 78
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
Fix CI #172
Fix CI #172
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wongma7 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
…mage value deciding both
some tests say:
|
lustre is not in the kernel anymore, need to install. |
1b49f17
to
b2dc1ac
Compare
42cc073
to
d8fe80b
Compare
f9edd35
to
dc272e3
Compare
|
/retest |
two Disruptive subPath tests failed in https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_aws-fsx-csi-driver/172/pull-aws-fsx-csi-driver-e2e/1403479400787218432. They might be "real" failures, but should skip Disruptive in CI anyhow. I will leave as TODO to figure out if there is a real bug wrt subPath and fsx |
lgtm |
/lgtm |
Is this a bug fix or adding new feature? fix
What is this PR about? / Why do we need it? CI has been blcoked for a long time and I didn't notice:
https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_aws-fsx-csi-driver/166/pull-aws-fsx-csi-driver-e2e/1370094655802183680
What testing is done?