Open Aishwarya-Hebbar opened 2 weeks ago
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Aishwarya-Hebbar Once this PR has been reviewed and has the lgtm label, please assign sipriyaa for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
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 /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
Started Vanilla block pre-checkin pipeline... Build Number: 57
Build ID: 57
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 2 of 883 Specs in 6.854 seconds
FAIL! -- 0 Passed | 2 Failed | 0 Pending | 881 Skipped
--- FAIL: TestE2E (6.92s)
FAIL
Ginkgo ran 1 suite in 1m14.741392137s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 58
Build ID: 58
Block vanilla build status: SUCCESS
Stage before exit: e2e-tests
Jenkins E2E Test Results:
------------------------------
Ran 0 of 883 Specs in 0.016 seconds
SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 883 Skipped
PASS
Ginkgo ran 1 suite in 1m9.970276826s
Test Suite Passed
Started Vanilla block pre-checkin pipeline... Build Number: 59
Build ID: 59
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 883 Specs in 2.266 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 882 Skipped
--- FAIL: TestE2E (2.34s)
FAIL
Ginkgo ran 1 suite in 1m10.322770963s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 60
Build ID: 60
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 883 Specs in 602.320 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 882 Skipped
--- FAIL: TestE2E (602.38s)
FAIL
Ginkgo ran 1 suite in 11m12.453021635s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 61
Build ID: 61
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 883 Specs in 681.638 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 882 Skipped
--- FAIL: TestE2E (681.70s)
FAIL
Ginkgo ran 1 suite in 12m35.802499339s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 62
Build ID: 62
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 883 Specs in 1.709 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 882 Skipped
--- FAIL: TestE2E (1.76s)
FAIL
Ginkgo ran 1 suite in 1m4.672149074s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 63
Build ID: 63
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 883 Specs in 1978.573 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 882 Skipped
--- FAIL: TestE2E (1978.63s)
FAIL
Ginkgo ran 1 suite in 33m58.360084592s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 64
Build ID: 64
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 883 Specs in 780.440 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 882 Skipped
--- FAIL: TestE2E (780.50s)
FAIL
Ginkgo ran 1 suite in 14m2.605360551s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 65
Build ID: 65
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 883 Specs in 41.173 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 882 Skipped
--- FAIL: TestE2E (41.23s)
FAIL
Ginkgo ran 1 suite in 1m41.249841917s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 66
Build ID: 66
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 883 Specs in 2.339 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 882 Skipped
--- FAIL: TestE2E (2.40s)
FAIL
Ginkgo ran 1 suite in 1m0.913135137s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 67
Build ID: 67
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 883 Specs in 2105.357 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 882 Skipped
--- FAIL: TestE2E (2105.41s)
FAIL
Ginkgo ran 1 suite in 36m2.350073213s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 68
Build ID: 68
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 883 Specs in 1197.676 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 882 Skipped
--- FAIL: TestE2E (1197.72s)
FAIL
Ginkgo ran 1 suite in 20m57.351936253s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 69
Build ID: 69
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 883 Specs in 1197.573 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 882 Skipped
--- FAIL: TestE2E (1197.63s)
FAIL
Ginkgo ran 1 suite in 20m53.875702637s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 70
Build ID: 70
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 883 Specs in 676.440 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 882 Skipped
--- FAIL: TestE2E (676.49s)
FAIL
Ginkgo ran 1 suite in 12m14.871633698s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 71
Build ID: 71
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 883 Specs in 1226.330 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 882 Skipped
--- FAIL: TestE2E (1226.38s)
FAIL
Ginkgo ran 1 suite in 21m20.629391111s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 72
Build ID: 72
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 883 Specs in 602.996 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 882 Skipped
--- FAIL: TestE2E (603.05s)
FAIL
Ginkgo ran 1 suite in 11m4.166681684s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 73
Build ID: 73
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 883 Specs in 3.185 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 882 Skipped
--- FAIL: TestE2E (3.28s)
FAIL
Ginkgo ran 1 suite in 1m36.833311978s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 74
Build ID: 74
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 883 Specs in 602.917 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 882 Skipped
--- FAIL: TestE2E (603.01s)
FAIL
Ginkgo ran 1 suite in 11m54.108933959s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 75
Build ID: 75
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 883 Specs in 2038.115 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 882 Skipped
--- FAIL: TestE2E (2038.21s)
FAIL
Ginkgo ran 1 suite in 35m26.917051397s
Test Suite Failed
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: