People think gomote create hangs when really it's just waiting a long time to get a buildlet (for the statically-provisioned buildlets).
Now that the scheduler is about to land (#19178), it shouldn't be too hard to plumb through position-in-line & queue depth updates down to the gomote binary so it can print out regular status messages.
The text was updated successfully, but these errors were encountered:
Also modernizes some code in the coordinator.
Updates golang/go#35354 (or fixes. But we could return more info.)
Run-TryBot: Brad Fitzpatrick <email@example.com>
TryBot-Result: Gobot Gobot <firstname.lastname@example.org>
Reviewed-by: Bryan C. Mills <email@example.com>