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

runtime: apparent deadlock in TestConcurrentReadsAfterGrowth on FreeBSD #48764

Open
bcmills opened this issue Oct 4, 2021 · 3 comments
Open
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-FreeBSD
Milestone

Comments

@bcmills
Copy link
Contributor

bcmills commented Oct 4, 2021

greplogs --dashboard -md -l -e '(?m)^goroutine.*\[.* minutes\]:\n(?:.+\n\t.*\n)*^sync\..*\.Wait.*\n\t.*\nruntime_test\.testConcurrentReadsAfterGrowth'

2021-10-02T16:05:55-a7fe161/freebsd-amd64-race

@bcmills bcmills added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Oct 4, 2021
@bcmills bcmills added this to the Backlog milestone Oct 4, 2021
@bcmills
Copy link
Contributor Author

bcmills commented Oct 4, 2021

May be related to #46272.

@bcmills bcmills changed the title runtime: apparent deadlock in TestConcurrentReadsAfterGrowth runtime: apparent deadlock in TestConcurrentReadsAfterGrowth on FreeBSD Oct 4, 2021
@prattmic
Copy link
Member

I got this failure on a TryBot on https://golang.org/cl/362977, which I'm fairly confident didn't break this builder since the change is arm-only.

https://storage.googleapis.com/go-build-log/3b040cf9/freebsd-amd64-12_2_0092f6cd.log

@prattmic
Copy link
Member

prattmic commented Nov 12, 2021

This is an interesting failure, because TestConcurrentReadsAfterGrowth is blocked on sync.WaitGroup.Wait waiting for goroutines to complete, but those goroutines don't appear to exist (anymore or ever?) based on the traceback.

This could perhaps be an issue with the last wg.Done() not properly waking the waiter?

cc @mknyszek

@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jul 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-FreeBSD
Projects
Status: Triage Backlog
Development

No branches or pull requests

3 participants