-
Notifications
You must be signed in to change notification settings - Fork 276
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
Propagate gomega.Gomega on integration/scheduler tests. #3329
Propagate gomega.Gomega on integration/scheduler tests. #3329
Conversation
Skipping CI for Draft Pull Request. |
✅ Deploy Preview for kubernetes-sigs-kueue ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
/lgtm
/approve
LGTM label has been added. Git tree hash: 5af8ade493e59c895d11cd68666f9cf4217eace1
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mbobrovskyi, mimowo 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 |
…igs#3329) * Propagate gomega.Gomega on fair_sharing_test.go. * Propagate gomega.Gomega on podsready/scheduler_test.go. * Propagate gomega.Gomega on preemption_test.go. * Propagate gomega.Gomega on workload_controller_test.go. * Propagate gomega.Gomega on scheduler_test.go.
…igs#3329) * Propagate gomega.Gomega on fair_sharing_test.go. * Propagate gomega.Gomega on podsready/scheduler_test.go. * Propagate gomega.Gomega on preemption_test.go. * Propagate gomega.Gomega on workload_controller_test.go. * Propagate gomega.Gomega on scheduler_test.go.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Propagate gomega.Gomega on integration/scheduler tests.
Which issue(s) this PR fixes:
Part of #3300
Special notes for your reviewer:
Does this PR introduce a user-facing change?