Skip to content

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

Closed

Description

@minux

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?

Activity

  1. added this to the Go1.8Early milestone on Jul 27, 2016
  2. bradfitz commented on Jul 27, 2016

    @bradfitz
    Contributor

    Ian is on vacation.

  3. bradfitz commented on Jul 27, 2016

    @bradfitz
    Contributor
  4. bsiegert commented on Jul 27, 2016

    @bsiegert
    Contributor

    Is that the same as #10027?

  5. minux commented on Jul 27, 2016

    @minux
    MemberAuthor
  6. minux commented on Jul 27, 2016

    @minux
    MemberAuthor
  7. ianlancetaylor commented on Jul 28, 2016

    @ianlancetaylor
    Contributor

    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.

  8. added
    WaitingForInfoIssue is not actionable because of missing required information, which needs to be provided.
    NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.
    on Sep 26, 2016
  9. rsc commented on Oct 20, 2016

    @rsc
    Contributor

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

  10. 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
  11. modified the milestones: Go1.9, Go1.8Maybe on Nov 11, 2016
  12. wenheping commented on Feb 18, 2017

    @wenheping

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

  13. removed
    WaitingForInfoIssue is not actionable because of missing required information, which needs to be provided.
    on Mar 21, 2017
  14. modified the milestones: Go1.10, Go1.9 on Jun 28, 2017
  15. gopherbot commented on Jun 28, 2017

    @gopherbot
    Contributor

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

  16. gopherbot commented on Nov 29, 2017

    @gopherbot
    Contributor

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

  17. bradfitz commented on Nov 29, 2017

    @bradfitz
    Contributor

    This is fixed by requiring NetBSD 8-BETA+.

  18. locked and limited conversation to collaborators on Nov 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    FrozenDueToAgeNeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.OS-NetBSD

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions