by gerg.ward:

What steps will reproduce the problem?
1. unzip the attached zip file
2. cd test-reporting
2. go test

What is the expected output?

# _/tmp/test-reporting
x_test.go:16:15: expected identifier
FAIL    _/tmp/test-reporting [build failed]

What do you see instead?
# _/tmp/test-reporting
x_test.go:16:15: expected identifier

Which compiler are you using (5g, 6g, 8g, gccgo)?

6g

Which operating system are you using?

Ubuntu 12.10 (quantal)

Which version are you using?  (run 'go version')

go version devel +fa2a0aff01f7 Thu Jan 24 20:46:33 2013 +1100 linux/amd64

(can also reproduce with 1.0.3)

Please provide any additional information below.

The difference between expected and actual output is subtle, and only a problem when
running lots of tests. It's particularly confusing when you have multiple failures, some
of which are reported with the big obvious "FAIL", and some of which are just
buried in compiler output two pages up.

The particular compilation error that triggers this for me is

  func setup() (boguspkg.bogustype, y int) {
  }

i.e. a syntax error combined with a non-existent package. It seems to take *two* errors
to cause this situation. Full working example attached: go-test-error-reporting.zip.

Attachments:

1. go-test-error-reporting.zip (817 bytes)