-
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
Improve storage test skipping pattern. #103876
Conversation
Including a skip method as the first line of a test does not prevent the test to fail in the BeforeEach function. If the test is skipped because of a tag in the name, then we can prevent such odd behavior.
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
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. |
Welcome @juanfescobar! |
Hi @juanfescobar. 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. |
/assign @spiffxp |
/ok-to-test |
ref: #73168 |
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.
Thanks, this is a much better way of describing that a test is flaky
/milestone v1.23
If this is impacting v1.22 we can change, otherwise we should wait until the branch opens back up
/lgtm |
@@ -283,8 +283,8 @@ var _ = utils.SIGDescribe("PersistentVolumes-local ", func() { | |||
e2epod.DeletePodOrFail(config.client, config.ns, pod2.Name) | |||
}) | |||
|
|||
ginkgo.It("should set different fsGroup for second pod if first pod is deleted", func() { | |||
e2eskipper.Skipf("Disabled temporarily, reopen after #73168 is fixed") |
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.
FYI @kubernetes/sig-storage-bugs this previous approach does not result in skipping the BeforeEach
which can then fail (setting up volumes to test) and waste time. It also prevents the possibility of actually running the test. When the BeforeEach fails it will report red, resulting in a dashboard of Red or no result which can be confusing 🙃
We should prefer adding a [Flaky]
tag or similar instead which the user can select and should prevent running the case entirely instead of running it up to the skip line (including Before*).
/triage accepted |
/lgtm |
#102344 may actually fix the flakiness. We can followup and monitor the test once it's running again. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, juanfescobar, msau42, spiffxp 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 |
Thanks @msau42 I meant for you to /approve I didn't realize my review got flagged as an approve as well |
/ok-to-test |
/retest Review the full test history for this PR. Silence the bot with an |
/retest |
What type of PR is this?
/kind bug
/kind flake
What this PR does / why we need it:
Include a [Flaky] tag in the test name so that it can be always skipped, as it is expected currently.
The reason for this skipping-pattern update is that the current one does not address the current expected behavior. Including a skip method as the first line of a test does not prevent the test to run the BeforeEach function (which can fail before the test is skipped), and thus the test could fail even though it was supposed to be always skipped.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: