Skip to content

Commit 60575cc

Browse files
increase failure timeout from 10 minutes to 20 minutes (#37413)
1 parent 02f811d commit 60575cc

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

run-ab-platform.sh

+4-4
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ EOL
106106
}
107107

108108
# TelemetryDockerUp checks if the webapp container is in a running state. If it is it will send a successful event.
109-
# if after 10 minutes it hasn't succeeded, a failed event will be sent (or if the user terminates early, a failed event would
109+
# if after 20 minutes it hasn't succeeded, a failed event will be sent (or if the user terminates early, a failed event would
110110
# also be sent).
111111
#
112112
# Note this only checks if the webapp container is running, that doesn't actually mean the entire stack is up.
@@ -117,8 +117,8 @@ TelemetryDockerUp()
117117
return
118118
fi
119119

120-
# for up to 600 seconds (10 minutes), check to see if the server services is in a running state
121-
end=$((SECONDS+600))
120+
# for up to 1200 seconds (20 minutes), check to see if the server services is in a running state
121+
end=$((SECONDS+1200))
122122
while [ $SECONDS -lt $end ]; do
123123
webappState=$(docker compose ps --all --format "{{.Service}}:{{.State}}" 2>/dev/null | grep server | cut -d ":" -f2 | xargs)
124124
if [ "$webappState" = "running" ]; then
@@ -128,7 +128,7 @@ TelemetryDockerUp()
128128
sleep 1
129129
done
130130

131-
TelemetrySend "failed" "install" "webapp was not running within 600 seconds"
131+
TelemetrySend "failed" "install" "webapp was not running within 1200 seconds"
132132
}
133133

134134
readonly telemetryKey="kpYsVGLgxEqD5OuSZAQ9zWmdgBlyiaej"

0 commit comments

Comments
 (0)