Re: patch testsuite - verbose logging

["Frank Ch. Eigler" <fche@elastic.org>]

Hi -

> I agree it would be good to have a bit more information in the dwz.log
> file. But -x is very verbose. I might get lost. But maybe others think
> it is fine. I am not against it. But I think just capturing stdout and
> verbose log it is fine. We can add some extra echos in the tests.

There is no 'verbose log' content in the .log file possible at the
present in the sense of RUNTESTFLAGS=-v.  These log files are for
helping someone debug failing tests, so normally one does not need to
look at them, let alone get lost.

> > Accidentally, this makes debuginfod-involving tests pass, since their
> > stderr DEBUGINFOD_PRGRESS traffic show up in stdout rather than
> > stderr (which is recorded as a fail).
> 
> I think that is a reason to not do the 2>@ redirection.
> We did recently find an issue with gdb-add-index because it had error
> output.  And I think we would like to know if the tests accidentially
> triggered debuginfod [...]

A simpler cure to that is to have the testuite makefile driver unset
$DEBUGINFOD_URLS before invoking dejagnu.

- FChE