-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
cmd/go: repeating packages for "go test" is racy #13005
Comments
[0 tv@brute ~/go/src/bazil.org/bazil/kv]$ go test . ./...
fork/exec /home/tv/tmp/go-build973088303/bazil.org/bazil/kv/_test/kv.test: text file busy
FAIL bazil.org/bazil/kv 0.001s
fork/exec /home/tv/tmp/go-build973088303/bazil.org/bazil/kv/_test/kv.test: no such file or directory
FAIL bazil.org/bazil/kv 0.001s
ok bazil.org/bazil/kv/kvfiles 0.002s
? bazil.org/bazil/kv/kvmock [no test files]
ok bazil.org/bazil/kv/kvmulti 0.002s
? bazil.org/bazil/kv/kvpeer [no test files]
ok bazil.org/bazil/kv/untrusted 0.004s |
Interesting find. I think the |
Fixed by CL 16136 |
I forgot to add it :) On Tue, Oct 20, 2015, 11:57 PM Andrew Gerrand notifications@github.com
|
I accidentally typoed
go test . ./...
in a build script and noticed an interesting trap: the first.
may be executing tests while the second.
from./...
tries to open the same executable for writing, leading into a "text file is busy" message, if the timing is just right.I would have expected either different temp file names, or
go test
to only run test for a package once, even if it was listed twice.It was pointed out to me that
go test fmt fmt fmt
already runs thefmt
tests just once, so this probably is about the...
logic not participating in the uniquify.The text was updated successfully, but these errors were encountered: