vsphere-csi-driver
vsphere-csi-driver copied to clipboard
kubernetes-sigs
[wip] [do not merge] [fss] use govmomi ListView to wait for CNS tasks
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:
Hi @adikul30. 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.
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/test-infra repository.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: adikul30
Once this PR has been reviewed and has the lgtm label, please assign lipingxue for approval by writing /assign @lipingxue in a comment. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@adikul30: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| pull-vsphere-csi-driver-verify-fmt | db456ec8480c55d30d031ee73d7479ee86b30988 | link | true | /test pull-vsphere-csi-driver-verify-fmt |
| pull-vsphere-csi-driver-unit-test | db456ec8480c55d30d031ee73d7479ee86b30988 | link | true | /test pull-vsphere-csi-driver-unit-test |
| pull-vsphere-csi-driver-verify-vet | db456ec8480c55d30d031ee73d7479ee86b30988 | link | true | /test pull-vsphere-csi-driver-verify-vet |
| pull-vsphere-csi-driver-verify-golangci-lint | db456ec8480c55d30d031ee73d7479ee86b30988 | link | true | /test pull-vsphere-csi-driver-verify-golangci-lint |
| pull-vsphere-csi-driver-verify-staticcheck | db456ec8480c55d30d031ee73d7479ee86b30988 | link | true | /test pull-vsphere-csi-driver-verify-staticcheck |
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/test-infra repository. I understand the commands that are listed here.
@adikul30: PR needs rebase.
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/test-infra repository.
Build ID: 1545
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
------------------------------
Ran 1 of 692 Specs in 351.985 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 691 Skipped
PASS
Ginkgo ran 1 suite in 6m56.524615463s
Test Suite Passed
--
Ran 11 of 692 Specs in 2131.477 seconds
FAIL! - Interrupted by User -- 5 Passed | 6 Failed | 0 Pending | 681 Skipped
--- FAIL: TestE2E (2131.50s)
FAIL
Ginkgo ran 1 suite in 35m46.337201928s
Test Suite Failed
Build ID: 1546
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 692 Specs in 7.851 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 691 Skipped
--- FAIL: TestE2E (7.87s)
FAIL
Ginkgo ran 1 suite in 1m7.149765868s
Test Suite Failed
Build ID: 1547
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
------------------------------
Ran 1 of 692 Specs in 333.669 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 691 Skipped
PASS
Ginkgo ran 1 suite in 6m34.723816527s
Test Suite Passed
--
------------------------------
Ran 12 of 692 Specs in 4387.484 seconds
SUCCESS! -- 12 Passed | 0 Failed | 0 Pending | 680 Skipped
PASS
Ginkgo ran 1 suite in 1h13m22.084209877s
Test Suite Passed
--
Ran 40 of 692 Specs in 1081.343 seconds
FAIL! -- 39 Passed | 1 Failed | 0 Pending | 652 Skipped
Ginkgo ran 1 suite in 18m16.249928558s
Test Suite Failed
Build ID: 1548
Block vanilla build status: SUCCESS
Stage before exit: e2e-tests
Jenkins E2E Test Results:
------------------------------
Ran 1 of 692 Specs in 102.525 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 691 Skipped
PASS
Ginkgo ran 1 suite in 3m5.82359052s
Test Suite Passed
Build ID: 1549
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
------------------------------
Ran 1 of 692 Specs in 316.713 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 691 Skipped
PASS
Ginkgo ran 1 suite in 6m45.085467261s
Test Suite Passed
--
Ran 12 of 692 Specs in 4283.006 seconds
FAIL! -- 10 Passed | 2 Failed | 0 Pending | 680 Skipped
--- FAIL: TestE2E (4283.04s)
FAIL
Ginkgo ran 1 suite in 1h11m48.349428042s
Test Suite Failed
Build ID: 1553
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
------------------------------
Ran 1 of 692 Specs in 326.725 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 691 Skipped
PASS
Ginkgo ran 1 suite in 6m48.854233723s
Test Suite Passed
--
Ran 12 of 692 Specs in 5392.264 seconds
FAIL! -- 7 Passed | 5 Failed | 0 Pending | 680 Skipped
--- FAIL: TestE2E (5392.30s)
FAIL
Ginkgo ran 1 suite in 1h30m12.341628724s
Test Suite Failed
Build ID: 1557
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
------------------------------
Ran 1 of 692 Specs in 333.437 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 691 Skipped
PASS
Ginkgo ran 1 suite in 6m38.85085865s
Test Suite Passed
--
Ran 8 of 692 Specs in 3626.581 seconds
FAIL! - Interrupted by User -- 3 Passed | 5 Failed | 0 Pending | 684 Skipped
--- FAIL: TestE2E (3626.62s)
FAIL
Ginkgo ran 1 suite in 1h0m42.727251257s
Test Suite Failed
Build ID: 1561
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
------------------------------
Ran 1 of 692 Specs in 322.873 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 691 Skipped
PASS
Ginkgo ran 1 suite in 6m34.026882517s
Test Suite Passed
--
Ran 12 of 692 Specs in 4993.549 seconds
FAIL! -- 9 Passed | 3 Failed | 0 Pending | 680 Skipped
--- FAIL: TestE2E (4993.57s)
FAIL
Ginkgo ran 1 suite in 1h23m30.211546373s
Test Suite Failed
Build ID: 1562
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
------------------------------
Ran 1 of 692 Specs in 324.431 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 691 Skipped
PASS
Ginkgo ran 1 suite in 6m41.100397645s
Test Suite Passed
--
------------------------------
Ran 12 of 692 Specs in 4502.199 seconds
SUCCESS! -- 12 Passed | 0 Failed | 0 Pending | 680 Skipped
PASS
Ginkgo ran 1 suite in 1h15m19.9821369s
Test Suite Passed
--
Ran 40 of 692 Specs in 757.357 seconds
FAIL! -- 38 Passed | 2 Failed | 0 Pending | 652 Skipped
Ginkgo ran 1 suite in 12m54.444469698s
Test Suite Failed
Build ID: 1563
Block vanilla build status: SUCCESS
Stage before exit: e2e-tests
Jenkins E2E Test Results:
------------------------------
Ran 2 of 692 Specs in 992.185 seconds
SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 690 Skipped
PASS
Ginkgo ran 1 suite in 17m56.544559156s
Test Suite Passed
Build ID: 1567
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
------------------------------
Ran 1 of 692 Specs in 328.418 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 691 Skipped
PASS
Ginkgo ran 1 suite in 7m9.22986679s
Test Suite Passed
--
Ran 12 of 692 Specs in 4822.404 seconds
FAIL! -- 11 Passed | 1 Failed | 0 Pending | 680 Skipped
--- FAIL: TestE2E (4822.43s)
FAIL
Ginkgo ran 1 suite in 1h20m44.491991067s
Test Suite Failed
Build ID: 1569
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
------------------------------
Ran 1 of 692 Specs in 328.801 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 691 Skipped
PASS
Ginkgo ran 1 suite in 7m13.466257449s
Test Suite Passed
--
Ran 12 of 692 Specs in 5514.045 seconds
FAIL! -- 6 Passed | 6 Failed | 0 Pending | 680 Skipped
--- FAIL: TestE2E (5514.07s)
FAIL
Ginkgo ran 1 suite in 1h32m14.35468841s
Test Suite Failed
Build ID: 1570
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
------------------------------
Ran 1 of 692 Specs in 442.737 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 691 Skipped
PASS
Ginkgo ran 1 suite in 9m4.78029354s
Test Suite Passed
--
Ran 12 of 692 Specs in 4680.752 seconds
FAIL! -- 11 Passed | 1 Failed | 0 Pending | 680 Skipped
--- FAIL: TestE2E (4680.78s)
FAIL
Ginkgo ran 1 suite in 1h18m23.672632857s
Test Suite Failed