Nate,
sed and tee would have done this for you.
Take a look at this video; it explains the unix way.
http://www.youtube.com/watch?v=tc4ROCJYbm0
It'll save you hours in the long run.
Andrew
On Wed, Mar 26, 2014 at 9:29 PM, Nate Finch wrote:
> I said I don't do bash :), plus, I added a flag so
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 wrote:
> Alternatively you can run the tests with -
I said I don't do bash :), plus, I added a flag so I can output the full
log to a file at the same time.
On Mar 26, 2014 5:22 PM, "David Cheney" wrote:
> What's wrong with go test 2>&1 | grep -v '[LOG]' ?
>
>
> On Thu, Mar 27, 2014 at 8:21 AM, roger peppe wrote:
>
>> Alternatively you can run t
What's wrong with go test 2>&1 | grep -v '[LOG]' ?
On Thu, Mar 27, 2014 at 8:21 AM, roger peppe 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" wrote:
>
>> So, I often g
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" 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
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
b
