Skip to content

runtime: TestGoroutineProfile often times out on freebsd #11501

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

Closed
aclements opened this issue Jul 1, 2015 · 3 comments
Closed

runtime: TestGoroutineProfile often times out on freebsd #11501

aclements opened this issue Jul 1, 2015 · 3 comments
Milestone

Comments

@aclements
Copy link
Member

TestGoroutineProfile in the runtime tests has been timing out on freebsd-amd64 and freebsd-386 fairly regularly since June 19th.

For example, http://build.golang.org/log/d17f225a550e374216b3b3659083528163b22af9 (2015-07-01T10:37:10-1cbbd7f/freebsd-amd64-gce101) is the most recent and http://build.golang.org/log/60872d743598fe54d315bfcbded6321fb9c18ccc (2015-06-19T05:15:22-a3c0730/freebsd-amd64-gce101) is the first.

It looks like runtime.GoroutineProfile is stuck trying to acquire worldsema, but it's unclear who's holding it (presumably some runtime G that isn't being printed).

Looking through the commit history leading up to the first failure, 90a1996 (runtime: reduce latency by aggressively ending mark phase, @RLH), e72f5f6 (runtime: fix tracing of syscallexit, @dvyukov), cfa3eda (runtime: fix race in scanvalid assertion, @rsc), and 3c60e6e (runtime: fix races in stack scan, @rsc) are the only ones that jump out at me as potentially related, but it may be none of those.

@aclements aclements added this to the Go1.5 milestone Jul 1, 2015
@dvyukov
Copy link
Member

dvyukov commented Jul 3, 2015

I can imagine that that test can be super slow on some hardware/OS.

@rsc
Copy link
Contributor

rsc commented Jul 30, 2015

I'm feeling lucky.

@rsc rsc closed this as completed Jul 30, 2015
@golang golang locked and limited conversation to collaborators Aug 5, 2016
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