it plainly obvious
- Unlink source files when done with them
- Close the perl file handles after writing test source files so that
stale NFS handles aren't left around when building on networked file
systems (duh!)
This commit was SVN r6912.
Nightly build of trunk and test-suite (PMB and mpich-testsuite)
as defined in build-HOSTNAME.txt
Uses build_tarball.pl (which creates ompi-out-VERSION.txt)
Uses build_tests.pl (which uses ompi-out-VERSION.txt and creates
ompi-tests-out-TEST_VERSION.txt)
Then should qsub the all created combinations of MPI-installations
build_tests.pl:
- Updated to take package_dir; the test-suites subdirectory to
configure -- currently PMB and mpich-testsuite
This commit was SVN r6604.
which should ease building:
--no_check: do not make check -- may not be interesting,
we still want to do further testing.
--install-dir: On clusters, tmp may not be shared,
still, one may not want to use --scrdir
build_tests.pl is taken form build_tarball.pl.
Actually all subs are the same (is it possible to have
a module that is included by both?)
It configures and compiles two tests (now PMB and the
mpichtests) and installs them for later execution.
This takes a (misnamed) input --outfile, the output
file of build_tarball.pl, so the test-files are
compiled for every combination of OpenMPI-compilations.
The following ompi_crontab.sh script the pulls all
combinations of MPI-tests compiled and qsubs them.
This commit was SVN r5579.
compiled libraries and compononents. Still to do:
- check components
- send mail if it finds anything wrong
- check multiple installation directories (?)
This commit was SVN r2811.
it's not going to the testing@open-mpi.org list (correspondingly
remove the subject prefix from the testing@open-mpi.org list config)
- re-add a missing unlink() that was causing problems.
This commit was SVN r2517.
per-host / per-config basis because some people (like me!) have a
common scratch root on NFS for multiple machines (e.g., share a
downloads directory).
This commit was SVN r2410.
- ensure to only keep a finite number of old build roots around (build
roots are kept if you --leave-install or if there was a build error
-- so you can go look and see what the error was, etc.)
- check to see if the last run already built the same tarball version
that's currently on the nightly build website -- if we've already
tested it, there's no point in compiling / testing it again. This
should cut down on the volume of [repetitive] testing e-mails to the
mailing list.
- add --force parameter to override ^^ -- *always* compile/test,
regardless of whether we have tested that version before.
- fix logic removing old tarballs
This commit was SVN r2405.
