> We're currently setting the admin task timeout to 20 minutes.
> This isn't enough on some cases.

To be clear:  This isn't enough in almost any case other than "the
DUT didn't really need repair in the first case".

In practical cases that I've seen, the work to successfully re-install
from USB runs at least 40 minutes end-to-end; longer times are possible,
and shouldn't be considered out of the ordinary.

So, I'd recommend at least 90 minutes for a repair timeout.  To be safe,
2 hours would be better.

https://chromium-review.googlesource.com/c/infra/infra/+/1135826

I'm starting with 90 minutes.
If we notice timeouts, we can bump it further / split timeouts based on the task being created.

The following revision refers to this bug:
  https://chromium.googlesource.com/infra/infra/+/0f97fffdaafffc2fe43f770d199f0561a8cfab64

commit 0f97fffdaafffc2fe43f770d199f0561a8cfab64
Author: Prathmesh Prabhu <pprabhu@chromium.org>
Date: Thu Jul 12 23:51:12 2018

crosskylabadmin: Bump up execution timeout for admin tasks

BUG= chromium:863180 

Change-Id: I29d2974a2f743c5a593dc7daace78d3b15bc629f
Reviewed-on: https://chromium-review.googlesource.com/1135826
Commit-Queue: Prathmesh Prabhu <pprabhu@chromium.org>
Reviewed-by: Ryan Tseng <hinoka@chromium.org>

[modify] https://crrev.com/0f97fffdaafffc2fe43f770d199f0561a8cfab64/go/src/infra/appengine/crosskylabadmin/app/frontend/frontend.go
[modify] https://crrev.com/0f97fffdaafffc2fe43f770d199f0561a8cfab64/go/src/infra/appengine/crosskylabadmin/app/clients/swarming.go