gocheck flags must follow ./path test paths

[Dan Kortschak]

It seems that gocheck somehow clobbers the args list since the position of -gocheck.v impacts on whether calling a test on a specific path is valid. When -gockeck.v+ is specified the path must precede it, otherwise the path is set to '.'.

.../code.google.com/p/biogo$ go test -gocheck.v ./align
? code.google.com/p/biogo [no test files]
.../code.google.com/p/biogo$ go test ./align
ok code.google.com/p/biogo/align 0.010s
.../code.google.com/p/biogo$ go test ./align -gocheck.v
ok code.google.com/p/biogo/align 0.010s

[Dan Kortschak (dan-kortschak)]

It seems, further, that the trailing -gocheck.v+ is then ignored.