"warning no tests to run"

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-08-29 12:25, roger peppe wrote:
> Hmm, I'm not sure. It's perhaps ok in some circumstances to have no
> tests defined in a package even if there are _test.go files (if the
> tests are platform-dependent, for example, or there are examples).
> 
> It seems to me that gwacl should have made sure (as usual) that a
> test fails before making it pass.
> 
> There are other ways that tests might not be hooked in (failing to
> call Suite for example), and changing go test won't catch those, so
> I'm inclined to leave it alone.
> 

Running 0 tests almost always indicates a failure and we already have
the warning about that case. It just doesn't show up when you do ./...

And it will tell you if there are no test files. It doesn't seem like
much of a stretch to ask it to also report the 'no tests run' warning
during ./...

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlIfCMEACgkQJdeBCYSNAANgewCdHzjjE0Js077swHUgO9wv+n0l
LgIAn30l0GVVe81tu7ZW1GCjVRUZxYd0
=Bwes
-----END PGP SIGNATURE-----