-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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/pprof: TestStackBarrierProfiling hangs #15477
Comments
CC @aclements |
@alexbrainman, can you re-run with GOTRACEBACK=crash? |
Alex |
@alexbrainman, are you (or were you) able to reproduce this reliably? How many CPUs does the host have? I haven't been able to reproduce this on a linux/amd64 host with GOARCH=386, or on the linux-386 gomote. If you can still reproduce this easily, could you run |
Actually, |
CL https://golang.org/cl/23134 mentions this issue. |
This should help with debugging failures. For #15138 and #15477. Change-Id: I77db2b6375d8b4403d3edf5527899d076291e02c Reviewed-on: https://go-review.googlesource.com/23134 Run-TryBot: Austin Clements <austin@google.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Rick Hudson <rlh@golang.org>
Yes. It fails nearly every time.
If I use GODEBUG=gcstackbarrierall=1, the problem goes away. So running:
This is all on current tip:
I hope you have everything you need, Dr Austin. Alex |
Oh, is this a single core? If it is, this is probably the same as #15706. |
@alexbrainman, could you give https://golang.org/cl/23172 a try? |
It is.
It is. The issue #15706 is about the same TestStackBarrierProfiling hangs. I am closing my issue as duplicate.
CL 23172 fixes my problem. I can run all.bash without fear now. Thank you. Alex |
Great! Thanks for testing. |
Please answer these questions before submitting your issue. Thanks!
go version
)?go env
)?If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
I run:
I expect test pass.
The test fails on my windows-amd64 too.
Alex
The text was updated successfully, but these errors were encountered: