-
Notifications
You must be signed in to change notification settings - Fork 11
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
Integration tests do not pass in local environment #193
Comments
I was able to reproduce the first part of the issue when running Lines 76 to 82 in f18c4e6
causing the error we see in the first part of the logs above:
the application is not found in this model, because it was deployed in a different model. |
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5283.
|
Thank you @NohaIhab for nailing down the root cause of this. We should thus make a sufficient improvement in our code (e.g. add a relevant comment in |
Bug Description
When running integration test command using environments degined in
tox.ini
(tox -e integration
) tests fail to pass.It should be noted that in recent PR these tests successfully passed in CI (GH runners). In particular
test_ingress_url
test.The following is a PASSED test in GH runner, but never finishes in local testing (see To Reproduce section for more details):
To Reproduce
Execute
tox -e integration
and observe errors and not passed tests. It looks like running this particular commandmlflow-server
application is deleted in one set of tests and another set of tests fails. See relevant log section for more details.When model for excuting integration tests is created and option to keep models is given (to prevent destruction of
mlflow-server
) Running the following commandtox -e integration -- --model test --keep-models
produces different error. This timetest_ingress_url
test never completes. See relevant log section for more details.Environment
Local development environment, in this repository, on
main
branch.Relevant log output
Additional context
Need to verify in some other development environment to exclude possible broken development environment on the reporter's development machine.
The text was updated successfully, but these errors were encountered: