November 2017 - petsc-dev - mailman3.cels.anl.gov

Re: [petsc-dev] BuildSystem: how to prevent 'make clean' before 'make'
by Blaise A Bourdin 29 Nov '17

29 Nov '17

Unfortunately, the weakest assumption is that each package’s build system is not screwed up… Blaise > On Nov 29, 2017, at 5:40 PM, Satish Balay <balay(a)mcs.anl.gov> wrote: > > Sure - there are lots of assumptions in GNUPackage and CMAKEPackage > [they assume most packages behave similarly wrt these types of builds] > > And one can also override these default routines provided. > > Some pacakges might provide a different 'clean' target. And some might prefer > VPATH? builds? [i.e mkdir objdir && cd objdir && ../configure && make]. > > The CMAKE packages default to this mode. Perhaps we need to add this for gnupackages aswell.. > > Satish > > On Wed, 29 Nov 2017, Blaise A Bourdin wrote: > >> Thanks. >> >> I understand that it is not optimal. But OTOH, you are also assuming that make clean does what it is supposed to do… >> >> Blaise >> >> >>> On Nov 29, 2017, at 5:29 PM, Satish Balay <balay(a)mcs.anl.gov> wrote: >>> >>> Right now there is no provision for this. The following can add it. >>> >>> >>>>>>>>>>> >>> $ git diff >>> diff --git a/config/BuildSystem/config/package.py b/config/BuildSystem/config/package.py >>> index 14de19502b..f9a2e68a25 100644 >>> --- a/config/BuildSystem/config/package.py >>> +++ b/config/BuildSystem/config/package.py >>> @@ -80,6 +80,7 @@ class Package(config.base.Configure): >>> self.makerulename = '' # some packages do too many things with the make stage; this allows a package to limit to, for example, just building the libraries >>> self.installedpetsc = 0 >>> self.installwithbatch = 0 # install the package even though configure is running in the initial batch mode; f2blaslapack and fblaslapack for example >>> + self.skipcleanbeforebuild = 0 # skip running 'make clean' before starting a fresh build of a package >>> return >>> >>> def __str__(self): >>> @@ -1322,7 +1323,8 @@ class GNUPackage(Package): >>> if self.parallelMake: pmake = self.make.make_jnp+' '+self.makerulename+' ' >>> else: pmake = self.make.make+' '+self.makerulename+' ' >>> >>> - output2,err2,ret2 = config.base.Configure.executeShellCommand('cd '+self.packageDir+' && '+self.make.make+' clean', timeout=200, log = self.log) >>> + if not self.skipcleanbeforebuild: >>> + output2,err2,ret2 = config.base.Configure.executeShellCommand('cd '+self.packageDir+' && '+self.make.make+' clean', timeout=200, log = self.log) >>> output3,err3,ret3 = config.base.Configure.executeShellCommand('cd '+self.packageDir+' && '+pmake, timeout=6000, log = self.log) >>> self.logPrintBox('Running make install on '+self.PACKAGE+'; this may take several minutes') >>> self.installDirProvider.printSudoPasswordMessage(self.installSudo) >>> <<<<<<<< >>> >>> But then - a dirty build dir might break subsequent builds with the same PETSC_ARCH [usually triggered when configure options change] >>> >>> Satish >>> >>> On Wed, 29 Nov 2017, Blaise A Bourdin wrote: >>> >>>> Hi, >>>> >>>> I am trying to get BuildSystem to build pnetcdf (parallel netcdf automatically). >>>> The build process is very straightforward (configure; make; make install) >>>> Looking at other packages, I came up with the following for $PETSC_DIR/config/BuildSystem/config/packages/pnetcdf.py >>>> >>>> import config.package >>>> import os >>>> >>>> class Configure(config.package.GNUPackage): >>>> def __init__(self, framework): >>>> config.package.Package.__init__(self, framework) >>>> self.download = ['http://cucis.ece.northwestern.edu/projects/PnetCDF/Release/parallel-netcdf-…'] >>>> self.functions = ['ncmpi_create'] >>>> self.includes = ['pnetcdf.h'] >>>> self.liblist = [['libpnetcdf.a']] >>>> self.downloaddirnames = ['parallel-netcdf-1.8.1'] >>>> return >>>> >>>> def setupDependencies(self, framework): >>>> config.package.GNUPackage.setupDependencies(self, framework) >>>> self.mpi = framework.require('config.packages.MPI', self) >>>> self.deps = [self.mpi] >>>> return >>>> >>>> def formGNUConfigureArgs(self): >>>> args = config.package.GNUPackage.formGNUConfigureArgs(self) >>>> args.append('LIBS="'+self.compilers.LIBS+'"') >>>> return args >>>> >>>> >>>> Looking at configure.log, it looks like BuildSystem does a make clean between configure and make >>>> Unfortunately, there must be something wrong with the parallel-netcdf makefile, as make clean erases some of the files generated by pkgconfig (?), so that make install later fails... >>>> >>>> Is there an easy way to skip the 'make clean' step? >>>> >>>> Blaise >>>> >>>> >>>> >>>> >>> >> >> -- Department of Mathematics and Center for Computation & Technology Louisiana State University, Baton Rouge, LA 70803, USA Tel. +1 (225) 578 1612, Fax +1 (225) 578 4276 http://www.math.lsu.edu/~bourdin

1 0

Re: [petsc-dev] BuildSystem: how to prevent 'make clean' before 'make'
by Satish Balay 29 Nov '17

29 Nov '17

Sure - there are lots of assumptions in GNUPackage and CMAKEPackage [they assume most packages behave similarly wrt these types of builds] And one can also override these default routines provided. Some pacakges might provide a different 'clean' target. And some might prefer VPATH? builds? [i.e mkdir objdir && cd objdir && ../configure && make]. The CMAKE packages default to this mode. Perhaps we need to add this for gnupackages aswell.. Satish On Wed, 29 Nov 2017, Blaise A Bourdin wrote: > Thanks. > > I understand that it is not optimal. But OTOH, you are also assuming that make clean does what it is supposed to do… > > Blaise > > > > On Nov 29, 2017, at 5:29 PM, Satish Balay <balay(a)mcs.anl.gov> wrote: > > > > Right now there is no provision for this. The following can add it. > > > > > >>>>>>>>> > > $ git diff > > diff --git a/config/BuildSystem/config/package.py b/config/BuildSystem/config/package.py > > index 14de19502b..f9a2e68a25 100644 > > --- a/config/BuildSystem/config/package.py > > +++ b/config/BuildSystem/config/package.py > > @@ -80,6 +80,7 @@ class Package(config.base.Configure): > > self.makerulename = '' # some packages do too many things with the make stage; this allows a package to limit to, for example, just building the libraries > > self.installedpetsc = 0 > > self.installwithbatch = 0 # install the package even though configure is running in the initial batch mode; f2blaslapack and fblaslapack for example > > + self.skipcleanbeforebuild = 0 # skip running 'make clean' before starting a fresh build of a package > > return > > > > def __str__(self): > > @@ -1322,7 +1323,8 @@ class GNUPackage(Package): > > if self.parallelMake: pmake = self.make.make_jnp+' '+self.makerulename+' ' > > else: pmake = self.make.make+' '+self.makerulename+' ' > > > > - output2,err2,ret2 = config.base.Configure.executeShellCommand('cd '+self.packageDir+' && '+self.make.make+' clean', timeout=200, log = self.log) > > + if not self.skipcleanbeforebuild: > > + output2,err2,ret2 = config.base.Configure.executeShellCommand('cd '+self.packageDir+' && '+self.make.make+' clean', timeout=200, log = self.log) > > output3,err3,ret3 = config.base.Configure.executeShellCommand('cd '+self.packageDir+' && '+pmake, timeout=6000, log = self.log) > > self.logPrintBox('Running make install on '+self.PACKAGE+'; this may take several minutes') > > self.installDirProvider.printSudoPasswordMessage(self.installSudo) > > <<<<<<<< > > > > But then - a dirty build dir might break subsequent builds with the same PETSC_ARCH [usually triggered when configure options change] > > > > Satish > > > > On Wed, 29 Nov 2017, Blaise A Bourdin wrote: > > > >> Hi, > >> > >> I am trying to get BuildSystem to build pnetcdf (parallel netcdf automatically). > >> The build process is very straightforward (configure; make; make install) > >> Looking at other packages, I came up with the following for $PETSC_DIR/config/BuildSystem/config/packages/pnetcdf.py > >> > >> import config.package > >> import os > >> > >> class Configure(config.package.GNUPackage): > >> def __init__(self, framework): > >> config.package.Package.__init__(self, framework) > >> self.download = ['http://cucis.ece.northwestern.edu/projects/PnetCDF/Release/parallel-netcdf-…'] > >> self.functions = ['ncmpi_create'] > >> self.includes = ['pnetcdf.h'] > >> self.liblist = [['libpnetcdf.a']] > >> self.downloaddirnames = ['parallel-netcdf-1.8.1'] > >> return > >> > >> def setupDependencies(self, framework): > >> config.package.GNUPackage.setupDependencies(self, framework) > >> self.mpi = framework.require('config.packages.MPI', self) > >> self.deps = [self.mpi] > >> return > >> > >> def formGNUConfigureArgs(self): > >> args = config.package.GNUPackage.formGNUConfigureArgs(self) > >> args.append('LIBS="'+self.compilers.LIBS+'"') > >> return args > >> > >> > >> Looking at configure.log, it looks like BuildSystem does a make clean between configure and make > >> Unfortunately, there must be something wrong with the parallel-netcdf makefile, as make clean erases some of the files generated by pkgconfig (?), so that make install later fails... > >> > >> Is there an easy way to skip the 'make clean' step? > >> > >> Blaise > >> > >> > >> > >> > > > >

1 0

Re: [petsc-dev] BuildSystem: how to prevent 'make clean' before 'make'
by Blaise A Bourdin 29 Nov '17

29 Nov '17

Thanks. I understand that it is not optimal. But OTOH, you are also assuming that make clean does what it is supposed to do… Blaise > On Nov 29, 2017, at 5:29 PM, Satish Balay <balay(a)mcs.anl.gov> wrote: > > Right now there is no provision for this. The following can add it. > > >>>>>>>>> > $ git diff > diff --git a/config/BuildSystem/config/package.py b/config/BuildSystem/config/package.py > index 14de19502b..f9a2e68a25 100644 > --- a/config/BuildSystem/config/package.py > +++ b/config/BuildSystem/config/package.py > @@ -80,6 +80,7 @@ class Package(config.base.Configure): > self.makerulename = '' # some packages do too many things with the make stage; this allows a package to limit to, for example, just building the libraries > self.installedpetsc = 0 > self.installwithbatch = 0 # install the package even though configure is running in the initial batch mode; f2blaslapack and fblaslapack for example > + self.skipcleanbeforebuild = 0 # skip running 'make clean' before starting a fresh build of a package > return > > def __str__(self): > @@ -1322,7 +1323,8 @@ class GNUPackage(Package): > if self.parallelMake: pmake = self.make.make_jnp+' '+self.makerulename+' ' > else: pmake = self.make.make+' '+self.makerulename+' ' > > - output2,err2,ret2 = config.base.Configure.executeShellCommand('cd '+self.packageDir+' && '+self.make.make+' clean', timeout=200, log = self.log) > + if not self.skipcleanbeforebuild: > + output2,err2,ret2 = config.base.Configure.executeShellCommand('cd '+self.packageDir+' && '+self.make.make+' clean', timeout=200, log = self.log) > output3,err3,ret3 = config.base.Configure.executeShellCommand('cd '+self.packageDir+' && '+pmake, timeout=6000, log = self.log) > self.logPrintBox('Running make install on '+self.PACKAGE+'; this may take several minutes') > self.installDirProvider.printSudoPasswordMessage(self.installSudo) > <<<<<<<< > > But then - a dirty build dir might break subsequent builds with the same PETSC_ARCH [usually triggered when configure options change] > > Satish > > On Wed, 29 Nov 2017, Blaise A Bourdin wrote: > >> Hi, >> >> I am trying to get BuildSystem to build pnetcdf (parallel netcdf automatically). >> The build process is very straightforward (configure; make; make install) >> Looking at other packages, I came up with the following for $PETSC_DIR/config/BuildSystem/config/packages/pnetcdf.py >> >> import config.package >> import os >> >> class Configure(config.package.GNUPackage): >> def __init__(self, framework): >> config.package.Package.__init__(self, framework) >> self.download = ['http://cucis.ece.northwestern.edu/projects/PnetCDF/Release/parallel-netcdf-…'] >> self.functions = ['ncmpi_create'] >> self.includes = ['pnetcdf.h'] >> self.liblist = [['libpnetcdf.a']] >> self.downloaddirnames = ['parallel-netcdf-1.8.1'] >> return >> >> def setupDependencies(self, framework): >> config.package.GNUPackage.setupDependencies(self, framework) >> self.mpi = framework.require('config.packages.MPI', self) >> self.deps = [self.mpi] >> return >> >> def formGNUConfigureArgs(self): >> args = config.package.GNUPackage.formGNUConfigureArgs(self) >> args.append('LIBS="'+self.compilers.LIBS+'"') >> return args >> >> >> Looking at configure.log, it looks like BuildSystem does a make clean between configure and make >> Unfortunately, there must be something wrong with the parallel-netcdf makefile, as make clean erases some of the files generated by pkgconfig (?), so that make install later fails... >> >> Is there an easy way to skip the 'make clean' step? >> >> Blaise >> >> >> >> > -- Department of Mathematics and Center for Computation & Technology Louisiana State University, Baton Rouge, LA 70803, USA Tel. +1 (225) 578 1612, Fax +1 (225) 578 4276 http://www.math.lsu.edu/~bourdin

1 0

Re: [petsc-dev] BuildSystem: how to prevent 'make clean' before 'make'
by Satish Balay 29 Nov '17

29 Nov '17

Right now there is no provision for this. The following can add it. >>>>>>>> $ git diff diff --git a/config/BuildSystem/config/package.py b/config/BuildSystem/config/package.py index 14de19502b..f9a2e68a25 100644 --- a/config/BuildSystem/config/package.py +++ b/config/BuildSystem/config/package.py @@ -80,6 +80,7 @@ class Package(config.base.Configure): self.makerulename = '' # some packages do too many things with the make stage; this allows a package to limit to, for example, just building the libraries self.installedpetsc = 0 self.installwithbatch = 0 # install the package even though configure is running in the initial batch mode; f2blaslapack and fblaslapack for example + self.skipcleanbeforebuild = 0 # skip running 'make clean' before starting a fresh build of a package return def __str__(self): @@ -1322,7 +1323,8 @@ class GNUPackage(Package): if self.parallelMake: pmake = self.make.make_jnp+' '+self.makerulename+' ' else: pmake = self.make.make+' '+self.makerulename+' ' - output2,err2,ret2 = config.base.Configure.executeShellCommand('cd '+self.packageDir+' && '+self.make.make+' clean', timeout=200, log = self.log) + if not self.skipcleanbeforebuild: + output2,err2,ret2 = config.base.Configure.executeShellCommand('cd '+self.packageDir+' && '+self.make.make+' clean', timeout=200, log = self.log) output3,err3,ret3 = config.base.Configure.executeShellCommand('cd '+self.packageDir+' && '+pmake, timeout=6000, log = self.log) self.logPrintBox('Running make install on '+self.PACKAGE+'; this may take several minutes') self.installDirProvider.printSudoPasswordMessage(self.installSudo) <<<<<<<< But then - a dirty build dir might break subsequent builds with the same PETSC_ARCH [usually triggered when configure options change] Satish On Wed, 29 Nov 2017, Blaise A Bourdin wrote: > Hi, > > I am trying to get BuildSystem to build pnetcdf (parallel netcdf automatically). > The build process is very straightforward (configure; make; make install) > Looking at other packages, I came up with the following for $PETSC_DIR/config/BuildSystem/config/packages/pnetcdf.py > > import config.package > import os > > class Configure(config.package.GNUPackage): > def __init__(self, framework): > config.package.Package.__init__(self, framework) > self.download = ['http://cucis.ece.northwestern.edu/projects/PnetCDF/Release/parallel-netcdf-…'] > self.functions = ['ncmpi_create'] > self.includes = ['pnetcdf.h'] > self.liblist = [['libpnetcdf.a']] > self.downloaddirnames = ['parallel-netcdf-1.8.1'] > return > > def setupDependencies(self, framework): > config.package.GNUPackage.setupDependencies(self, framework) > self.mpi = framework.require('config.packages.MPI', self) > self.deps = [self.mpi] > return > > def formGNUConfigureArgs(self): > args = config.package.GNUPackage.formGNUConfigureArgs(self) > args.append('LIBS="'+self.compilers.LIBS+'"') > return args > > > Looking at configure.log, it looks like BuildSystem does a make clean between configure and make > Unfortunately, there must be something wrong with the parallel-netcdf makefile, as make clean erases some of the files generated by pkgconfig (?), so that make install later fails... > > Is there an easy way to skip the 'make clean' step? > > Blaise > > > >

1 0

BuildSystem: how to prevent 'make clean' before 'make'
by Blaise A Bourdin 29 Nov '17

29 Nov '17

Hi, I am trying to get BuildSystem to build pnetcdf (parallel netcdf automatically). The build process is very straightforward (configure; make; make install) Looking at other packages, I came up with the following for $PETSC_DIR/config/BuildSystem/config/packages/pnetcdf.py import config.package import os class Configure(config.package.GNUPackage): def __init__(self, framework): config.package.Package.__init__(self, framework) self.download = ['http://cucis.ece.northwestern.edu/projects/PnetCDF/Release/parallel-netcdf-…'] self.functions = ['ncmpi_create'] self.includes = ['pnetcdf.h'] self.liblist = [['libpnetcdf.a']] self.downloaddirnames = ['parallel-netcdf-1.8.1'] return def setupDependencies(self, framework): config.package.GNUPackage.setupDependencies(self, framework) self.mpi = framework.require('config.packages.MPI', self) self.deps = [self.mpi] return def formGNUConfigureArgs(self): args = config.package.GNUPackage.formGNUConfigureArgs(self) args.append('LIBS="'+self.compilers.LIBS+'"') return args Looking at configure.log, it looks like BuildSystem does a make clean between configure and make Unfortunately, there must be something wrong with the parallel-netcdf makefile, as make clean erases some of the files generated by pkgconfig (?), so that make install later fails... Is there an easy way to skip the 'make clean' step? Blaise -- Department of Mathematics and Center for Computation & Technology Louisiana State University, Baton Rouge, LA 70803, USA Tel. +1 (225) 578 1612, Fax +1 (225) 578 4276 http://www.math.lsu.edu/~bourdin

1 0

Re: [petsc-dev] remove temporary output with new test-harness
by Scott Kruger 29 Nov '17

29 Nov '17

On 11/29/17 10:25 AM, Matthew Knepley wrote: > On Wed, Nov 29, 2017 at 11:23 AM, Scott Kruger <kruger(a)txcorp.com > <mailto:[email protected]>> wrote: > > > > The generated scripts automatically run in a subdirectory to avoid > name conflicts. For example, runex1.sh creates a runex1 directory > relative > to its location and then runs the actual test in there. These > temporary directories are not removed automatically by the test > harness as it hasn't been a problem yet. > > > Okay, then it would be nice to give a list of files to be removed after > the test. Why? It's all in $PETSC_ARCH/tests which is meant to be ephemeral in the same way that $PETSC_ARCH/objs is. If it turns out that disk space is an issue (like it is for the executables themselves), then we can have the scripts remove that temporary directory after the test is run easily enough, but we still don't need to have all of the coding related to figuring out which files were generated (and tip of the hat to Jed who had the idea of running in the subdirectories to avoid name conflicts to begin with). Scott > > Thanks, > > Matt > > Scott > > > On 11/29/17 9:43 AM, Matthew Knepley wrote: > > On Wed, Nov 29, 2017 at 10:38 AM, Scott Kruger > <kruger(a)txcorp.com <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>>> wrote: > > rm $PETSC_ARCH/tests/<path_to_file>/<file> > > > I assume you really mean something else, specifically > related to the > generated test script, but there isn't enough information > to answer > that. > > Or more specifically, the test language was not written to > generate > scripts that have an `rm` command in them, so perhaps > explaining why > an extension would be a good idea.] > > > I think what Stefano means is the following; > > I write a test for the HDF5 Viewer. It creates a file called > "vector.dat". I want it removed at the end of the test. > > I think the answer is, the test directory is blown away, so as > long as the file is in that temp dir, you are fine. > > Thanks, > > Matt > > Scott > > > On 11/29/17 6:02 AM, Stefano Zampini wrote: > > How can I remove a file created by the executable I'm > testing > with the new test har > <https://maps.google.com/?q=with+the+new+test+har&entry=gmail&source=g>ness? > > -- Stefano > > > -- Tech-X Corporation kruger(a)txcorp.com > <mailto:[email protected]> <mailto:[email protected] > <mailto:[email protected]>> > 5621 Arapahoe Ave, Suite A Phone: (720) 974-1841 > <tel:%28720%29%20974-1841> > <tel:%28720%29%20974-1841> > Boulder, CO 80303 Fax: (303) 448-7756 > <tel:%28303%29%20448-7756> > <tel:%28303%29%20448-7756> > > > > > -- > 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 > > https://www.cse.buffalo.edu/~knepley/ > <https://www.cse.buffalo.edu/~knepley/> > <http://www.caam.rice.edu/~mk51/ <http://www.caam.rice.edu/~mk51/>> > > > -- > Tech-X Corporation kruger(a)txcorp.com <mailto:[email protected]> > 5621 Arapahoe Ave, Suite A Phone: (720) 974-1841 > <tel:%28720%29%20974-1841> > Boulder, CO 80303 Fax: (303) 448-7756 > <tel:%28303%29%20448-7756> > > > > > -- > 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 > > https://www.cse.buffalo.edu/~knepley/ <http://www.caam.rice.edu/~mk51/> -- Tech-X Corporation kruger(a)txcorp.com 5621 Arapahoe Ave, Suite A Phone: (720) 974-1841 Boulder, CO 80303 Fax: (303) 448-7756

1 0

Re: [petsc-dev] remove temporary output with new test-harness
by Matthew Knepley 29 Nov '17

29 Nov '17

On Wed, Nov 29, 2017 at 11:23 AM, Scott Kruger <kruger(a)txcorp.com> wrote: > > > The generated scripts automatically run in a subdirectory to avoid name > conflicts. For example, runex1.sh creates a runex1 directory relative > to its location and then runs the actual test in there. These temporary > directories are not removed automatically by the test harness as it hasn't > been a problem yet. > Okay, then it would be nice to give a list of files to be removed after the test. Thanks, Matt > Scott > > > On 11/29/17 9:43 AM, Matthew Knepley wrote: > >> On Wed, Nov 29, 2017 at 10:38 AM, Scott Kruger <kruger(a)txcorp.com >> <mailto:[email protected]>> wrote: >> >> rm $PETSC_ARCH/tests/<path_to_file>/<file> >> >> >> I assume you really mean something else, specifically related to the >> generated test script, but there isn't enough information to answer >> that. >> >> Or more specifically, the test language was not written to generate >> scripts that have an `rm` command in them, so perhaps explaining why >> an extension would be a good idea.] >> >> >> I think what Stefano means is the following; >> >> I write a test for the HDF5 Viewer. It creates a file called >> "vector.dat". I want it removed at the end of the test. >> >> I think the answer is, the test directory is blown away, so as long as >> the file is in that temp dir, you are fine. >> >> Thanks, >> >> Matt >> >> Scott >> >> >> On 11/29/17 6:02 AM, Stefano Zampini wrote: >> >> How can I remove a file created by the executable I'm testing >> with the new test har >> <https://maps.google.com/?q=with+the+new+test+har&entry=gmail&source=g> >> ness? >> >> -- Stefano >> >> >> -- Tech-X Corporation kruger(a)txcorp.com <mailto:[email protected] >> > >> 5621 Arapahoe Ave, Suite A Phone: (720) 974-1841 >> <tel:%28720%29%20974-1841> >> Boulder, CO 80303 Fax: (303) 448-7756 >> <tel:%28303%29%20448-7756> >> >> >> >> >> -- >> 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 >> >> https://www.cse.buffalo.edu/~knepley/ <http://www.caam.rice.edu/~mk51/> >> > > -- > Tech-X Corporation kruger(a)txcorp.com > 5621 Arapahoe Ave, Suite A Phone: (720) 974-1841 > Boulder, CO 80303 Fax: (303) 448-7756 > -- 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 https://www.cse.buffalo.edu/~knepley/ <http://www.caam.rice.edu/~mk51/>

1 0

Re: [petsc-dev] remove temporary output with new test-harness
by Scott Kruger 29 Nov '17

29 Nov '17

The generated scripts automatically run in a subdirectory to avoid name conflicts. For example, runex1.sh creates a runex1 directory relative to its location and then runs the actual test in there. These temporary directories are not removed automatically by the test harness as it hasn't been a problem yet. Scott On 11/29/17 9:43 AM, Matthew Knepley wrote: > On Wed, Nov 29, 2017 at 10:38 AM, Scott Kruger <kruger(a)txcorp.com > <mailto:[email protected]>> wrote: > > rm $PETSC_ARCH/tests/<path_to_file>/<file> > > > I assume you really mean something else, specifically related to the > generated test script, but there isn't enough information to answer > that. > > Or more specifically, the test language was not written to generate > scripts that have an `rm` command in them, so perhaps explaining why > an extension would be a good idea.] > > > I think what Stefano means is the following; > > I write a test for the HDF5 Viewer. It creates a file called > "vector.dat". I want it removed at the end of the test. > > I think the answer is, the test directory is blown away, so as long as > the file is in that temp dir, you are fine. > > Thanks, > > Matt > > Scott > > > On 11/29/17 6:02 AM, Stefano Zampini wrote: > > How can I remove a file created by the executable I'm testing > with the new test harness? > > -- > Stefano > > > -- > Tech-X Corporation kruger(a)txcorp.com <mailto:[email protected]> > 5621 Arapahoe Ave, Suite A Phone: (720) 974-1841 > <tel:%28720%29%20974-1841> > Boulder, CO 80303 Fax: (303) 448-7756 > <tel:%28303%29%20448-7756> > > > > > -- > 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 > > https://www.cse.buffalo.edu/~knepley/ <http://www.caam.rice.edu/~mk51/> -- Tech-X Corporation kruger(a)txcorp.com 5621 Arapahoe Ave, Suite A Phone: (720) 974-1841 Boulder, CO 80303 Fax: (303) 448-7756

1 0

Re: [petsc-dev] remove temporary output with new test-harness
by Matthew Knepley 29 Nov '17

29 Nov '17

On Wed, Nov 29, 2017 at 10:38 AM, Scott Kruger <kruger(a)txcorp.com> wrote: > rm $PETSC_ARCH/tests/<path_to_file>/<file> > > > I assume you really mean something else, specifically related to the > generated test script, but there isn't enough information to answer that. > > Or more specifically, the test language was not written to generate > scripts that have an `rm` command in them, so perhaps explaining why an > extension would be a good idea.] > I think what Stefano means is the following; I write a test for the HDF5 Viewer. It creates a file called "vector.dat". I want it removed at the end of the test. I think the answer is, the test directory is blown away, so as long as the file is in that temp dir, you are fine. Thanks, Matt > Scott > > > On 11/29/17 6:02 AM, Stefano Zampini wrote: > >> How can I remove a file created by the executable I'm testing with the >> new test harness? >> >> -- >> Stefano >> > > -- > Tech-X Corporation kruger(a)txcorp.com > 5621 Arapahoe Ave, Suite A Phone: (720) 974-1841 > Boulder, CO 80303 Fax: (303) 448-7756 > -- 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 https://www.cse.buffalo.edu/~knepley/ <http://www.caam.rice.edu/~mk51/>

1 0

Re: [petsc-dev] remove temporary output with new test-harness
by Scott Kruger 29 Nov '17

29 Nov '17

rm $PETSC_ARCH/tests/<path_to_file>/<file> I assume you really mean something else, specifically related to the generated test script, but there isn't enough information to answer that. Or more specifically, the test language was not written to generate scripts that have an `rm` command in them, so perhaps explaining why an extension would be a good idea. Scott On 11/29/17 6:02 AM, Stefano Zampini wrote: > How can I remove a file created by the executable I'm testing with the > new test harness? > > -- > Stefano -- Tech-X Corporation kruger(a)txcorp.com 5621 Arapahoe Ave, Suite A Phone: (720) 974-1841 Boulder, CO 80303 Fax: (303) 448-7756

1 0