Scott,

    Thanks but it does not appear to work. In the branch 
barry/vec-to-test-harness I have enabled it by adding a test: rule and boom it 
doesn't try to build the example probably. Please check out the branch and see 
if you can figure out the problem, feel free to put a correction into the test 
branch if you know the correction. 

$ ./config/gmakegentest.py 
Warning: 
/Users/barrysmith/Src/petsc/src/dm/examples/tutorials/output/ex13f90_1.out not 
found.
~/Src/petsc (barry/vec-to-test-harness *=) arch-basic
$ make -f gmakefile test globsearch="dm*ex13f90*"
Use "/usr/bin/make V=1" to see verbose compile lines, "/usr/bin/make V=0" to 
suppress.
          FC arch-basic/tests/src/dm/examples/tutorials/ex13f90.o
/Users/barrysmith/Src/petsc/src/dm/examples/tutorials/ex13f90.F90:25:6:

   use ex13f90aux
      1
Fatal Error: Can't open module file 'ex13f90aux.mod' for reading at (1): No 
such file or directory
compilation terminated.
make: *** [arch-basic/tests/src/dm/examples/tutorials/ex13f90.o] Error 1
~/Src/petsc (barry/vec-to-test-harness *=) arch-basic

The test branch also fails with 

$ make -f gmakefile test globsearch="vec*ex7*"
Use "/usr/bin/make V=1" to see verbose compile lines, "/usr/bin/make V=0" to 
suppress.
          CC arch-basic/tests/src/vec/vec/examples/tutorials/ex7.o
     CLINKER arch-basic/tests/src/vec/vec/examples/tutorials/ex7
Undefined symbols for architecture x86_64:
  "_ex7f_", referenced from:
      _main in ex7.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [arch-basic/tests/src/vec/vec/examples/tutorials/ex7] Error 1
~/Src/petsc (barry/vec-to-test-harness *=) arch-basic




> On Nov 20, 2017, at 10:12 AM, Scott Kruger <[email protected]> wrote:
> 
> 
> 
> depends keyword:
> 
> From:
>  dm/examples/tutorials/ex13f90.F90
> 
> !/*TEST
> !
> !   build:
> !      requires: !complex
> !      depends:  ex13f90aux.F90
> !
> !TEST*/
> 
> 
> 
> Scott
> 
> 
> On 11/19/17 10:48 AM, Smith, Barry F. wrote:
>>   Scott,
>>    I asked you this before and you responded but I forgot and lost your 
>> response.
>>    For tests that rely on multiple source files can the test harness handle 
>> it? How? For example src/vec/vec/examples/tutorials/ex21f90.F90
>>    Is there a list of all keywords that are searched for when generating the 
>> tests from the source code?
>>    Thanks
>>    Barry
> 
> -- 
> Tech-X Corporation               [email protected]
> 5621 Arapahoe Ave, Suite A       Phone: (720) 974-1841
> Boulder, CO 80303                Fax:   (303) 448-7756

Reply via email to