/go

os/signal: test timeout (entire VM hangs) on netbsd/386 (7.0.1 GENERIC) #16511

Closed
minux opened this Issue Jul 27, 2016 · 11 comments

Comments

Assignees
No one assigned
Labels
Projects
None yet
Milestone
  Go1.10
8 participants
@minux
@bradfitz
@bsiegert
@ianlancetaylor
@rsc
@wenheping
@gopherbot
@quentinmit
@minux
Member

minux commented Jul 27, 2016 •
Edited 1 time

I upgraded the netbsd/386 builder to the latest 7.0.1 release,
and suddenly a lot of the builds fail at os/signal.

E.g.
timeout:
https://build.golang.org/log/f4c637234824467172beb3c7fdaf61fbd403d55c
illegal instruction:
https://build.golang.org/log/d1841610bb2fd982671f4db6bd8d1836a0a2d735
(this log also shows a failure in runtime/pprof, which might be interesting
as well.)
SIGTRAP:
https://build.golang.org/log/7275a54c64635553b418a15a58475698cf772f64

Repeated run of os/signal tests showed that it's failing in TestStress.

/cc @ianlancetaylor any ideas?

@minux minux added the OS-NetBSD label Jul 27, 2016

@minux minux added this to the Go1.8Early milestone Jul 27, 2016

@bradfitz
Owner

bradfitz commented Jul 27, 2016

Ian is on vacation.
@bradfitz
Owner

bradfitz commented Jul 27, 2016

/cc @bsiegert @mdempsky
@bsiegert
Contributor

bsiegert commented Jul 27, 2016

Is that the same as #10027?
@minux
Member

minux commented Jul 27, 2016

@minux
Member

minux commented Jul 27, 2016

@ianlancetaylor
Contributor

ianlancetaylor commented 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.

@quentinmit quentinmit added WaitingForInfo NeedsInvestigation labels Sep 26, 2016

@quentinmit quentinmit modified the milestones: Go1.8Maybe, Go1.8Early Sep 26, 2016

@rsc
Contributor

rsc commented Oct 20, 2016

If the entire builder VM freezes then it's probably not Go's fault. Sounds like a kernel problem.

@rsc rsc changed the title from os/signal: test timeout on netbsd/386 (7.0.1 GENERIC) to os/signal: test timeout (entire VM hangs) on netbsd/386 (7.0.1 GENERIC) Nov 2, 2016

@rsc rsc modified the milestones: Go1.9, Go1.8Maybe Nov 11, 2016

@wenheping

wenheping commented Feb 18, 2017

The same test error of Go-1.8 On NetBSD/amd64(7.0.1 GENERIC).

@bsiegert bsiegert referenced this issue Mar 15, 2017

Closed

os/signal: tests run too long and fail on NetBSD #19295

@bradfitz bradfitz removed the WaitingForInfo label Mar 21, 2017

@gopherbot gopherbot closed this Mar 21, 2017

@bradfitz bradfitz reopened this Mar 21, 2017

@bradfitz bradfitz modified the milestones: Go1.10, Go1.9 Jun 28, 2017

@gopherbot

gopherbot commented Jun 28, 2017

CL https://golang.org/cl/47036 mentions this issue.

gopherbot pushed a commit that referenced this issue Jun 28, 2017

@bradfitz
doc: document the state of NetBSD in the Go 1.9 release notes 
Updates #20836
Updates #19339
Updates #19652
Updates #20835
Updates #16511
Updates #10166
Updates #8574

Change-Id: If9a7f560489f1a8d628dafab227925bd8989326e
Reviewed-on: https://go-review.googlesource.com/47036
Reviewed-by: Ian Lance Taylor <iant@golang.org>
3200207
@gopherbot

gopherbot commented Nov 29, 2017

Change https://golang.org/cl/80515 mentions this issue: runtime: fix sysctl calling convention on netbsd/386

gopherbot pushed a commit that referenced this issue Nov 29, 2017

@bradfitz
runtime: fix sysctl calling convention on netbsd/386 
Thanks to coypoop for noticing at:

  #22914 (comment)

FreeBSD/386 and NetBSD/386 diverged between Go 1.4 and Go 1.5 when
Russ sent https://golang.org/cl/135830043 (git rev 25f6b02)
to change the calling convention of the C compilers to match Go.
But netbsd wasn't updated.

Tested on a NetBSD/386 VM, since the builders aren't back up yet (due
to this bug)

Fixes #22914
Updates #19339
Updates #20852
Updates #16511

Change-Id: Id76ebe8f29bcc85e39b1c11090639d906cd6cf04
Reviewed-on: https://go-review.googlesource.com/80515
Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Benny Siegert <bsiegert@gmail.com>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
70ee9b4
@bradfitz
Owner

bradfitz commented Nov 29, 2017

This is fixed by requiring NetBSD 8-BETA+.

@bradfitz bradfitz closed this Nov 29, 2017

@bradfitz bradfitz referenced this issue Dec 2, 2017

Closed

doc: flesh out Ports section for Go 1.10 release notes #22911

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment