-
Notifications
You must be signed in to change notification settings - Fork 9
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
Split test_seldon_servers
in order to be able to run tests on each SeldonDeployment separately
#229
Labels
enhancement
New feature or request
Projects
Comments
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5049.
|
This was referenced Nov 27, 2023
orfeas-k
added a commit
that referenced
this issue
Dec 4, 2023
…#228) - tests(integration): Configure test_seldon_servers test in order to be able to run tests only on one of the SeldonDeployments CRs. This can be done using pytest's-k flag and the corresponding keyword. You can find keywords in CONTRIBUTING.md or by looking at the id field of seldon_servers.py objects. - tests(integration): Remove limits from SeldonDeployments applied. - Update CONTRIBUTING.md with instructions on how to run tests separately. - ci: Run test_seldon_servers integration test for each SeldonDeployment CR in a distinct GH runner. - ci: Extract automatically tox integration environments using a script. Fixes #229
orfeas-k
added a commit
that referenced
this issue
Jan 23, 2024
…#228) - tests(integration): Configure test_seldon_servers test in order to be able to run tests only on one of the SeldonDeployments CRs. This can be done using pytest's-k flag and the corresponding keyword. You can find keywords in CONTRIBUTING.md or by looking at the id field of seldon_servers.py objects. - tests(integration): Remove limits from SeldonDeployments applied. - Update CONTRIBUTING.md with instructions on how to run tests separately. - ci: Run test_seldon_servers integration test for each SeldonDeployment CR in a distinct GH runner. - ci: Extract automatically tox integration environments using a script. Fixes #229
kimwnasptd
pushed a commit
that referenced
this issue
Jan 23, 2024
…#228) (#234) - tests(integration): Configure test_seldon_servers test in order to be able to run tests only on one of the SeldonDeployments CRs. This can be done using pytest's-k flag and the corresponding keyword. You can find keywords in CONTRIBUTING.md or by looking at the id field of seldon_servers.py objects. - tests(integration): Remove limits from SeldonDeployments applied. - Update CONTRIBUTING.md with instructions on how to run tests separately. - ci: Run test_seldon_servers integration test for each SeldonDeployment CR in a distinct GH runner. - ci: Extract automatically tox integration environments using a script. Fixes #229
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why it needs to get done
We 've seen those tests on servers (SeldonDeployment CRs) being flaky during the past (e.g. #203), for reasons that we believe are due to resources. Being able to split those and run each server in its own environment will hopefully fix this.
What needs to get done
Configure
test_seldon_servers
in order to be able to run tests only on one serverWhen is the task considered done
tox
only on one server.The text was updated successfully, but these errors were encountered: