-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Use testing mode to raise errors during automatic signature inference #8866
Conversation
Signed-off-by: Jerry Liang <jerry.liang@databricks.com>
Documentation preview for b21e104 will be available here when this CircleCI job completes successfully. More info
|
@jerrylian-db Can we use |
Signed-off-by: Jerry Liang <jerry.liang@databricks.com>
@harupy great idea! Done :) |
@pytest.fixture(autouse=True) | ||
def set_envs(monkeypatch): | ||
monkeypatch.setenvs( | ||
{ | ||
"MLFLOW_TESTING": "true", | ||
} | ||
) |
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.
We can remove this because the top-level conftest.py
already has it:
Lines 144 to 148 in 152063e
@pytest.fixture(scope="session", autouse=True) | |
def enable_mlflow_testing(): | |
with pytest.MonkeyPatch.context() as mp: | |
mp.setenv(_MLFLOW_TESTING.name, "TRUE") | |
yield |
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.
Huh, so we can remove this from all individual test suites? If I remove it from the test suites, will running those test suites on their own have this environment variable set?
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.
Yes :) You can test it to confirm.
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 once #8866 (comment) is addressed!
Signed-off-by: Jerry Liang <jerry.liang@databricks.com>
Co-authored-by: Harutaka Kawamura <hkawamura0130@gmail.com> Signed-off-by: Jerry Liang <66143562+jerrylian-db@users.noreply.github.com>
…mlflow#8866) * implement it Signed-off-by: Jerry Liang <jerry.liang@databricks.com> * change environment variable Signed-off-by: Jerry Liang <jerry.liang@databricks.com> * fix test Signed-off-by: Jerry Liang <jerry.liang@databricks.com> * adapt feedback Signed-off-by: Jerry Liang <jerry.liang@databricks.com> --------- Signed-off-by: Jerry Liang <jerry.liang@databricks.com>
…mlflow#8866) * implement it Signed-off-by: Jerry Liang <jerry.liang@databricks.com> * change environment variable Signed-off-by: Jerry Liang <jerry.liang@databricks.com> * fix test Signed-off-by: Jerry Liang <jerry.liang@databricks.com> * adapt feedback Signed-off-by: Jerry Liang <jerry.liang@databricks.com> --------- Signed-off-by: Jerry Liang <jerry.liang@databricks.com>
Related Issues/PRs
#xxxWhat changes are proposed in this pull request?
The automatic signature inference feature swallows failures. However, this makes it difficult to for contributors to debug during testing. This PR uses the
MLFLOW_TESTING
environment variable to disable failure swallowing of this feature in MLflow tests.How is this patch tested?
I manually added an exception to the signature inference code and verified that the exception was raised in an MLflow test. I manually removed the monkeypatch in that test suite, and the exception was no longer raised (instead the test failed because there was no inferred signature, as expected).
Does this PR change the documentation?
Release Notes
Is this a user-facing change?
(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/artifacts
: Artifact stores and artifact loggingarea/build
: Build and test infrastructure for MLflowarea/docs
: MLflow documentation pagesarea/examples
: Example codearea/model-registry
: Model Registry service, APIs, and the fluent client calls for Model Registryarea/models
: MLmodel format, model serialization/deserialization, flavorsarea/recipes
: Recipes, Recipe APIs, Recipe configs, Recipe Templatesarea/projects
: MLproject format, project running backendsarea/scoring
: MLflow Model server, model deployment tools, Spark UDFsarea/server-infra
: MLflow Tracking server backendarea/tracking
: Tracking Service, tracking client APIs, autologgingInterface
area/uiux
: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/docker
: Docker use across MLflow's components, such as MLflow Projects and MLflow Modelsarea/sqlalchemy
: Use of SQLAlchemy in the Tracking Service or Model Registryarea/windows
: Windows supportLanguage
language/r
: R APIs and clientslanguage/java
: Java APIs and clientslanguage/new
: Proposals for new client languagesIntegrations
integrations/azure
: Azure and Azure ML integrationsintegrations/sagemaker
: SageMaker integrationsintegrations/databricks
: Databricks integrationsHow should the PR be classified in the release notes? Choose one:
rn/breaking-change
- The PR will be mentioned in the "Breaking Changes" sectionrn/none
- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/feature
- A new user-facing feature worth mentioning in the release notesrn/bug-fix
- A user-facing bug fix worth mentioning in the release notesrn/documentation
- A user-facing documentation change worth mentioning in the release notes