fix sm-python-sdk unit test dependency issue

Ruinong Tian · Ruinong Tian · commit a43a9dc940a7 · 2025-04-29T19:35:04.000Z
diff --git a/test/test_artifacts/v2/sm-python-sdk.test.Dockerfile b/test/test_artifacts/v2/sm-python-sdk.test.Dockerfile
@@ -4,7 +4,7 @@ FROM $SAGEMAKER_DISTRIBUTION_IMAGE
 ARG MAMBA_DOCKERFILE_ACTIVATE=1
 RUN git clone --recursive https://github.com/aws/sagemaker-python-sdk.git
 
-RUN micromamba install -y --freeze-installed -c conda-forge pytest mock stopit awslogs
+RUN micromamba install -y --freeze-installed -c conda-forge pytest mock stopit awslogs deepdiff
 
 # Sagemaker Python SDK's unit tests requires AWS_DEFAULT_REGION to be set. So, using an arbitrary value of us-east-1
 ENV AWS_DEFAULT_REGION=us-east-1
diff --git a/test/test_artifacts/v3/sm-python-sdk.test.Dockerfile b/test/test_artifacts/v3/sm-python-sdk.test.Dockerfile
@@ -4,7 +4,7 @@ FROM $SAGEMAKER_DISTRIBUTION_IMAGE
 ARG MAMBA_DOCKERFILE_ACTIVATE=1
 RUN git clone --recursive https://github.com/aws/sagemaker-python-sdk.git
 
-RUN micromamba install -y --freeze-installed -c conda-forge pytest mock stopit awslogs
+RUN micromamba install -y --freeze-installed -c conda-forge pytest mock stopit awslogs deepdiff
 
 # Sagemaker Python SDK's unit tests requires AWS_DEFAULT_REGION to be set. So, using an arbitrary value of us-east-1
 ENV AWS_DEFAULT_REGION=us-east-1
