go: runtime: frequent crashes with "exit status 16962" on netbsd-arm64-bsiegert builder
#!watchflakes
post <- goos == "netbsd" && goarch == "arm64" && `exit status 16962`
The netbsd/arm64 builder regularly fails with a process (usually compile) exiting with exit status 16962 - some examples:
https://build.golang.org/log/21955ac5c870203c1e6ff0c9c4f3437c10778dbf https://build.golang.org/log/f58d31621ecf6eb5317790d7683479bb44b9561d https://build.golang.org/log/96764e29f501a683cccf7006af49b865d0e2f133
16962 is 0x4242 hexadecimal, which seems to suggest that sigreturn_tramp is failing to call setcontext:
https://github.com/golang/go/blob/master/src/runtime/sys_netbsd_arm64.s#L275
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 40 (35 by maintainers)
Commits related to this issue
- runtime: crash on netbsd-arm64 when setcontext fails Instead of exiting with status 16962 when we fail to call SYS_setcontext in sigreturn, reference a null pointer and crash. Hopefully, this will en... — committed to golang/go by bsiegert 2 years ago
- runtime: crash on netbsd-arm64 when setcontext fails Instead of exiting with status 16962 when we fail to call SYS_setcontext in sigreturn, reference a null pointer and crash. Hopefully, this will en... — committed to jproberts/go by bsiegert 2 years ago
- dashboard: update netbsd, openbsd builders to Go 1.19.2 The NetBSD builders are failing in a way that only manifests with Go 1.17. The OpenBSD builders are also very flaky. Update both operating syst... — committed to golang/build by rsc 2 years ago
If the problem is Go 1.17.13, then we can have the coordinator install something newer.
The failures are typically early in the bootstrap phase, which means they are in binaries built with Go 1.14.2. I did the following two things:
GOROOT_BOOTSTRAP, which includes the latest change on this issue.