From f2096ad9957b52e33a1705a501833abcb681190c Mon Sep 17 00:00:00 2001 From: Alexander Rakoczy Date: Tue, 25 May 2021 21:41:15 -0400 Subject: [PATCH] buildlet: increase timeout period for client The a1.metal instances take about four minutes to become available before beginning to boot the Windows ARM64 VM. This means we need somewhere between five and ten minutes before we can first connect to the buildlet. It's possible that other instances are faster to boot, but this is currently the most economical choice. For golang/go#42604 Change-Id: Ib76944307c9ad28fd1adca0dc54f3fbeaabfffa0 Reviewed-on: https://go-review.googlesource.com/c/build/+/322654 Trust: Alexander Rakoczy Run-TryBot: Alexander Rakoczy TryBot-Result: Go Bot Reviewed-by: Carlos Amedee --- buildlet/buildlet.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/buildlet/buildlet.go b/buildlet/buildlet.go index 9a58a90e9f..169630305d 100644 --- a/buildlet/buildlet.go +++ b/buildlet/buildlet.go @@ -82,9 +82,9 @@ type VMOpts struct { // it can connect with the endpoint before returning. The buildletURL is in the form of: // "https://". The ipPort field is in the form of ":". The function // will attempt to connect to the buildlet for the lesser of: the default timeout period -// (5 minutes) or the timeout set in the passed in context. +// (10 minutes) or the timeout set in the passed in context. func buildletClient(ctx context.Context, buildletURL, ipPort string, opts *VMOpts) (*Client, error) { - ctx, cancel := context.WithTimeout(ctx, 5*time.Minute) + ctx, cancel := context.WithTimeout(ctx, 10*time.Minute) defer cancel() try := 0 for !opts.SkipEndpointVerification {