From 3a64e701fce052793253c7c8cc5010d5db13bc60 Mon Sep 17 00:00:00 2001 From: Jan Was Date: Tue, 1 Mar 2022 16:41:02 +0100 Subject: [PATCH] Increase timeout in container test When the container healthcheck was added, it also replaced looping over trino-cli in the container test script with docker inspect. Since executing trino-cli could time out after the container started but before the server was ready, it actually added to the total timeout of the loop. Now, none of the commands in the loop are blocking for longer periods, so the timeout is easier to control. It was measured that the container can take up to 7 minutes to start on arm64 using emulation, so the timeout is raised to 10 minutes. --- core/docker/container-test.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core/docker/container-test.sh b/core/docker/container-test.sh index 08985dc3929c..ec56c4ceac74 100644 --- a/core/docker/container-test.sh +++ b/core/docker/container-test.sh @@ -8,7 +8,7 @@ function cleanup { function test_trino_starts { local QUERY_PERIOD=10 - local QUERY_RETRIES=30 + local QUERY_RETRIES=60 CONTAINER_ID= trap cleanup EXIT