-
Notifications
You must be signed in to change notification settings - Fork 40.6k
Add Stress Tests for VolumeAttributesClass #129918
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
base: master
Are you sure you want to change the base?
Add Stress Tests for VolumeAttributesClass #129918
Conversation
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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-sigs/prow repository. |
d6ad82a
to
5b53ec6
Compare
f652658
to
fb0c190
Compare
/test pull-kubernetes-e2e-kind |
/release-note-none |
@carlory: you can only set the release note label to release-note-none if the release-note block in the PR body text is empty or "none". In response to this:
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-sigs/prow repository. |
@sunnylovestiramisu It looks good to me. Do we have an existing job in test-infra that runs this? |
Cool. I find it and the job is successful. Thank you. /lgtm |
LGTM label has been added. Git tree hash: cfe1a6d2e8550cb01b27deecc60837a9c70c6e3c
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: carlory, sunnylovestiramisu 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 |
/hold the job pull-kubernetes-e2e-gce-storage-slow doesn't run new tests.
https://github.com/kubernetes/test-infra/blob/f52ea67ed62d5403b40957d3fcce41efdc39b882/config/jobs/kubernetes/sig-storage/sig-storage-gce-config.yaml#L48 @sunnylovestiramisu |
:/ That is weird, let me try the test arguments locally. |
fb0c190
to
9d9a313
Compare
New changes are detected. LGTM label has been removed. |
Is the cluster that is running pull-kubernetes-e2e-gce-storage-slow has FeatureGate:VolumeAttributesClass enabled? We will need to add --env=KUBE_FEATURE_GATES="VolumeAttributesClass=true" to the file you pointed out? |
/test pull-kubernetes-e2e-storage-kind-alpha-beta-features |
1 similar comment
/test pull-kubernetes-e2e-storage-kind-alpha-beta-features |
0aae584
to
9d9a313
Compare
@sunnylovestiramisu: 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-sigs/prow repository. I understand the commands that are listed here. |
WithFeatureGate will add a So, I'm not sure whether the Maybe we need to create a new temporary job for this? cc @pohly do we have an existing job for stress tests in sig-testing? |
Update that job to use
No, not at the moment. |
The bigger issue is that a real stress test could lead to test flakes in tests which run in parallel. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Stress test coverage for VolumeAttributesClass, add to pull-kubernetes-e2e-gce-storage-slow after VolumeAttributesClass feature gate is on.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Ran
go test -timeout=0 -v ./test/e2e -provider=skeleton -kubeconfig $HOME/.kube/config -ginkgo.v -ginkgo.focus='\[FeatureGate:VolumeAttributesClass\]' -gce-zone=us-central1-b -gce-project {MY_GCP_PROJECT}
succeeded locallyDoes this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: