-
Notifications
You must be signed in to change notification settings - Fork 180
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]Storage quota changes in supervisor for policy driven allocation tests #3032
base: master
Are you sure you want to change the base?
[WIP]Storage quota changes in supervisor for policy driven allocation tests #3032
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. |
Started WCP block pre-checkin pipeline... Build Number: 1541 |
|
bd16764
to
eea879b
Compare
Started WCP block pre-checkin pipeline... Build Number: 1542 |
|
Started WCP block pre-checkin pipeline... Build Number: 1543 |
|
eea879b
to
af3050a
Compare
Started WCP block pre-checkin pipeline... Build Number: 1544 |
|
af3050a
to
7c5ded5
Compare
7c5ded5
to
e06dc27
Compare
Started GC block pre-checkin pipeline... Build Number: 1 |
|
Started GC block pre-checkin pipeline... Build Number: 2 |
|
Started GC block pre-checkin pipeline... Build Number: 3 |
|
Started GC block pre-checkin pipeline... Build Number: 4 |
|
Started GC block pre-checkin pipeline... Build Number: 5 |
|
Started GC block pre-checkin pipeline... Build Number: 6 |
|
Started GC block pre-checkin pipeline... Build Number: 7 |
e06dc27
to
ececb1d
Compare
|
Started GC block pre-checkin pipeline... Build Number: 8 |
|
747df1b
to
5d2df9f
Compare
Started GC block pre-checkin pipeline... Build Number: 9 |
|
5d2df9f
to
ab63751
Compare
Started GC block pre-checkin pipeline... Build Number: 10 |
|
Started GC block pre-checkin pipeline... Build Number: 11 |
|
Started GC block pre-checkin pipeline... Build Number: 12 |
|
Started GC block pre-checkin pipeline... Build Number: 13 |
|
Started GC block pre-checkin pipeline... Build Number: 14 |
|
Started GC block pre-checkin pipeline... Build Number: 16 |
|
Started GC block pre-checkin pipeline... Build Number: 17 |
|
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: