Hi Mike,
> I like to run under strace to see why the test is failing. I can't
> seem to find where stderr is being redirected. I thought it was in
> tap-driver.sh so I patched it but still no strace output.
Have you tried strace(1)'s -o option so its output doesn't appear on
stderr and you don't
Hi,
Regarding the topic of colored TAP output, it seems that there are good
reasons for having both plain-text and colored-text output. There are
also reasons for people to customize the colors.
Here are two ideas that might help. For all I know, the code may already
be structured this way
On Oct 26, 2017 5:59 AM, "Ralph Corderoy" wrote:
Hi Mike,
> I like to run under strace to see why the test is failing. I can't
> seem to find where stderr is being redirected. I thought it was in
> tap-driver.sh so I patched it but still no strace output.
Have you tried strace(1)'s -o option s
> On Oct 26, 2017 5:59 AM, "Ralph Corderoy" wrote:
>
> Hi Mike,
>
> > I like to run under strace to see why the test is failing. I can't
> > seem to find where stderr is being redirected. I thought it was in
> > tap-driver.sh so I patched it but still no strace output.
>
> Have you tried strace(1