vsphere-csi-driver
vsphere-csi-driver copied to clipboard
Published
20 hours ago •
kubernetes-sigs
kubernetes-sigs
[WIP]windows support
What this PR does / why we need it: This PR has the changes for test code to validate the windows CSI
Hi @marunachalam. 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.
Build ID: 6
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
JUnit report was created: /home/worker/workspace/Windows-Precheckin-BlockVanilla/6/vsphere-csi-driver/tests/e2e/junit.xml
Ran 1 of 272 Specs in 446.584 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 271 Skipped
PASS
Ginkgo ran 1 suite in 8m34.970351001s
Test Suite Passed
--
Ran 12 of 272 Specs in 7077.249 seconds
FAIL! -- 8 Passed | 4 Failed | 0 Pending | 260 Skipped
--- FAIL: TestE2E (7077.37s)
FAIL
Ginkgo ran 1 suite in 1h58m11.197319645s
Test Suite Failed
Build ID: 7
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
JUnit report was created: /home/worker/workspace/Windows-Precheckin-BlockVanilla/7/vsphere-csi-driver/tests/e2e/junit.xml
Ran 1 of 4 Specs in 285.038 seconds
FAIL! -- 1 Passed | 0 Failed | 0 Pending | 3 Skipped
Ginkgo ran 1 suite in 5m44.125722171s
Test Suite Failed
Build ID: 9
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 272 Specs in 4.646 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 271 Skipped
--- FAIL: TestE2E (4.76s)
FAIL
Ginkgo ran 1 suite in 1m17.962453473s
Test Suite Failed
Build ID: 10
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 272 Specs in 628.466 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 271 Skipped
--- FAIL: TestE2E (628.58s)
FAIL
Ginkgo ran 1 suite in 11m37.19110136s
Test Suite Failed
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
JUnit report was created: /home/worker/workspace/marunachalam-windows-regression/Results/5/vsphere-csi-driver/tests/e2e/junit.xml
Ran 1 of 1 Specs in 354.195 seconds
FAIL! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
Ginkgo ran 1 suite in 7m11.856604873s
Test Suite Failed
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
[Fail] Volume Expansion Test [It] [csi-block-vanilla] [csi-supervisor] [csi-block-vanilla-parallelized] Verify online volume expansion by updating PVC with different sizes concurrently
/home/worker/workspace/marunachalam-windows-regression/Results/6/go/pkg/mod/k8s.io/[email protected]/test/e2e/framework/util.go:602
Ran 58 of 259 Specs in 28673.293 seconds
FAIL! -- 35 Passed | 23 Failed | 0 Pending | 201 Skipped
Ginkgo ran 1 suite in 7h59m9.078820574s
Test Suite Failed
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 274 Specs in 729.566 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 273 Skipped
--- FAIL: TestE2E (729.68s)
FAIL
Ginkgo ran 1 suite in 13m12.268538672s
Test Suite Failed
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 274 Specs in 5.270 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 273 Skipped
--- FAIL: TestE2E (5.38s)
FAIL
Ginkgo ran 1 suite in 53.664843789s
Test Suite Failed
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
JUnit report was created: /home/worker/workspace/marunachalam-windows-regression/Results/9/vsphere-csi-driver/tests/e2e/junit.xml
Ran 1 of 253 Specs in 214.858 seconds
FAIL! -- 1 Passed | 0 Failed | 0 Pending | 252 Skipped
Ginkgo ran 1 suite in 4m22.323059268s
Test Suite Failed
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 274 Specs in 607.667 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 273 Skipped
--- FAIL: TestE2E (607.78s)
FAIL
Ginkgo ran 1 suite in 10m57.388549228s
Test Suite Failed
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 274 Specs in 914.819 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 273 Skipped
--- FAIL: TestE2E (914.92s)
FAIL
Ginkgo ran 1 suite in 16m18.179890929s
Test Suite Failed
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 274 Specs in 915.663 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 273 Skipped
--- FAIL: TestE2E (915.78s)
FAIL
Ginkgo ran 1 suite in 16m6.084441672s
Test Suite Failed