-
Notifications
You must be signed in to change notification settings - Fork 286
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
Introduce multikueue integration test target for separate CI run #4042
Introduce multikueue integration test target for separate CI run #4042
Conversation
Skipping CI for Draft Pull Request. |
/ok-to-test |
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
879fefe
to
64b5584
Compare
@mszadkow would it be easier to nest the structure of the suites to have singlecluster and multicluster grouping folders as for e2e tests? How otherwise are we to run the main integration tests, excluding multkueue? |
Yes, all is possible. |
64b5584
to
886897d
Compare
Answering your question about file path.Join and usage of PROJECT_DIR. |
17759f3
to
e44d8ec
Compare
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 overall
e44d8ec
to
30a43cd
Compare
I see, I don't have a strong view on that, but it feels more consistent with what we do for e2e tests. |
/assign @mbobrovskyi |
30a43cd
to
67895b7
Compare
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
Thanks!
LGTM label has been added. Git tree hash: c841c5f35159868c715506f99345c6f82877fb70
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mbobrovskyi, mimowo, mszadkow 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 |
What type of PR is this?
/kind feature
What this PR does / why we need it:
The multikueue integration tests are quite heavy in nature.
Thus to meet the demand for new integrations in multikueue in the future we need to separate them from the existing tests.
Which issue(s) this PR fixes:
Relates to #4040
Special notes for your reviewer:
Does this PR introduce a user-facing change?