Use cached_db fixture in tests/tracking/test_log_image.py for faster execution#19212
Merged
Use cached_db fixture in tests/tracking/test_log_image.py for faster execution#19212
cached_db fixture in tests/tracking/test_log_image.py for faster execution#19212Conversation
…test execution Co-authored-by: harupy <17039389+harupy@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR introduces the cached_db fixture to tests/tracking/test_log_image.py to improve test execution performance by avoiding repeated database migrations. The implementation achieves a 76% reduction in test execution time (29.5s → 7.1s).
Key Changes
- Added imports for
shutil,uuid,Path, and_use_tracking_urito support database caching functionality - Introduced an autouse fixture
set_tracking_urithat copies a pre-initialized database and sets the tracking URI for each test - Applied the cached database pattern to avoid expensive database setup operations
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Copilot
AI
changed the title
[WIP] Use cached_db fixture for faster test execution
Use cached_db fixture in tests/tracking/test_log_image.py for 76% faster execution
Dec 4, 2025
harupy
reviewed
Dec 4, 2025
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Harutaka Kawamura <hkawamura0130@gmail.com>
cached_db fixture in tests/tracking/test_log_image.py for faster execution
harupy
approved these changes
Dec 4, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issues/PRs
#xxxWhat changes are proposed in this pull request?
Adopts the
cached_dbfixture pattern to eliminate repeated database schema migrations in test_log_image.py, reducing execution time from 29.5s to 7.1s (76% improvement).Changes:
set_tracking_uriautouse fixture that copies session-scopedcached_dbto test-local temporary paths_use_tracking_uricontext manager for automatic URI lifecycle managementuuid.uuid4().hexnamingHow is this PR tested?
All 47 existing tests pass with identical behavior.
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/tracking: Tracking Service, tracking client APIs, autologgingarea/models: MLmodel format, model serialization/deserialization, flavorsarea/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registryarea/scoring: MLflow Model server, model deployment tools, Spark UDFsarea/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflowsarea/gateway: MLflow AI Gateway client APIs, server, and third-party integrationsarea/prompts: MLflow prompt engineering features, prompt templates, and prompt managementarea/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionalityarea/projects: MLproject format, project running backendsarea/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesHow 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?
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.