-
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
cmd/go: -failfast flag does not apply across packages #33038
Comments
/cc @jayconrod @bcmills |
For now, this command helps me a lot:
|
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
Please refrain from "bumping" github threads; see https://github.com/golang/go/wiki/NoPlusOne. If you would like to speed up the resolution of this issue, you can either react with a 👍 on the original post, or look into sending a CL with a test. See https://go.dev/doc/contribute :) |
Note that the flag will stop future tests for a failing package. But tests for other packages will continue. See golang/go#33038
Note that the flag will stop future tests for a failing package. But tests for other packages will continue. See golang/go#33038
Run `go test` to exit as soon as one test fails. While this may mean the test you care about never runs, it's better than waiting for a whole suite after one flake: Since all our acceptance tests are in one package `-failfast` should work: golang/go#33038
Change https://go.dev/cl/529198 mentions this issue: |
Bump :) |
Using
go1.12
The documentation for
failfast
says "Do not start new tests after the first test failure."When running
go test ./... -failfast
and one of the packages has a failure, it continues to run the tests for other packages. My interpretation of the documentation above is thatgo test
would stop after any failure, even if in a different package.The text was updated successfully, but these errors were encountered: