[BUG] Cannot log custom transformer model on Azure Databricks when using mlflow.transformers.log_model() #11813
Open
6 of 23 tasks
Labels
area/artifacts
Artifact stores and artifact logging
area/model-registry
Model registry, model registry APIs, and the fluent client calls for model registry
area/models
MLmodel format, model serialization/deserialization, flavors
area/tracking
Tracking service, tracking client APIs, autologging
bug
Something isn't working
integrations/databricks
Databricks integrations
Issues Policy acknowledgement
Where did you encounter this bug?
Other
Willingness to contribute
No. I cannot contribute a bug fix at this time.
MLflow version
System information
Describe the problem
I'm trying to fine-tune an open-source, customized BERT-based model on some toy data they provided in their GitHub. The goal is to log the training metrics and specs, and eventually log the fine-tuned model.
Somehow, when I run
, the line
AutoModel.from_pretrained(training_args.output_dir)
gives me an error "OSError: No such device (os error 19)".Yet when I run
this error disappears.
And when I run
AutoModel.from_pretrained(training_args.output_dir)
standalone without wrapping withwith mlflow.start_run():
, the error still does not show up.I want to make the first code block work, since currently the error has forced me to manually log the model in a separate run after training.
The code imports modules/py files that are provided here: the useful ones are
arguments.py
,data.py
,modeling.py
, andtrainer.py
. I put them all inside a folder calledfinetune
at the same directory level as the databricks notebook I'm running.Tracking information
Code to reproduce issue
Stack trace
Other info / logs
What component(s) does this bug affect?
area/artifacts
: Artifact stores and artifact loggingarea/build
: Build and test infrastructure for MLflowarea/deployments
: MLflow Deployments client APIs, server, and third-party Deployments integrationsarea/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, autologgingWhat interface(s) does this bug affect?
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 supportWhat language(s) does this bug affect?
language/r
: R APIs and clientslanguage/java
: Java APIs and clientslanguage/new
: Proposals for new client languagesWhat integration(s) does this bug affect?
integrations/azure
: Azure and Azure ML integrationsintegrations/sagemaker
: SageMaker integrationsintegrations/databricks
: Databricks integrationsThe text was updated successfully, but these errors were encountered: