"warning no tests to run"

[Gavin Panella]

On 29 August 2013 09:25, roger peppe <roger.peppe at canonical.com> wrote:
> It seems to me that gwacl should have made sure (as usual)
> that a test fails before making it pass.

I'm the culprit. However, I have an excuse. This was originally
developed as /logging.go, and was moved into a subpackage in rev
90.2.27. I assumed the tests would continue to run, and - tada - there
were no failures, so I moved on.

For me there would have been value in having `go test` draw attention
to missing tests in the ./... case. I didn't do everything I possibly
could to ensure that the tests were still being exercised, but I also
don't feel like I was negligent.

It's hard to keep everyone happy!