[petsc-dev] Improving nightly builds for maint

[Satish Balay]

On Wed, 18 Oct 2017, Lisandro Dalcin wrote:

> I opened this PR: https://bitbucket.org/petsc/petsc/pull-requests/
> 
> However, this is unlikely to fix these failures:
> 
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/10/15/examples_maint_arch-linux-pkgs-valgrind_el6.log
> 
> Satish, can we find a way to disable these tests when running under valgrind?

src/dm/examples/tutorials/ex15.c:      requires: define(PETSC_HAVE_MPIIO) !define(PETSC_HAVE_LIBMSMPI)

One way is to improve the test harness to support something like:

requires: !define(PETSC_ARCH="arch-linux-pkgs-valgrind")

Alternate is to remove/increase the timout. It doesn't work for some
builds anyway [esp valgrind runs]

This feature relies on sending 'kill' message to the process it
started - i.e mpiexec. But some mpiexecs when killed - don't kill the
child processes cleanly]

$ git diff |cat
diff --git a/bin/maint/buildtest b/bin/maint/buildtest
index 31b5a3a028..e4bbf96db8 100755
--- a/bin/maint/buildtest
+++ b/bin/maint/buildtest
@@ -104,7 +104,7 @@ if ( $? ) then
 else
   set VALGRIND=`echo MPIEXEC="${PETSC_DIR}/bin/petscmpiexec -valgrind"`
   setenv PETSCVALGRIND_OPTIONS "--suppressions=${PETSC_DIR}/bin/maint/petsc-val.supp"
-  set TIMEOUT=720
+  set TIMEOUT=7200
 endif


Satish