Re: [PATCH v3 9/9] run_tests: log stderr

["Radim Krčmář" <rkrcmar@redhat.com>]

2016-05-10 13:41+0200, Paolo Bonzini:
> On 15/04/2016 22:52, Radim Krčmář wrote:
>>  	echo "exec {stdout}>&1"
>>  	echo "RUNTIME_log_stdout='>(cat >&\$stdout)'"
>> +	echo "RUNTIME_log_stderr=>(cat >&2)"
>>  
>>  	cat scripts/runtime.bash
>>  
>> diff --git a/scripts/runtime.bash b/scripts/runtime.bash
>> index fc4be91d8727..ff2d98b547b5 100644
>> --- a/scripts/runtime.bash
>> +++ b/scripts/runtime.bash
>> @@ -61,7 +61,8 @@ function run()
>>  
>>      # extra_params in the config file may contain backticks that need to be
>>      # expanded, so use eval to start qemu.  Same for $RUNTIME_log_stdout.
>> -    summary=$(eval $cmdline > >(eval "tee -a $RUNTIME_log_stdout" | extract_summary))
>> +    summary=$(eval $cmdline > >(eval "tee -a $RUNTIME_log_stdout" | extract_summary) \
>> +                            2>> $RUNTIME_log_stderr)
> 
> Whoa, so this uses the outer eval?

No, RUNTIME_log_stderr is evaluated only at the time of definition,
which makes it inconsistent with RUNTIME_log_stdout.

>                                     Perhaps the 2>> should move before
> the >.

I will drop this patch ... it's too insane and Drew liked stderr in
./run_tests.sh output.  Sorry.