For example, if an x_test.go file contains a syntax error,
b.test fails with an error message. But it wasn't printing
the same FAIL line that a build failure later would print.
This makes all the test failures that happen (once we
decide to start running tests) consistently say FAIL.
Fixes #4701.
R=golang-dev, bradfitz
CC=golang-dev
https://golang.org/cl/
13431044
testlocal "$bad" 'with bad characters in path'
rm -rf "testdata/$bad"
+TEST error message for syntax error in test go file says FAIL
+export GOPATH=$(pwd)/testdata
+if ./testgo test syntaxerror 2>testdata/err; then
+ echo 'go test syntaxerror succeeded'
+ ok=false
+elif ! grep FAIL testdata/err >/dev/null; then
+ echo 'go test did not say FAIL:'
+ cat testdata/err
+ ok=false
+fi
+rm -f ./testdata/err
+unset GOPATH
+
# Test tests with relative imports.
TEST relative imports '(go test)'
if ! ./testgo test ./testdata/testimport; then
if strings.HasPrefix(str, "\n") {
str = str[1:]
}
+ failed := fmt.Sprintf("FAIL\t%s [setup failed]\n", p.ImportPath)
+
if p.ImportPath != "" {
- errorf("# %s\n%s", p.ImportPath, str)
+ errorf("# %s\n%s\n%s", p.ImportPath, str, failed)
} else {
- errorf("%s", str)
+ errorf("%s\n%s", str, failed)
}
continue
}
--- /dev/null
+package p
+
+func f() (x.y, z int) {
+}