-
Notifications
You must be signed in to change notification settings - Fork 38.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tag ginkgo tests affected by pdcsi migration for skipping #105052
Conversation
Hi @leiyiz. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the 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. |
/ok-to-test |
/retest |
/priority important-soon |
cd08864
to
178618f
Compare
@@ -43,7 +43,7 @@ import ( | |||
"k8s.io/kubernetes/test/e2e/storage/utils" | |||
) | |||
|
|||
var _ = utils.SIGDescribe("Mounted volume expand", func() { | |||
var _ = utils.SIGDescribe("Mounted volume expand [Feature:StorageProviderGCEPD]", func() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gnufied do we still need these tests or do the testsuite tests cover it? https://github.com/kubernetes/kubernetes/blob/master/test/e2e/storage/testsuites/volume_expand.go
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
volume expand tests are also covered in pdcsi migration tests
https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/blob/master/test/run-k8s-integration-ci.sh#L32
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, what I mean is are these tests in mounted_volume_resize still needed or do we have equivalent test cases in testsuites/volume_expand.go
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this test in mounted_volume_resize will also run due to focus [V|v]olume\sexpand
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This e2e exercises a test which is not covered by test suite. I think we had some bug where if while volume is mounted and you quickly deleted the pod and recreated it (where global mount does not have chance to be removed), resize won't work. This e2e exercises that scenario.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at this test case, I don't see anything that prevents the test from being imported into testsuites/volume_expand.go. Can you file a bug to track moving this test over? For now I think adding the tag to it is fine, but we'll want to move the test and remove the tag before 1.23 code freeze.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no problem. #105581
8d84abe
to
d919128
Compare
Can you also open an issue to track the upgrade test issue? |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: leiyiz, msau42 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…rageclass check for statefulset and upgrade tests
d919128
to
822cc33
Compare
no problem #105595 |
/lgtm |
@leiyiz: The following tests failed, say
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. |
/retest |
What type of PR is this?
What this PR does / why we need it:
When we turn on
CSIMigrationGCE
, some prow tests (and unit tests) are going to fail due to their reliance on gcepd driver. we need to tag them with an appropriate tag so that we can skip them in release-blocking jobs and presubmits.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: