[petsc-dev] test harness: output of actually executed command for V=1 gone?

[Scott Kruger]

On 9/20/19 2:49 PM, Jed Brown wrote:
> Hapla  Vaclav via petsc-dev <petsc-dev at mcs.anl.gov> writes:
> 
>> On 20 Sep 2019, at 19:59, Scott Kruger <kruger at txcorp.com<mailto:kruger at txcorp.com>> wrote:
>>
>>
>> On 9/20/19 10:44 AM, Hapla Vaclav via petsc-dev wrote:
>> I was used to copy the command actually run by test harness, change to example's directory and paste the command (just changing one .. to ., e.g. ../ex1 to ./ex1).
>> Is this output gone? Bad news. I think there should definitely be an option to quickly reproduce the test run to work on failing tests.
>>
>> I only modified the V=0 option to suppress the TAP 'ok' output.
>>
>> I think you are referring to the 'not ok' now giving the error code instead of the cmd which is now true regardless of V.  This was suggested by others.  I defer to the larger group on what's desired here.
>>
>> Note that is sometimes tedious to deduce the whole command line from the test declarations, for example because of multiple args: lines.
>>
>> Personally, I recommend just cd'ing into the test directory and running the scripts by hand.
>>
>> For example:
>> cd $PETSC_ARCH/tests/ksp/ksp/examples/tests/runex22
>> cat ksp_ksp_tests-ex22_1.sh
>> mpiexec  -n 1 ../ex22   > ex22_1.tmp 2> runex22.err
>>
>> OK, this takes a bit more time but does to job.
> 
> That's yucky.  I think we should have an option to print the command(s)
> that would be run, one line per expanded {{a b c}}, so we can copy-paste
> into the terminal with only one step of indirection.

Ugh.  I'm dealing with bash at this level - not python.

Satish and Barry:  Do we need the Error codes or can I revert to 
previous functionality?

Scott


-- 
Tech-X Corporation               kruger at txcorp.com
5621 Arapahoe Ave, Suite A       Phone: (720) 974-1841
Boulder, CO 80303                Fax:   (303) 448-7756