-
Notifications
You must be signed in to change notification settings - Fork 435
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
[WIP] Add documentation on running e2e tests locally #5362
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5362 +/- ##
=======================================
Coverage 52.58% 52.58%
=======================================
Files 272 272
Lines 29468 29468
=======================================
Hits 15495 15495
Misses 13165 13165
Partials 808 808 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
I was able to get one test run locally
For my reference, the chain of options used to run an e2e test is |
This comment was marked as outdated.
This comment was marked as outdated.
b79e3a1
to
e1352fb
Compare
76acd8a
to
f097398
Compare
67ccfd0
to
bea3809
Compare
e367618
to
6579b62
Compare
/retest |
c7b1ad6
to
d5ff647
Compare
/retest |
- update Makefile targets for local e2e - Add script on peering vnets
d5ff647
to
f2fa86e
Compare
/retest |
/retest |
/retest |
/test pull-cluster-api-provider-azure-ci-entrypoint |
/test pull-cluster-api-provider-azure-windows-custom-builds |
/pull-cluster-api-provider-azure-capi-e2e |
/retest |
/test pull-cluster-api-provider-azure-windows-with-ci-artifacts |
/test pull-cluster-api-provider-azure-windows-custom-builds |
So closing this PR to open up a new one #5489 for a better test signal. |
@nawazkh: Closed this PR. 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-sigs/prow repository. |
@nawazkh: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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-sigs/prow repository. I understand the commands that are listed here. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #5268
Special notes for your reviewer:
TODOs:
Release note: