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
misc/cgo/testcarchive: TestSIGPROF flakes with "signal: profiling timer expired" #19320
Comments
Again just now, same message: https://storage.googleapis.com/go-build-log/bb8472a0/darwin-amd64-10_11_2bd97160.log |
CL https://golang.org/cl/42830 mentions this issue. |
I see this once every ~200 runs of What I think may be happening:
If this is so, then I don't see a way to uninstall the SIGPROF handler. https://golang.org/cl/42830 leaves the handler installed once it is installed. That's enough to fix the test, over several thousand runs. Is this good enough? Should we also forward SIGPROF in this case? |
Kicking to Go 1.10. @bcmills, feel free to take it over (soon) if you think this is important for Go 1.9. |
Change https://golang.org/cl/68850 mentions this issue: |
Change https://golang.org/cl/69111 mentions this issue: |
Change https://golang.org/cl/69114 mentions this issue: |
Updates #19320. Change-Id: Id38df033e3f0873986e668c8ff3855b6e08407a9 Reviewed-on: https://go-review.googlesource.com/69114 Run-TryBot: Elias Naur <elias.naur@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
Happened on a freebsd-amd64-12_0 trybot run: https://farmer.golang.org/temporarylogs?name=freebsd-amd64-12_0&rev=f424e02578b25cb81ab055a6bd39e86b1f37855a&st=0xc455410000
|
Another |
@ianlancetaylor @bcmills, David Crawshaw seems very busy and had submitted CL https://go-review.googlesource.com/c/go/+/42830 which has been open for more than 2 years. Could someone please take over that CL giving him credit, we can submit the newly created one and abandon his old CL. |
I don't have the bandwidth to take this on at the moment, but if someone wants to make a run at this I could probably at least find the time to review a fix. |
|
Change https://golang.org/cl/200740 mentions this issue: |
I see this test failure from a trybot, in https://storage.googleapis.com/go-build-log/f8d7aae9/darwin-amd64-10_11_578453d9.log.
The text was updated successfully, but these errors were encountered: