-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Fix flaky test_download_artifacts
in tests/store/artifact/test_http_artifact_repo.py
#6702
Conversation
Signed-off-by: harupy <hkawamura0130@gmail.com>
# Response for `_download_file("a.txt")` | ||
MockStreamResponse("data_a", 200), | ||
# Response for `list_experiments("dir")` | ||
MockResponse({"files": [{"path": "b.txt", "is_dir": False, "file_size": 1}]}, 200), |
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.
The traceback below indicates that a list-artifacts request (to list artifacts in the dir
directory) was responded with MockStreamResponse("data_a", 200)
.
def list_artifacts(self, path=None):
endpoint = "/mlflow-artifacts/artifacts"
url, tail = self.artifact_uri.split(endpoint, maxsplit=1)
root = tail.lstrip("/")
params = {"path": posixpath.join(root, path) if path else root}
host_creds = _get_default_host_creds(url)
resp = http_request(host_creds, endpoint, "GET", params=params)
augmented_raise_for_status(resp)
file_infos = []
> for f in resp.json().get("files", []):
E AttributeError: 'str' object has no attribute 'get'
endpoint = '/mlflow-artifacts/artifacts'
file_infos = []
host_creds = <mlflow.utils.rest_utils.MlflowHostCreds object at 0x0000022673C56B88>
params = {'path': 'dir'}
path = 'dir'
resp = <tests.store.artifact.test_mlflow_artifact_repo.MockStreamResponse object at 0x0000022671828D88>
root = ''
self = <mlflow.store.artifact.mlflow_artifacts_repo.MlflowArtifactsRepository object at 0x00000226718288C8>
tail = ''
url = 'http://localhost:5000/api/2.0'
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.
This error can be reproduced by modifying async_download_artifact
like this:
diff --git a/mlflow/store/artifact/artifact_repo.py b/mlflow/store/artifact/artifact_repo.py
index 63a0195c3..a0c52e242 100644
--- a/mlflow/store/artifact/artifact_repo.py
+++ b/mlflow/store/artifact/artifact_repo.py
@@ -152,8 +152,14 @@ class ArtifactRepository:
local_destination_file_path = self._create_download_destination(
src_artifact_path=src_artifact_path, dst_local_dir_path=dst_local_dir_path
)
+ import time
+
+ def delayed_download_file(remote_file_path, local_path):
+ time.sleep(1)
+ return self._download_file(remote_file_path, local_path)
+
download_future = self.thread_pool.submit(
- self._download_file,
+ delayed_download_file,
remote_file_path=src_artifact_path,
local_path=local_destination_file_path,
)
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.
This test assumes the following request order:
1. list_artifacts
2. list_artifacts
3. download_artifact <-
4. list_artifacts. <-
5. download_artifact
but request 3 and 4 could be swapped because a download-artifact operation is performed asynchronously.
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.
In the fixed test, the request order doesn't matter.
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.
I've observed this error a few times before on Windows, but not sure why it only occurs on Windows.
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
Signed-off-by: harupy <hkawamura0130@gmail.com> Signed-off-by: harupy <hkawamura0130@gmail.com> Signed-off-by: Prithvi Kannan <prithvi.kannan@databricks.com>
Signed-off-by: harupy <hkawamura0130@gmail.com> Signed-off-by: harupy <hkawamura0130@gmail.com> Signed-off-by: Prithvi Kannan <prithvi.kannan@databricks.com>
Signed-off-by: harupy <hkawamura0130@gmail.com> Signed-off-by: harupy <hkawamura0130@gmail.com>
Signed-off-by: harupy hkawamura0130@gmail.com
Related Issues/PRs
#xxx
What changes are proposed in this pull request?
Fix flaky
test_download_artifacts
intests/store/artifact/test_http_artifact_repo.py
.https://github.com/mlflow/mlflow/runs/8187814349?check_suite_focus=true
How is this patch tested?
Updated test
Does this PR change the documentation?
Details
link on thePreview docs
check.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/pipelines
: Pipelines, Pipeline APIs, Pipeline configs, Pipeline 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