[petsc-dev] every test example runs in a new directory with new test harness

Jed Brown jed at jedbrown.org
Mon Feb 6 01:05:09 CST 2017

Barry Smith <bsmith at mcs.anl.gov> writes:

>   test:
>     suffix: restart_0
>     requires: hdf5
>     args: -run_type test -refinement_limit 0.0    -bc_type dirichlet -interpolate 1 -petscspace_order 1 -dm_view hdf5:sol.h5 -vec_view hdf5:sol.h5::append
>   test:
>     suffix: restart_1
>     requires: hdf5
>     args: -run_type test -refinement_limit 0.0    -bc_type dirichlet -interpolate 1 -petscspace_order 1 -f sol.h5 -restart
> See a problem?
> Should the same run of the example view the files and then load them back in? versus trying to read in a data file from another run that may not even have been created before and even if it was, the file was definitely created  in a different directory? 

So if write only is broken, do you want both to fail?  I think it's
better to read and write separately, with comparison using h5diff, since
that independently tests read vs write and establishes backward
compatibility, which you'd really like the test system to make you deal
with explicitly.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20170206/a2657b7b/attachment.sig>

More information about the petsc-dev mailing list