x/build/cmd/gomote: odd failures using gomote groups #76090
Description
When I run gomote inside benchlab, occasionally I get:
gomote -group=benchlab create gotip-linux-386: exit status 1
with concatenated stderr+stdout:
# Failure: loading group "benchlab": EOF
Usage of gomote: gomote [global-flags] <cmd> [cmd-flags]
Global flags:
-group string
name of the gomote group to apply commands to (default is $GOMOTE_GROUP)
-localdev
use the localhost in-development coordinator
-server string
Address for GRPC server (default "gomote.golang.org:443")
-staging
use the staging build coordinator and buildlets
-user string
gomote server username (default "rsc")
Commands:
create create a buildlet; with no args, list types of buildlets
destroy destroy a buildlet
gettar extract a tar.gz from a buildlet
group manage groups of instances
list list active buildlets
login authenticate with the gomote service
ls list the contents of a directory on a buildlet
ping test whether a buildlet is alive and reachable
push sync your GOROOT directory to the buildlet
put put files on a buildlet
putbootstrap put bootstrap toolchain in place
puttar extract a tar.gz to a buildlet
rdp Unimplimented: RDP (Remote Desktop Protocol) to a Windows buildlet
repro reproduce a build environment in a new buildlet
rm delete files or directories
run run a command on a buildlet
ssh ssh to a buildlet
There are two weird things. One is printing usage after the "loading group" failure. The other is the loading group failure message being just EOF.
I have not reproduced this at the command line. Perhaps it has to do with running multiple instances in parallel. I am running:
gomote -group=benchlab create gotip-linux-386
gomote -group=benchlab create gotip-linux-amd64
...
at the same time in different processes. Perhaps there is another file access bug? I remember there was one in the past about VMs disappearing from the group.