You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
increasing resources for the job for integration tests helped a little bit, but didn't fully solve the problem with running Ray (see comment)
we know that setting INTEGRATION_NPROC=3 makes the tests usually pass, but it means lower parallelism enforced on the lightweight tests, which is not ideal
The MK integration tests take around 1min 50s of the time, so we could offload the main integration suite and allow for lower parallelism on the MK suite.
The text was updated successfully, but these errors were encountered:
mimowo
added
the
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
label
Jan 23, 2025
What would you like to be cleaned:
I would like to extract the integration multikueue tests to a dedicated suite.
Why is this needed:
The multikueue integration tests are quite heavy in nature, because:
For the experiments in the context of Kuberay multikueue integrations tests we learned that:
Another argument for the separate CI job is that the integration tests take long (around 18 min currently): https://prow.k8s.io/job-history/gs/kubernetes-ci-logs/logs/periodic-kueue-test-integration-main.
The MK integration tests take around 1min 50s of the time, so we could offload the main integration suite and allow for lower parallelism on the MK suite.
The text was updated successfully, but these errors were encountered: