go: runtime: frequent TestSegv failures since 2021-10-26
@prattmic, possibly related to CL 339989 / #47522?
greplogs --dashboard -md -l -e 'FAIL: TestSegv' --since=2021-10-01
2021-10-27T13:12:49-cfb5321/illumos-amd64 2021-10-27T08:50:27-bdefb77/illumos-amd64 2021-10-27T08:50:27-bdefb77/solaris-amd64-oraclerel 2021-10-27T05:33:58-ca5f65d/illumos-amd64 2021-10-26T23:12:17-13eccaa/illumos-amd64 2021-10-26T23:12:17-13eccaa/solaris-amd64-oraclerel 2021-10-26T23:06:10-e5c5125/illumos-amd64 2021-10-26T23:06:10-e5c5125/solaris-amd64-oraclerel 2021-10-26T22:05:53-80be4a4/illumos-amd64 2021-10-26T22:05:53-80be4a4/solaris-amd64-oraclerel 2021-10-26T21:32:57-86f6bf1/darwin-amd64-race 2021-10-26T21:32:57-86f6bf1/illumos-amd64
About this issue
- Original URL
- State: open
- Created 3 years ago
- Comments: 40 (33 by maintainers)
Commits related to this issue
- runtime: disable TestSegv panic check on darwin, illumos, solaris CL 339990 made this test more strict, exposing pre-existing issues on these OSes. Skip for now until they can be resolved. Updates #... — committed to golang/go by prattmic 3 years ago
- runtime: skip TestSegv traceback check on 386 The VDSO (__kernel_vsyscall) is reachable via asmcgocall(cgo_start_thread) on linux-386, which causes traceback to throw. Fixes #49182. For #50504. Cha... — committed to jproberts/go by prattmic 2 years ago
- runtime: refactor ARM VDSO call setup to helper We have a very complex process to make VDSO calls on ARM. Create a wrapper helper function which reduces duplication and allows for additional calls fr... — committed to golang/go by prattmic 3 years ago
- runtime: add test skips for ios For #59912. For #59913. Updates #49182. Change-Id: I3fcdfaca3a4f7120404e7a36b4fb5f0e57dd8114 Reviewed-on: https://go-review.googlesource.com/c/go/+/491095 TryBot-Bypa... — committed to golang/go by bcmills a year ago
There are various TestSegv issues that watchflakes are tracking, e.g. #59443. I think we can close this as a dup. If this happens again watchflakes will post on or reopen an existing issue, or open a new one.
I tend to agree that as a general feature getting correct tracebacks when an external SIGSEGV lands in an esoteric location is not important to users. I’ve been pushing on these bugs primarily to support testing. To ensure that the common cases work and don’t regress, I want to be able to write a straightforward test that tracebacks work. It is very difficult to write such a test if there are lots of edge cases that don’t work properly.
For now, I’ll skip this part of the test on 386, and I’ve filed #50504 as a low priority issue for this
asmcgocallproblem.I think since https://go-review.googlesource.com/c/go/+/339990
CL https://go-review.googlesource.com/c/go/+/339989 causes windows-arm64-10 builder fails.