-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/build: maintner.golang.org not-accessible #21383
Comments
I always suspected maintner was really just Brad on his phone. |
I don't have access to the production infrastructure, unfortunately. My guess is it's crashing on some bad input. |
I think @jessfraz and @adams-sarah have access to production as well |
maintner in a crash loop. panic: runtime error: invalid memory address or nil pointer dereference goroutine 521 [running]: |
Running to a meeting, but looks like a nil check ( |
Change https://golang.org/cl/54751 mentions this issue: |
From Sarah: https://golang.org/cl/54751
Which makes me wonder if there is some sort of race or ordering problem. One thing we could do is run this with the race detector on, either in production or in some sort of staging realm that mirrors the same data. |
with the maintainer back up, Reverse pool summary: Reverse pool machine detail My logs don't indicate anything out of the ordinary:
|
@paulzhol, can you open a separate issue for that one? |
Hey @kevinburke, all. Turns out my CL is the right fix. So the issue will only crop up periodically, which is what we are seeing for maintner outages. |
Waiting to deploy. Will ping back here when this fix is live. |
fyi this is live as of friday. |
The freebsd-arm-paulzhol builder is stuck in a loop since yesterday trying to build the sys subrepo but failing because it can't download it:
Also the dashboard for the sys build reports HTTP 404, attached logs captured from farmer.golang.org:
temporarylogs.txt
temporarylogs2.txt
The text was updated successfully, but these errors were encountered: