Re: [Qemu-devel] Status and RFC of patchew testings on QEMU

["Daniel P. Berrange" <berrange@redhat.com>]

On Mon, Jul 17, 2017 at 11:06:12AM +0100, Peter Maydell wrote:
> On 17 July 2017 at 10:39, Fam Zheng <famz@redhat.com> wrote:
> > On Mon, 07/17 10:28, Peter Maydell wrote:
> >> Ideally we'd streamline our make process to not produce so much
> >> irrelevant output :-)
> >
> > Does that mean to make "quite-command" absolutely quiet if V=1 is not specified?
> 
> The current 'quiet' mode is not quite aimed at the same purpose:
> it's good for interactive use where you don't want the long detail
> of command lines but you do want some periodic indication of
> progress through the compile. For entirely noninteractive
> setups like travis and patchew there's no need to produce
> what is in effect a rather verbose progress bar...

For unattended automated systems though, I think running with V=1 is
preferrable to quiet mode. When you don't have direct access to the
test system to reproduce systems, every bit of information that you
can get from the logs is potentially useful, including full compiler
args. The flipside is that in other cases the verbose output can
obscure the error messages you are after - depends what your're trying
to debug - code problems vs build system problems.

Perhaps it would be best to extract stderr separately. ie run with V=1
and have a full log that contains stdout+stderr as normal, but have a
second log which only contains stderr contents to make it easier to
see the error / warning messages in isolation from the "noise".


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|