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

time: TestOverflowRuntimeTimer failing #8136

gpaul opened this issue Jun 2, 2014 · 5 comments

time: TestOverflowRuntimeTimer failing #8136

gpaul opened this issue Jun 2, 2014 · 5 comments


Copy link

@gpaul gpaul commented Jun 2, 2014

Please merge this into issue #6874 and reopen it.

go version go1.3beta2 +177ed19da89f Wed May 28 14:04:31 2014 -0400 linux/amd64

What steps reproduce the problem?
If possible, include a link to a program on

This failure is reproduced quickly by running this script.

set -xe
go test -c -i time
while /bin/true
    GOMAXPROCS=$[ 1 + $[ RANDOM % 256 ] ]
    ./time.test -test.v

What happened?
=== RUN TestOverflowRuntimeTimer-251
--- FAIL: TestOverflowRuntimeTimer-251 (0.10 seconds)
    sleep_test.go:391: runtime timer stuck: overflow in addtimer

What should have happened instead?
=== RUN TestOverflowRuntimeTimer-251
--- PASS: TestOverflowRuntimeTimer-251 (0.01 seconds)

Please provide any additional information below.
uname -a
Linux mybox 3.6.11-4.fc16.x86_64 #1 SMP Tue Jan 8 20:57:42 UTC 2013 x86_64 x86_64 x86_64
Copy link
Contributor Author

@gpaul gpaul commented Jun 2, 2014

Comment 1:

This also fails on the latest release-branch.go1.3:
go version go1.3rc1 linux/amd64
Copy link

@ianlancetaylor ianlancetaylor commented Jun 3, 2014

Comment 2:

Labels changed: added repo-main, release-go1.3maybe.

Copy link

@ianlancetaylor ianlancetaylor commented Jun 3, 2014

Comment 3:

Actually, resetting this to Go 1.4.  It appears to indicate a problem with the test
rather than an actual problem with the package.

Labels changed: added release-go1.4, removed release-go1.3maybe.

Copy link

@gopherbot gopherbot commented Jun 12, 2014

Comment 4:

CL mentions this issue.
Copy link

@robpike robpike commented Jun 12, 2014

Comment 5:

This issue was closed by revision 83c8140.

Status changed to Fixed.

@gpaul gpaul added fixed labels Jun 12, 2014
@rsc rsc added this to the Go1.4 milestone Apr 14, 2015
@rsc rsc removed the release-go1.4 label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 25, 2016
wheatman added a commit to wheatman/go-akaros that referenced this issue Jun 25, 2018
The test requires that timerproc runs, but busy loops and starves
the scheduler so that, with high probability, timerproc doesn't run.
Avoid the issue by expecting the test to succeed; if not, a major
outside timeout will kill it and let us know.

As you can see from the diffs, there have been several attempts to
fix this with chicanery, but none has worked. Don't bother trying
any more.

Fixes golang#8136.

R=rsc, josharian
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.