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

cmd/compile: apparent deadlocks on builders #45885

Open
bcmills opened this issue Apr 30, 2021 · 0 comments
Open

cmd/compile: apparent deadlocks on builders #45885

bcmills opened this issue Apr 30, 2021 · 0 comments

Comments

@bcmills
Copy link
Member

@bcmills bcmills commented Apr 30, 2021

I started looking into build failures with stuck subprocesses due to an unexpected TryBot flake in https://storage.googleapis.com/go-build-log/385d1fe8/freebsd-amd64-12_2_0bbe1706.log.

I check the builder logs for similar failures, and found a lot of processes stuck on go build but for the most part little clue about what go build itself was stuck on.

However, one of the logs seems to point to a very long hang in an invocation of cmd/compile:

2021-04-29T16:29:52-f7c6f62/linux-amd64-buster (stuck 7 minutes on compile, if I'm reading this code properly)

A couple of others (including the aforementioned TryBot run) were stuck in go build or go install, but didn't terminate the go command with quite the right signal to figure out where it was stuck.
2021-04-29T23:41:22-a9705e1/freebsd-amd64-12_2
2021-04-23T21:48:41-a6d3dc4/freebsd-386-12_2

We do occasionally see hangs in other cmd/go invocations, but they are generally very specific (go list on MIPS - #45884, and occasionally something on darwin ‐ #38768) and in particular don't account for the linux-amd64-buster failure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant