-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
x/build: run standard library tests without -short #17472
Comments
I also noticed the the Maybe non-trybot (post-submit) builders should run in non-short mode. |
We definitely need some builder somewhere running in non-short mode. Another example, just off the top of my head: #15979. |
I'm going to break out the individual failures into new issues, so that they get looked at. For the moment, I'm going to ignore tests that are merely slow; my list of issues to break out will be generated by |
I've split out all the failing (not merely slow) tests into their own issues. Once those are fixed, we should give this another whirl. And set up a builder to do it regularly. |
CL https://golang.org/cl/32585 mentions this issue. |
TestAssembly takes 20s on my machine, which is too slow for normal operation. Marking as -short has its dangers (#17472), but hopefully we'll soon have a builder for that. All the SSA tests are hermetic and not time sensitive and can thus be run in parallel. Reduces the cmd/compile/internal/gc test time during all.bash on my laptop from 42s to 7s. Updates #17751 Change-Id: Idd876421db23b9fa3475e8a9b3355a5dc92a5a29 Reviewed-on: https://go-review.googlesource.com/32585 Run-TryBot: Josh Bleecher Snyder <[email protected]> Reviewed-by: Brad Fitzpatrick <[email protected]>
I just ran I'm going to repurpose this issue as being to run a builder without -short, and move it off the Go 1.8 release milestone. |
I see an odd failure in the original test output: --- FAIL: TestRepoRootForImportPath (1.02s) In other words, the test is passing a URL ending in "swift.git" to repoRootForImportPath but the path returned ends in "swift". The test is expecting the returned URL to end with "swift.git". I'm seeing the same failure in my area, and I was curious if anyone could give me tips Was that failure one of the failures that was split out and fixed in this issue? Whoops. Nevermind. I saw my problem in 1.7ish and It goes away in 1.8.3. Must be due to some vcs.go changes. |
Change https://golang.org/cl/58050 mentions this issue: |
This is necessary when you aren't actively changing the runtime. Oops. Also, run the tests on the builders, to avoid silent failures (#17472). Change-Id: I1fc03790cdbddddb07026a772137a79919dcaac7 Reviewed-on: https://go-review.googlesource.com/58050 Run-TryBot: Josh Bleecher Snyder <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]>
The specific issues reported here has been fixed and for the general suggestion of running go test without -short this is a dup of the older #10456; closing this. |
I saw some bugs with go test in cmd/go, so I decided to run everything without -short. Need to run go test without -short once in a while on the whole tree. I tried it today and there were some disappointments.
I'll let someone else decide if they want to break out individual bugs for the failures, but the point made in the first paragraph still stands: Before release, test everything.
What version of Go are you using (
go version
)?go version devel +7a60a96 Sat Apr 30 05:59:54 2016 +0000 darwin/amd64
What operating system and processor architecture are you using (
go env
)?wally=% go env
GOARCH="amd64"
GOBIN="/Users/r/bin"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/r"
GORACE=""
GOROOT="/Users/r/go"
GOTOOLDIR="/Users/r/go/pkg/tool/darwin_amd64"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/r3/cryt3b891yj6rzqr8vzcn2xc0000gn/T/go-build408997659=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
wally=%
What did you do?
cd $GOROOT/src; go test ./...
What did you expect to see?
Everything passes.
What did you see instead?
Most do well, but some crash and some (math/big for example) are just crazy slow and time out
The text was updated successfully, but these errors were encountered: