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

math/big: TestFloat64SpecialCases fails in slow machines #5407

Closed
gopherbot opened this issue May 4, 2013 · 1 comment
Closed

math/big: TestFloat64SpecialCases fails in slow machines #5407

gopherbot opened this issue May 4, 2013 · 1 comment

Comments

@gopherbot
Copy link

by nicolas.riesco:

Before filing a bug, please check whether it has been fixed since the
latest release. Search the issue tracker and check that you're running the
latest version of Go:

Run "go version" and compare against
http://golang.org/doc/devel/release.html  If a newer version of Go exists,
install it and retry what you did to reproduce the problem.

Thanks.

What steps will reproduce the problem?
If possible, include a link to a program on play.golang.org.
1. go test math/big
2.
3.

What is the expected output?
ok      math/big    xxx.xxxs

What do you see instead?
*** Test killed: ran too long (10m0s).
FAIL    math/big    600.007s

Which compiler are you using (5g, 6g, 8g, gccgo)?
8g

Which operating system are you using?
linux 386

Which version are you using?  (run 'go version')
go version devel +987b23a69416 Fri May 03 17:15:43 2013 +0800 linux/386

Please provide any additional information below.
I'm running the test on an EEE PC 901 (Atom N270@1.60 GHz x 2, 1 GB RAM).
The failure is caused by TestFloat64SpecialCases with cases:
    "long:1e-400000",
    "long:-1e-400000",
@minux
Copy link
Member

minux commented May 4, 2013

Comment 1:

the "long:" prefix precisely means that that particular test case is going to take a
long time,
and that test case will be skipped by the -short mode.
(See http://tip.golang.org/src/pkg/math/big/rat_test.go/#L503)
Thus if you want to pass the math/big test, increase timeout if your CPU is too slow,
like this:
go test -timeout 30m math/big

Status changed to WorkingAsIntended.

@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

2 participants