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: TestSignalExitStatus fails on NetBSD, flaky on Solaris, FreeBSD #14063
Milestone
Comments
CL https://golang.org/cl/18817 mentions this issue. |
gopherbot
pushed a commit
that referenced
this issue
Jan 22, 2016
It doesn't work and I don't know why. Update #14063. Change-Id: I42735012cf6247eca5336f29fcf713e08c8477f8 Reviewed-on: https://go-review.googlesource.com/18817 Run-TryBot: Ian Lance Taylor <iant@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Also seen a few times on Solaris recently. e.g. http://build.golang.org/log/38a44f48270e2fa571f78ce123a6bc9c1c1cd120 /cc @4ad |
bradfitz
changed the title
runtime: TestSignalExitStatus fails on NetBSD
runtime: TestSignalExitStatus fails on NetBSD, flay on Solaris
Feb 2, 2016
CL https://golang.org/cl/19208 mentions this issue. |
gopherbot
pushed a commit
that referenced
this issue
Feb 4, 2016
Update #14063. Change-Id: Id13456deb15c90a8af282b77d78ff5cdbd1de8bf Reviewed-on: https://go-review.googlesource.com/19208 Run-TryBot: Ian Lance Taylor <iant@golang.org> Reviewed-by: Minux Ma <minux@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
bradfitz
changed the title
runtime: TestSignalExitStatus fails on NetBSD, flay on Solaris
runtime: TestSignalExitStatus fails on NetBSD, flaky on Solaris
Feb 4, 2016
bradfitz
changed the title
runtime: TestSignalExitStatus fails on NetBSD, flaky on Solaris
runtime: TestSignalExitStatus fails on NetBSD, flaky on Solaris, FreeBSD
May 12, 2016
Also seen being flaky on freebsd-arm: |
CL https://golang.org/cl/23203 mentions this issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The runtime package test TestSignalExitStatus fails on NetBSD. The program kills itself with SIGTERM, but the process still somehow manages to exit with a zero status. I have not been able to recreate the problem using a C program. I do not see anything interesting running ktruss. I have no idea why this fails. I'm to change the test to skip on NetBSD, and I'm filing this issue for reference.
The text was updated successfully, but these errors were encountered: