no log tests

Z. Nate Finch nate.finch at canonical.com
Wed Mar 26 19:00:22 UTC 2014


So, I often get failed tests that are so obscured by our log output that I
can't even tell what's failing.  So I made a little thing to filter out the
logs.  Yes, I'm sure you could do this with some bash stuff or grep or
whatever, but I'll write bash when my job or my life depends on it, and not
before.

just do

go get github.com/natefinch/nolog

And then you can run nolog instead of go test.  It passes arguments
through, so you can do

nolog ./... -gocheck.v

(or whatever)
and it'll output everything except the lines that start with [LOG], which
makes it a lot easier to see

The filtering is really dumb, it just filters out lines that start with
[LOG], but it seems to work fine for my needs.

-Nate
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140326/7138e2eb/attachment.html>


More information about the Juju-dev mailing list