-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: *** Test killed with quit: ran too long (5-10m0s) w/ go1.5beta2 on linux/arm (Raspberry Pi 2) #11779
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
Comments
Looks like a timeout running the cmd/go tests, which admittedly take a long time. Your installation succeeded--it was just the tests that failed. On your system, can you run go test -test.v -test.short cmd/go and paste the output? Thanks. It will take a long time to run. What I want to know is which tests took the longest. |
I cannot speak for the OP, but this is what mine is doing.
|
|
Thanks. I see the following tests taking at least 10 seconds: TestNoteReading (42.61s) |
CL https://golang.org/cl/12364 mentions this issue. |
CL https://golang.org/cl/12363 mentions this issue. |
On my laptop reduces time required for test from 22 seconds to 0.14 seconds. Update #11779. Change-Id: I715d85bd9c6f7683c6915eedd2539813aa5efc58 Reviewed-on: https://go-review.googlesource.com/12363 Reviewed-by: David Crawshaw <crawshaw@golang.org> Reviewed-by: Andrew Gerrand <adg@golang.org>
It changes GOROOT, so we shouldn't run it in short mode. Also, it's fairly slow. Update #11779. Change-Id: I3d3344954cf9b2ac70070c878a67cb65ac8fd85c Reviewed-on: https://go-review.googlesource.com/12364 Run-TryBot: Ian Lance Taylor <iant@golang.org> Reviewed-by: Andrew Gerrand <adg@golang.org>
If you have a chance, could you try current tip? The cmd/go test should take over a minute less; I'd like to find out whether that seems to be enough to get it back under the deadline. Thanks. |
re-run at tip
|
./all.bash re-run from tip (go version devel +f35868a Mon Jul 20 03:27:22 2015 +0000 linux/arm)
|
Speed up the test suite by building the errors package rather than the strings package in some cases where the specific package we are building doesn't matter. The errors package is smaller, and doesn't have any assembler code. Also make a couple of tests run in parallel. Update #11779. Change-Id: I62e47f8655f9d85bf93c70ae6e6121276d96aee0 Reviewed-on: https://go-review.googlesource.com/12365 Run-TryBot: Ian Lance Taylor <iant@golang.org> Reviewed-by: David Crawshaw <crawshaw@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
The errors package is smaller and builds faster. Update #11779. Change-Id: Iaf2d43734ec4b0aa325590eb5d38522306b608cb Reviewed-on: https://go-review.googlesource.com/12366 Reviewed-by: David Crawshaw <crawshaw@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
CL https://golang.org/cl/12368 mentions this issue. |
I think this should be fixed now, but please reopen if not. Thanks. |
confirmed fixed. go version devel +3051ab2 Mon Jul 20 21:55:20 2015 +0000 linux/arm |
Just for reference, I'm running on an 8 core Intel Xeon E5-2650. I get the following timings: go version devel +6c7acdf Wed Jul 22 01:25:32 2015 +0000 linux/amd64
TestWildcardsDoNotLookInUselessDirectories 26.12 |
Huh, "go list" on your system is really really slow. I wonder why? You can see above that TestWildcardsDoNotLookInUselessDirectories on the Raspberry PI takes only a few seconds, not 26. It's probably worth opening a different issue for what you are seeing. Thanks. |
the tests failed in the same place |
You have to lower the stack size and increase the timouts for ./all.bash to On Sun, Sep 27, 2015 at 11:14 AM, johnstall notifications@github.com
|
On the Raspberry Pi 2 (900MHz quad-core ARM Cortex-A7 CPU 1GB RAM) running Raspbian (Linux raspberry pi 4.0.7-v7+ #801) ./all.bash fails during the Testing Packages phase:
(see https://gist.github.com/ajstarks/0c4af5aac10488be17de for the full transcript)
The text was updated successfully, but these errors were encountered: