Re: [petsc-dev] remove temporary output with new test-harness

Satish, I fixed the errors related to the DATAFILESPATH in ex37 Barry > On Dec 3, 2017, at 10:51 AM, Satish Balay wrote: > > Hm - how do we reproduce this? > > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/12/03/examples_full_next.log > > There are a

Re: [petsc-dev] remove temporary output with new test-harness

On Sun, 3 Dec 2017, Satish Balay wrote: > But you can do this 'rm' manually. make -f gmakefile cleantest && make -f gmakefile test Satish

Re: [petsc-dev] remove temporary output with new test-harness

Hm - how do we reproduce this? http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/12/03/examples_full_next.log There are a bunch of failures about - but I dn't see 'petsc-' prefix in them. Satish On Sun, 3 Dec 2017, Stefano Zampini wrote: > An inconsistency I have just noted. The

Re: [petsc-dev] remove temporary output with new test-harness

On Sun, 3 Dec 2017, Stefano Zampini wrote: > The issue may arise with output files from a previous test run. Wouldn't those files get overwritten when the test is rerun? > Would it be possible to run ‘rm -rf *’ in the example temporary directory > before running the test? The current thought

Re: [petsc-dev] remove temporary output with new test-harness

An inconsistency I have just noted. The command suggested to re-run failed tests does not work (it provides ‘petsc’ instead of the source tree location ’sees_tutorials’ as per the example below) # To rerun failed tests: # make -f gmakefile.test test search='petsc-runex62_fetidp_3d_tet'

Re: [petsc-dev] remove temporary output with new test-harness

The issue may arise with output files from a previous test run. Would it be possible to run ‘rm -rf *’ in the example temporary directory before running the test? Thanks, Stefano > On Nov 29, 2017, at 8:36 PM, Scott Kruger wrote: > > > > On 11/29/17 10:25 AM, Matthew