You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
os/signal: test timeout (entire VM hangs) on netbsd/386 (7.0.1 GENERIC) #16511
The problem on netbsd is even worse,
the builder VM freezes (sometimes
restarts automatically) after a few builds.
so far I haven't been able to capture a
copy of the kernel messages yet.
there isn't any log on the console.
changed the title [-]os/signal: test timeout on netbsd/386 (7.0.1 GENERIC)[/-][+]os/signal: test timeout (entire VM hangs) on netbsd/386 (7.0.1 GENERIC)[/+]on Nov 2, 2016
Activity
bradfitz commentedon Jul 27, 2016
Ian is on vacation.
bradfitz commentedon Jul 27, 2016
/cc @bsiegert @mdempsky
bsiegert commentedon Jul 27, 2016
Is that the same as #10027?
minux commentedon Jul 27, 2016
minux commentedon Jul 27, 2016
ianlancetaylor commentedon Jul 28, 2016
See if you can get the strace output (or dtruss, or whatever it is called on NetBSD) of
signal.test -test.short -test.run=TestStress.Sounds like something is going wrong if a signal is received while handling that signal. Or, it's a problem with the alternate signal stack.
rsc commentedon Oct 20, 2016
If the entire builder VM freezes then it's probably not Go's fault. Sounds like a kernel problem.
[-]os/signal: test timeout on netbsd/386 (7.0.1 GENERIC)[/-][+]os/signal: test timeout (entire VM hangs) on netbsd/386 (7.0.1 GENERIC)[/+]wenheping commentedon Feb 18, 2017
The same test error of Go-1.8 On NetBSD/amd64(7.0.1 GENERIC).
gopherbot commentedon Jun 28, 2017
CL https://golang.org/cl/47036 mentions this issue.
doc: document the state of NetBSD in the Go 1.9 release notes
gopherbot commentedon Nov 29, 2017
Change https://golang.org/cl/80515 mentions this issue:
runtime: fix sysctl calling convention on netbsd/386runtime: fix sysctl calling convention on netbsd/386
bradfitz commentedon Nov 29, 2017
This is fixed by requiring NetBSD 8-BETA+.