Closed Aishwarya-Hebbar closed 1 month ago
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: 1
Build ID: 1
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 850 Specs in 4.937 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 849 Skipped
--- FAIL: TestE2E (5.01s)
FAIL
Ginkgo ran 1 suite in 1m21.9919817s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 2
Build ID: 2
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 850 Specs in 525.050 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 849 Skipped
--- FAIL: TestE2E (525.13s)
FAIL
Ginkgo ran 1 suite in 9m53.018612549s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 3
Build ID: 3
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 850 Specs in 21.558 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 849 Skipped
--- FAIL: TestE2E (21.63s)
FAIL
Ginkgo ran 1 suite in 1m38.324424251s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 4
Build ID: 4
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 850 Specs in 1.874 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 849 Skipped
--- FAIL: TestE2E (1.95s)
FAIL
Ginkgo ran 1 suite in 1m11.905579351s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 5
Build ID: 5
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 850 Specs in 45.338 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 849 Skipped
--- FAIL: TestE2E (45.40s)
FAIL
Ginkgo ran 1 suite in 1m59.004036027s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 6
Build ID: 6
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 850 Specs in 44.934 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 849 Skipped
--- FAIL: TestE2E (45.00s)
FAIL
Ginkgo ran 1 suite in 1m52.509520374s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 7
Build ID: 7
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 850 Specs in 55.392 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 849 Skipped
--- FAIL: TestE2E (55.46s)
FAIL
Ginkgo ran 1 suite in 2m5.707034768s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 8
Build ID: 8
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 850 Specs in 367.730 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 849 Skipped
--- FAIL: TestE2E (367.80s)
FAIL
Ginkgo ran 1 suite in 7m21.788940291s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 9
Build ID: 9
Block vanilla build status: SUCCESS
Stage before exit: e2e-tests
Jenkins E2E Test Results:
------------------------------
Ran 1 of 850 Specs in 202.176 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 849 Skipped
PASS
Ginkgo ran 1 suite in 4m31.995774485s
Test Suite Passed
Started Vanilla block pre-checkin pipeline... Build Number: 10
Build ID: 10
Block vanilla build status: SUCCESS
Stage before exit: e2e-tests
Jenkins E2E Test Results:
------------------------------
Ran 1 of 850 Specs in 257.164 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 849 Skipped
PASS
Ginkgo ran 1 suite in 5m24.827031045s
Test Suite Passed
Started Vanilla block pre-checkin pipeline... Build Number: 11
Build ID: 11
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 31 of 850 Specs in 527.215 seconds
FAIL! -- 0 Passed | 31 Failed | 0 Pending | 819 Skipped
--- FAIL: TestE2E (527.32s)
FAIL
Ginkgo ran 1 suite in 9m53.675074327s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 12
Build ID: 12
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 4 of 850 Specs in 513.989 seconds
FAIL! -- 0 Passed | 4 Failed | 0 Pending | 846 Skipped
--- FAIL: TestE2E (514.08s)
FAIL
Ginkgo ran 1 suite in 9m37.573153877s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 13
Build ID: 13
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 4 of 850 Specs in 1267.804 seconds
FAIL! -- 3 Passed | 1 Failed | 0 Pending | 846 Skipped
--- FAIL: TestE2E (1267.89s)
FAIL
Ginkgo ran 1 suite in 22m12.763493872s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 14
Build ID: 14
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 4 of 850 Specs in 551.129 seconds
FAIL! -- 2 Passed | 2 Failed | 0 Pending | 846 Skipped
--- FAIL: TestE2E (551.22s)
FAIL
Ginkgo ran 1 suite in 10m26.419027867s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 15
Build ID: 15
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 4 of 850 Specs in 429.468 seconds
FAIL! -- 2 Passed | 2 Failed | 0 Pending | 846 Skipped
--- FAIL: TestE2E (429.57s)
FAIL
Ginkgo ran 1 suite in 8m17.026919701s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 16
Build ID: 16
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 4 of 850 Specs in 825.801 seconds
FAIL! -- 2 Passed | 2 Failed | 0 Pending | 846 Skipped
--- FAIL: TestE2E (825.89s)
FAIL
Ginkgo ran 1 suite in 14m54.454877256s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 17
Build ID: 17
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 4 of 850 Specs in 1021.595 seconds
FAIL! -- 3 Passed | 1 Failed | 0 Pending | 846 Skipped
--- FAIL: TestE2E (1021.70s)
FAIL
Ginkgo ran 1 suite in 18m11.976440599s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 18
Build ID: 18
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 4 of 850 Specs in 1133.033 seconds
FAIL! -- 3 Passed | 1 Failed | 0 Pending | 846 Skipped
--- FAIL: TestE2E (1133.13s)
FAIL
Ginkgo ran 1 suite in 20m4.776267401s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 19
Build ID: 19
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 4 of 850 Specs in 1105.193 seconds
FAIL! -- 3 Passed | 1 Failed | 0 Pending | 846 Skipped
--- FAIL: TestE2E (1105.28s)
FAIL
Ginkgo ran 1 suite in 19m30.633000676s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 21
Build ID: 21
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 850 Specs in 128.959 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 849 Skipped
--- FAIL: TestE2E (129.02s)
FAIL
Ginkgo ran 1 suite in 3m14.142333952s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 23
Build ID: 23
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 850 Specs in 2.527 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 849 Skipped
--- FAIL: TestE2E (2.62s)
FAIL
Ginkgo ran 1 suite in 1m26.301390581s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 24
Build ID: 24
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 850 Specs in 603.379 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 849 Skipped
--- FAIL: TestE2E (603.47s)
FAIL
Ginkgo ran 1 suite in 11m33.672091482s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 25
Build ID: 25
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 850 Specs in 141.570 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 849 Skipped
--- FAIL: TestE2E (141.66s)
FAIL
Ginkgo ran 1 suite in 3m58.429867014s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 26
Build ID: 26
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 850 Specs in 151.159 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 849 Skipped
--- FAIL: TestE2E (151.25s)
FAIL
Ginkgo ran 1 suite in 3m59.055769884s
Test Suite Failed
Started Vanilla block pre-checkin pipeline... Build Number: 27
What this PR does / why we need it: HCI mesh tests automation for disruptive scenarios.
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: https://gist.github.com/Aishwarya-Hebbar/b4839ec294ce65689a3f8747640cda80