vsphere-csi-driver
vsphere-csi-driver copied to clipboard
[WIP] temp
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:
Started VCP to CSI migration pipeline... Build Number: 444
Started VCP to CSI migration pipeline... Build Number: 445
VCP to CSI migration build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 18 of 659 Specs in 5701.416 seconds
FAIL! -- 17 Passed | 1 Failed | 0 Pending | 641 Skipped
--- FAIL: TestE2E (5701.48s)
FAIL
Ginkgo ran 1 suite in 1h36m36.077559046s
Test Suite Failed
Started VCP to CSI migration pipeline... Build Number: 446
VCP to CSI migration build status: SUCCESS
Stage before exit: finally
Jenkins E2E Test Results:
------------------------------
Ran 1 of 659 Specs in 818.185 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 658 Skipped
PASS
Ginkgo ran 1 suite in 15m13.228976367s
Test Suite Passed
Started VCP to CSI migration pipeline... Build Number: 449
VCP to CSI migration build status: SUCCESS
Stage before exit: finally
Jenkins E2E Test Results:
------------------------------
Ran 18 of 666 Specs in 3340.308 seconds
SUCCESS! -- 18 Passed | 0 Failed | 0 Pending | 648 Skipped
PASS
Ginkgo ran 1 suite in 56m43.29830924s
Test Suite Passed
/approve
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: kavyashree-r, sashrith
Once this PR has been reviewed and has the lgtm label, please assign chethanv28 for approval by writing /assign @chethanv28 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
/approve
/ok-to-test /lgtm
/approve
/approve /lgtm
/approve cancel
/approve
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Aishwarya-Hebbar, divyenpatel, kavyashree-r, sashrith
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [divyenpatel]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment