Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How does one repro gobot test failures? #43599

Closed
jeanbza opened this issue Jan 8, 2021 · 2 comments
Closed

How does one repro gobot test failures? #43599

jeanbza opened this issue Jan 8, 2021 · 2 comments

Comments

@jeanbza
Copy link
Member

jeanbza commented Jan 8, 2021

re: https://go-review.googlesource.com/c/exp/+/263178

Here, gobot is failing on:

Failed on windows-amd64-2016: https://storage.googleapis.com/go-build-log/4fd94558/windows-amd64-2016_7476d61d.log
Failed on linux-amd64: https://storage.googleapis.com/go-build-log/4fd94558/linux-amd64_ab816ec1.log
Failed on linux-amd64-race: https://storage.googleapis.com/go-build-log/4fd94558/linux-amd64-race_589bd1d8.log
Failed on windows-386-2008: https://storage.googleapis.com/go-build-log/4fd94558/windows-386-2008_4cb3fdbb.log

I'm unable to repro these locally (linux-rodete), nor on my windows desktop, nor on https://hub.docker.com/r/amd64/docker/.

How does one go about trying to test these types of failures? Is there some set of docker images that are reliable, or common practices, a doc that I could read, etc?

@ALTree
Copy link
Member

ALTree commented Jan 8, 2021

The trybots run on the builders. The builders infrastructure is not generally directly accessible, but there's a tool called gomote that can be used to access specific builders, which can be useful to debug issues that you cannot reproduce elsewhere (you have to ask for access first, see the Access token section).

Another option is to look for the exact builder configuration of the trybots that are failing, here: https://github.com/golang/build/tree/master/env and try to replicate it locally.

@cagedmantis
Copy link
Contributor

Closing this as @ALTree has provided an answer.

@golang golang locked and limited conversation to collaborators Jan 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants