[petsc-dev] tiny issues in test harness

Jakub Kruzik jakub.kruzik at vsb.cz
Mon Oct 1 05:48:29 CDT 2018


ecc1beb596a8093f7509ca38016ed30c93784193 works for me. Thanks!

#2 Yes, using double quotes works, but it took me a while to figure out 
why the filter didn't work for me with single quotes. Might be worth 
mentioning that filters with single quotes might not work correctly in 
dev manual and/or putting guards into parsing/petsc_testrun.

Jakub

On 9/26/18 11:00 PM, Scott Kruger wrote:
>
>
> Fix for #1 is merged into next.
>
> See ecc1beb596a8093f7509ca38016ed30c93784193
>
> For #2, I think it'll work if you use double quotes and egrep.
> If you do this:
> cd $PETSC_DIR/src/sys/examples/test
> grep filter *.c
>
> I think you'll see some examples of complicated filters that Barry got 
> working.
>
> Scott
>
>
> On 8/14/18 4:05 AM, Jakub Kruzik wrote:
>> Hi all,
>>
>> I started using test harness in PERMON and find out a couple of 
>> issues with it.
>>
>> 1) multiple "args:" keywords in "test:" in "testset:" are ignored 
>> except for the last "args:" keyword. See attached MWE and check it with
>>
>> python2 ${PETSC_DIR}/config/testparse.py -t ex1.c -v 3
>>
>> 2) single quotes can't be used in "filter:"  keyword. E.g. filter: 
>> grep 'r =' generates
>>
>> petsc_testrun ... 'grep 'r =''
>>
>> resulting in filter being "grep r". Might be worth mentioning this in 
>> dev manual and/or putting guards into parsing/petsc_testrun.
>>
>> Best,
>>
>> Jakub
>>
>


More information about the petsc-dev mailing list