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
refactor events utils in e2e #85190
refactor events utils in e2e #85190
Conversation
/retest pull-kubernetes-conformance-image-test |
/retest |
weird, how to retest this case |
it looks like same as #84940 |
/test pull-kubernetes-conformance-image-test |
you can safely ignore |
we are waiting for kind 0.6.0 to ship |
thanks @dims |
Unknown CLA label state. Rechecking for CLA labels. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
|
This seems good for me to share common code between e2e tests as subpackage of e2e framework without any invalid additional dependencies. /retest |
/retest |
@fejta could you help review this PR which related to sig-testing ? thanks |
/retest |
/test pull-kubernetes-conformance-image-test |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danielqsj, oomichi 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 |
/retest |
/test pull-kubernetes-e2e-gce |
/test pull-kubernetes-e2e-kind |
What type of PR is this?
/kind feature
/sig testing
What this PR does / why we need it:
test/e2e/common
is a mixture of tests (test/e2e/common/downward_api.go
) and utility code (test/e2e/common/events.go
). It would be nice to refactor it so that the utility code can be imported without also importing the tests. Most likely a better place for the utility code is undertest/e2e/framework
.For this PR, the specific reason was the usage of
WaitTimeoutForEvent
in a storage test, which then made it impossible to import the storage tests without those other tests. See #83609. OnceWaitTimeoutForEvent
is in an independent utility package, the copied waitTimeoutForEvent can be removed fromtest/e2e/storage/testsuites/volumemode.go
again.Which issue(s) this PR fixes:
part of #83937
Special notes for your reviewer:
/cc @pohly
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: