On Mon, Feb 6, 2017 at 1:05 AM, Jed Brown <[email protected]> wrote: > Barry Smith <[email protected]> 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. >
I know the test is broken, but I did already mail the list about this and was waiting for an answer to be worked out. I agree with Satish that running two commands would be great. I could rewrite the example to both write and load it, but it would complicate it. Also, I am trying to get the pattern I expect the user to follow for checkpointing. Matt -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
