-
Notifications
You must be signed in to change notification settings - Fork 301
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
Get e2e tests working in prow #312
Conversation
/test pull-cloud-provider-aws-e2e |
362ff57
to
b844034
Compare
/test pull-cloud-provider-aws-e2e |
b844034
to
ff8521a
Compare
/test pull-cloud-provider-aws-e2e |
* Create test run directory earlier to avoid failure * Install e2e prereqs
ff8521a
to
b50bd5c
Compare
popd | ||
|
||
if [[ "${DOWN}" = "yes" ]]; then | ||
kops delete cluster --name "${CLUSTER_NAME}" --yes | ||
${test_run}/kops delete cluster --name "${CLUSTER_NAME}" --yes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how did the binary get here? is kops also an e2e-tool?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question, its downloaded by the kubetest2 kops deployer: https://github.com/kubernetes/kops/blob/master/tests/e2e/pkg/kops/download.go#L32-L55
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we call kubetest2 --down (or whatever the right arguments are) then instead, so we don't have to care about that implementation detail?
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nckturner, 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 |
…-upstream-release-1.22 Automated cherry pick of #312: Fix e2e failures
…f-#304-#312-upstream-release-1.20 Cherry pick E2E test changes and fix failing tagging controller test for 1.20
…f-#304-#312-upstream-release-1.21 Cherry pick E2E test changes and fix failing tagging controller test for 1.21
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
Fixes failing e2e test.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: