GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
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?
to your account
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build473380735=/tmp/go-build -gno-record-gcc-switches"
I expected no tests to execute after the first test failed.
The second test was executed, even though -test.failfast was specified.
Note, things work as expected if t.Fatal is changed to t.Error.
The issue is with FatalX which calls runtime.Goexit. This causes the failure counting to be skipped in tRunner.
Fix coming shortly.
Change https://golang.org/cl/101035 mentions this issue: testing: failfast fails fast when Fatal called
testing: failfast fails fast when Fatal called
Any chance that the fix for this could be backported to the 1.10.x stream?
@jdef No, sorry.