x/build/cmd/gomote: 502 Bad Gateway error

[hyangah]

I often encounter this 502 Bad Gateway error while actively working with a buildlet created using gomote. I guess this is because I was holding the buildlet too long (~30min) and there is a hidden time limit on each buildlet. If so, we need a better error message than this:

$ gomote ls user-hakim-windows-amd64-2016-0
Error running ls: 502 Bad Gateway: 

And, gomote list still shows the lease is not yet expired. That's misleading.

$ gomote list
user-hakim-windows-amd64-2016-0	windows-amd64-2016	host-windows-amd64-2016	expires in 29m49.611152102s

[bcmills]

I'm seeing this frequently too. I don't think it's actually a time limit, but it's opaque enough that I'm not sure.

CC @golang/osp-team

[thanm]

I ran into the same problem this morning. Very mysterious error.

[gopherbot]

Change https://golang.org/cl/200738 mentions this issue: cmd/coordinator: make gomote proxy 502 error include detail

[bradfitz]

Deployed coordinator with new logging. Please report any errors you see. We can also search the coordinator's logs for it too.

[thanm]

New error just now:

Error running puttar: 502 Bad Gateway; body: (golang.org/issue/28365): gomote proxy error: Put http://10.240.0.16/writetgz?dir=: net/http: request canceled while waiting for connection now run: gomote run user-thanm-android-386-emu-0 /bin/bash build-on-gomote.sh Error running run: Error trying to execute /bin/bash: buildlet: HTTP status 502 Bad Gateway: (golang.org/issue/28365): gomote proxy error: Post http://10.240.0.16/exec?: net/http: request canceled while waiting for connection

[gopherbot]

Change https://golang.org/cl/203217 mentions this issue: buildlet, cmd/coordinator: stop using legacy Request.Cancel for cancellation