-
Notifications
You must be signed in to change notification settings - Fork 346
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
Add a -version flag to differentiate two gotests binaries #133
Comments
@lepinkainen Sorry you ran into that issue. If anyone wants to send a PR that will include the version (including git commit), I will review and approve it. |
@cweill I can take a look into adding this |
@teddylear Sounds good to me. A PR will be welcome. |
@cweill Added PR. As noted in PR, there appears to be an existing bug in the with the 1.16 version of the tests. Please let me know if there is a ticket for that already or if I should make one. |
@teddylear can you tell more about failed tests? (maybe in sep issue) |
Fwiw,
|
I have two setups, in one the
-parallel
option works just fine in vscode - it generates parallel test cases as it should. In the other it doesn't do anything (not reporting errors in custom flags is a problem in the vscode go plugin, which is not the issue here).Both were installed with
go get -u github.com/cweill/gotests/...
when in the $HOME directory within 15 minutes of each other.One installation looks like this (go version go1.14.3 darwin/amd64) - no
-parallel
optionThe other like this (go version go1.13.8 linux/amd64) -
-parallel
found and works perfectlyTook me a LONG while to figure out why vscode was generating parallel tests on one and not on the other... There is no way to differentiate the two installs except by manually comparing the help texts - which themselves only appear when giving a faulty flag. Just running
gotests
by itself gives the exact same defaults on both installations.It would be really useful to have a
-version
flag in gotests to debug these issues and maybe make it possible for plugins like the Go vscode plugin to determine if some options are available or not.Bonus question: why did both platforms and go versions get a completely different version of gotests?
The text was updated successfully, but these errors were encountered: