Closed harupy closed 6 months ago
/crt sklearn
/crt sklearn
/crt sklearn
test
/crt sklearn
Running cross-version tests for sklearn
/crt sklearn
/crt sklearn
Running cross-version tests for k
/crt sklearn
Running cross-version tests for k
/crt sklearn
Running cross-version tests for k
/crt sklearn
Running cross-version tests for k
/crt sklearn
Cross-version test run started: https://github.com/harupy/mlflow/actions/runs/8719470642
/crt sklearn
Cross-version test run started: https://github.com/harupy/mlflow/actions/runs/8733966623
/cross-version-test sklearn,xgboost
Cross-version test run started: https://github.com/harupy/mlflow/actions/runs/8733982579
/cross-version-test sklearn,xgboost
Cross-version test run started: https://github.com/harupy/mlflow/actions/runs/8751324507
🛠 DevTools 🛠
[![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/harupy/mlflow/pull/88?quickstart=1) #### Install mlflow from this PR ``` pip install git+https://github.com/mlflow/mlflow.git@refs/pull/88/merge ``` #### Checkout with GitHub CLI ``` gh pr checkout 88 ```
Related Issues/PRs
#xxx ### What changes are proposed in this pull request?How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing 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/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, 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/none
- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change
- The PR will be mentioned in the "Breaking Changes" 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 notesShould this PR be included in the next patch release?