Skip to content

Fix GPU runbook: track MLflow runs in ./mlruns - #37

Merged
professor3333 merged 1 commit into
mainfrom
fix/mlflow-file-store
Nov 5, 2026
Merged

professor3333 merged 1 commit into
mainfrom
fix/mlflow-file-store

Conversation

@professor3333

Copy link
Copy Markdown
Owner

Summary

  • The second Kaggle run stopped when MLflow tracking started: UnsupportedModelRegistryStoreURIException ... unsupported URI 'sqlite:///…/mlflow.db'. MLflow 3 defaults to a SQLite store, and mlflow-skinny (the neural extra) cannot open one. MLflow 3.17 also refuses the file store unless MLFLOW_ALLOW_FILE_STORE=true.
  • Unless MLFLOW_TRACKING_URI is set, the trainer now uses the local file store ./mlruns and allows it for this process only. That is the directory the runbook packs and the docs describe.
  • Tests:
    • a new tracker test reproduces the exact failure before the fix;
    • the end-to-end CLI test (train → predict → experiment with a tiny model) now runs with MLflow on and checks mlruns/.
  • docs/training_on_gpu.md: the mlflow ui command sets the same opt-in.

Checks

  • ruff check, ruff format --check, mypy src/, pytest -m "not slow" pass.

MLflow 3 defaults to a SQLite store, which mlflow-skinny cannot open, so
the first GPU experiment stopped when tracking started. Unless
MLFLOW_TRACKING_URI is set, runs now go to ./mlruns (with the file store
explicitly allowed). The end-to-end CLI test now trains with MLflow on.
@professor3333
professor3333 merged commit cc5fcc7 into main Nov 5, 2026
2 of 3 checks passed
@professor3333
professor3333 deleted the fix/mlflow-file-store branch November 5, 2026 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant