-
Notifications
You must be signed in to change notification settings - Fork 446
WIP: v1beta2: migrate logic and tests #7369
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: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 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 |
5cd4460 to
3a80984
Compare
a73ed58 to
47f6338
Compare
47f6338 to
e7ecf33
Compare
e7ecf33 to
2a9be5d
Compare
8356e95 to
0e2c950
Compare
0e2c950 to
916621d
Compare
|
/test pull-kueue-test-e2e-tas-main |
70c4a55 to
0523af3
Compare
Signed-off-by: Michał Woźniak <[email protected]>
0523af3 to
dd79fc8
Compare
|
@mimowo: 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. |
|
PR needs rebase. 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. |
What type of PR is this?
/kind api-change
What this PR does / why we need it:
Which issue(s) this PR fixes:
Part of #7113
Special notes for your reviewer:
No release note because the introduction of v1beta2 was already mentioned.
Does this PR introduce a user-facing change?