go: runtime: "fatal: systemstack called from unexpected goroutine" on Android
#!watchflakes
post <- builder ~ `android` && `systemstack called from unexpected goroutine`
greplogs --dashboard -md -l -e '^fatal: systemstack called from unexpected goroutine' --since=2021-01-01
2022-02-02T21:12:39-53d6a72/android-amd64-emu
##### GOMAXPROCS=2 runtime -cpu=1,2,4 -quick
fatal: systemstack called from unexpected goroutineTrap
exitcode=133
FAIL runtime 59.879s
2021-10-08T16:26:20-59d4e92-99c1b24/android-amd64-emu
fatal: systemstack called from unexpected goroutineSegmentation fault
exitcode=139FAIL golang.org/x/net/publicsuffix 3.419s
I’ll also note that badsystemstackMsg seems to be missing a final newline as of CL 93659 (CC @aclements @randall77). 😅
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 24 (18 by maintainers)
Commits related to this issue
- dashboard: add known issues for android-*-emu Issue golang/go#42212 manifests as test timeouts, and is by far the most frequent of these known issues. Issue golang/go#51001 causes failures with "sys... — committed to golang/build by bcmills 2 years ago
- dashboard: unmark known-issues with low failure rates I had initially added known issues fairly aggressively in order to use them to reduce noise in 'greplogs -triage'. Now that we are using 'watchfl... — committed to golang/build by bcmills a year ago
I’ve mailed CL 407615 that makes android-amd64-emu a post-submit builder only (in the main repo) while investigation of this issue is underway. If submitted, this issue can be unmarked as a release-blocker for Go 1.19.