From 02c952532eb868c7c69fc02ba107b785ea8540c5 Mon Sep 17 00:00:00 2001 From: Dmitry Meyer Date: Fri, 24 Jul 2026 09:30:03 +0000 Subject: [PATCH] Use test log storage in `test_updates_running_job` No logs written by the test, but an instance of a `LogStorage` implementation is created via `write_logs()` -> `get_log_storage()`, leading to possible side effects, e.g. `CloudWatchLogStorage.__init__()` checks if the log group exists and fails with an error (suppressed, but a warning is still emitted): > UserWarning: A test tried to use socket.socket.connect() with host > "3.250.243.83" (allowed: "127.0.0.1,localhost (127.0.0.1)"). > raise SocketConnectBlockedError(allowed_list, host) --- .../server/background/pipeline_tasks/test_running_jobs.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/tests/_internal/server/background/pipeline_tasks/test_running_jobs.py b/src/tests/_internal/server/background/pipeline_tasks/test_running_jobs.py index 95a93d6e3..737a6d4dc 100644 --- a/src/tests/_internal/server/background/pipeline_tasks/test_running_jobs.py +++ b/src/tests/_internal/server/background/pipeline_tasks/test_running_jobs.py @@ -91,7 +91,7 @@ ) from dstack._internal.utils.common import get_current_datetime -pytestmark = pytest.mark.usefixtures("image_config_mock") +pytestmark = pytest.mark.usefixtures("image_config_mock", "test_log_storage") @dataclass