Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

runtime: TestNetpollBreak failing on netbsd-arm-bsiegert #35074

Closed
bcmills opened this issue Oct 22, 2019 · 2 comments
Closed

runtime: TestNetpollBreak failing on netbsd-arm-bsiegert #35074

bcmills opened this issue Oct 22, 2019 · 2 comments
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-NetBSD Soon This needs to be done soon. (regressions, serious bugs, outages)
Milestone
Go1.14

Comments

@bcmills
Copy link
Contributor

bcmills commented Oct 22, 2019

Now that #35037 is resolved, the netbsd-arm-bsiegert builder is showing a different failure mode, this time in TestNetpollBreak (https://build.golang.org/log/bc18dc9b999d2adff72d678f0608afc8a6cbc4d9):

--- FAIL: TestNetpollBreak (10.03s)
    proc_test.go:1020: netpollBreak did not interrupt netpoll: slept for: 10.028473916s
FAIL
FAIL	runtime	190.460s

CC @ianlancetaylor @mknyszek
@bcmills bcmills added OS-NetBSD NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. Soon This needs to be done soon. (regressions, serious bugs, outages) labels Oct 22, 2019
@bcmills bcmills added this to the Go1.14 milestone Oct 22, 2019
@bcmills bcmills mentioned this issue Oct 22, 2019
Closed
@ianlancetaylor
Copy link
Contributor

Yes, this one is very puzzling. I don't understand why this test would start failing at CL 202441. I'm also wondering what happens on freebsd-arm and openbsd-arm, but we don't have a builder for the latter and our builders for netbsd-arm and freebsd-arm are limited.

@ianlancetaylor
Copy link
Contributor

This problem has fixed itself, with the dashboard showing two successful runs after an unrelated CL. Optimistically closing.

@golang golang locked and limited conversation to collaborators Oct 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-NetBSD Soon This needs to be done soon. (regressions, serious bugs, outages)
Projects
None yet
Milestone
Go1.14
Development

No branches or pull requests
3 participants
@ianlancetaylor @bcmills @gopherbot