not to build to not be added to the ALL_COMPONENTS list and therefore
not distributed in a tarball
* add some of the contrib/ stuff to the dist tarball (the stuff to
make binary packages and the "--with-platform" files)
This commit was SVN r6955.
of flags to configure. Now don't need to specify the contrib/platform
part of the path if you don't want to
* Add "optimized" platform setting that will undo all the performance-
affecting things that a developer build sets up.
This commit was SVN r6946.
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.
- If -d is specified, it assumes that the next parameter is
a valid subdirectory path.
- If -f is specified, then it generates the statistic for tehse
files. Each -f is pared with one file only. So multiple files require
multiple -f's
- -p "%" can be given to spew out the files which have a coverage
below this percentage
This commit was SVN r5426.
- Added some minor changes to make sure that files are not reported more than once
- Print average coverage statistics
- TODO
- Add support to get statistics for a particular file
This commit was SVN r5418.
Currently, the fllowing have been implemented:
- the directory/ies are specified in a file "dir_list"
- gcov is run on all the files which were touched
- 4 files are generated as output
- touched_files (those files which generated .da files)
- untouched_files (those which did nto generate .da files)
- coverage_stats.txt (index, filename, dirname, %coverage)
- zero_coverage.txt (same as above, but for those with 0% coverage)
- Currently, the statistics are generated only for *.c and *.cc files.
gcov does infact generate the numbers for header files as and when
they are used. So, for every inclusion of a header file, a seperate
.da for that header file is created. To get the numbers out for
the header files, we need to aggregate all the stats for the header
files manually. This is yet to be done
Things to do;
- Generate the statistics for the header files
- Command line parsing instead of reading from "dir_list"
- Input a % and list all the files which were covered less
than that percentage
This commit was SVN r5415.
