-
Notifications
You must be signed in to change notification settings - Fork 181
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]vsan stretch with CSI snapshot testcases #3050
base: master
Are you sure you want to change the base?
[WIP]vsan stretch with CSI snapshot testcases #3050
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Aishwarya-Hebbar 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 |
Hi @Aishwarya-Hebbar. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
6deda0b
to
3aea347
Compare
Started GC block pre-checkin pipeline... Build Number: 143 |
|
3aea347
to
285d7ae
Compare
Started GC block pre-checkin pipeline... Build Number: 144 |
|
Started GC block pre-checkin pipeline... Build Number: 145 |
|
285d7ae
to
20d3d63
Compare
Started GC block pre-checkin pipeline... Build Number: 146 |
7639547
to
30d6499
Compare
|
7a7882f
to
59fab1a
Compare
Started GC block pre-checkin pipeline... Build Number: 147 |
|
Started GC block pre-checkin pipeline... Build Number: 148 |
59fab1a
to
ddbec9d
Compare
|
|
Started GC block pre-checkin pipeline... Build Number: 158 |
Started GC block pre-checkin pipeline... Build Number: 159 |
|
|
Started GC block pre-checkin pipeline... Build Number: 160 |
ab7e5f5
to
3b1eca9
Compare
Started GC block pre-checkin pipeline... Build Number: 161 |
|
Started GC block pre-checkin pipeline... Build Number: 162 |
|
Started GC block pre-checkin pipeline... Build Number: 163 |
|
Started GC block pre-checkin pipeline... Build Number: 164 |
|
3b1eca9
to
d67368c
Compare
Started GC block pre-checkin pipeline... Build Number: 165 |
|
Started GC block pre-checkin pipeline... Build Number: 166 |
|
d67368c
to
d7a4478
Compare
Started GC block pre-checkin pipeline... Build Number: 167 |
|
|
Started GC block pre-checkin pipeline... Build Number: 169 |
|
Started GC block pre-checkin pipeline... Build Number: 170 |
|
d7a4478
to
11f44e0
Compare
What this PR does / why we need it:
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #Testing done:
A PR must be marked "[WIP]", if no test result is provided. A WIP PR won't be reviewed, nor merged.
The requester can determine a sufficient test, e.g. build for a cosmetic change, E2E test in a predeployed setup, etc.
For new features, new tests should be done, in addition to regression tests.
If jtest is used to trigger precheckin tests, paste the result after jtest completes and remove [WIP] in the PR subject.
The review cycle will start, only after "[WIP]" is removed from the PR subject.
Special notes for your reviewer:
Release note: