Skip to content

runtime: TestCgoSignalDeadlock slow down on windows-386 builder #6054

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

Closed
alexbrainman opened this issue Aug 6, 2013 · 2 comments
Closed

Comments

@alexbrainman
Copy link
Member

after recent change

changeset:   17538:6423f26d0193
user:        Dmitriy Vyukov <dvyukov@google.com>
date:        Sun Aug 04 14:08:13 2013 +0400
summary:     runtime: disable dynamic priority boosting on windows

windows-386 builder is failing to complete

go test runtime -short -timeout=300s -cpu=1,2,4

in time. It looks like TestCgoSignalDeadlock takes much longer to run now. See attached
"go test ..." command output for hg revisions 17537 and 17538. The output is
from our windows-386 builder.

Alex

Attachments:

  1. rev17537.txt (32768 bytes)
  2. rev17538.txt (32768 bytes)
@dvyukov
Copy link
Member

dvyukov commented Aug 6, 2013

Comment 1:

sent https://golang.org/cl/12531043/

@dvyukov
Copy link
Member

dvyukov commented Aug 7, 2013

Comment 2:

This issue was closed by revision 1590abe.

Status changed to Fixed.

@rsc rsc added this to the Go1.2 milestone Apr 14, 2015
@rsc rsc removed the go1.2maybe label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants