Skip to content

runtime: TestCallbackPanic fails on windows #4971

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.

Sign up for GitHub

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
Closed
dvyukov opened this issue Mar 3, 2013 · 3 comments
Closed

runtime: TestCallbackPanic fails on windows #4971

dvyukov opened this issue Mar 3, 2013 · 3 comments
Labels
FrozenDueToAge
Milestone
Go1.1

Comments

@dvyukov
Copy link
Member

dvyukov commented Mar 3, 2013 

TestCallbackPanic is flaky on windows after the new scheduler:

# runtime -cpu=1,2,4
--- FAIL: TestCallbackPanic-4 (0.00 seconds)
    syscall_windows_test.go:188: locked OS thread on exit from TestCallbackPanic
FAIL
FAIL    runtime 84.960s

http://build.golang.org/log/21dc7c858124261a0f258e27cbeb6f26873fe54f
http://build.golang.org/log/77462841e01db05ddcf29d769c829a5a205c0958
http://build.golang.org/log/05a2a5c71fc2f3415419e836d4cc3fa0161e8e94

The observations are: it usually happens with GOMAXPROCS=4, execution time 84.960s is
suspiciously high.
@rsc
Copy link
Contributor

rsc commented Mar 8, 2013

Comment 1:

When I've seen the high system time it is because usleep is not actually sleeping.
However, that should just slow things down; it should not cause the error shown.

Labels changed: added priority-later, removed priority-triage.

Status changed to Accepted.

@rsc
Copy link
Contributor

rsc commented Mar 8, 2013

Comment 2:

https://golang.org/cl/7627043

Owner changed to @rsc.

Status changed to Started.

@rsc
Copy link
Contributor

rsc commented Mar 8, 2013

Comment 3:

This issue was closed by revision 1a4599b.

Status changed to Fixed.

@rsc rsc added this to the Go1.1 milestone Apr 14, 2015
@rsc rsc removed the go1.1 label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
@rsc rsc removed their assignment Jun 22, 2022
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Go1.1
Development

No branches or pull requests
3 participants
@rsc @dvyukov @gopherbot