Hi Rog, I tried this but it causes unrelated test failures as tests which scan for output now no longer find anything as the global log level is raised to ERROR.
Maybe this is a bug. Cheers Dave On Thu, Mar 27, 2014 at 8:21 AM, roger peppe <rogpe...@gmail.com> wrote: > Alternatively you can run the tests with -juju.log ERROR (sent from my > phone so unable to double check the extact syntax) > On 26 Mar 2014 19:00, "Z. Nate Finch" <nate.fi...@canonical.com> wrote: > >> 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 >> >> -- >> Juju-dev mailing list >> Juju-dev@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju-dev >> >> > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev > >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
