MPICH Status and ToDo Items

This page contains links to the various MPICH status and todo items
Results from test suites (using old test harness)
This shows what does and does not work, on various platforms, and for many test suites.

To modify these tests, edit /home/MPI/nightly/basictests and /home/MPI/nightly/updatesum.

Special tests
This shows the results of special tests, such as configuring, building, and testing with memory tracing (--enable-g=mem), logging, or shared libraries, on one system (usually Linux).
See Running the special tests for information on running or modifying these tests. It is a good idea to add tests to this file in response to user bug reports to ensure that fixed bugs stay fixed.
Coverage analysis
This shows the results of coverage analysis (what code has not been executed) after running the test suites. The goal is for every line of code not associated with handling internal errors to be executed by the test suites. The coverage tool provides a way to mark error handling code so that the coverage output can identify the lines of code that need testing.

DeviceCombined Text FileAnnotated Source Files
ch3:nemesis coverage.txt Index

Output from the coverage tests themselves (e.g., the configure, make, and run output) may be available in /mcs/mpich/nightly/coverage/-device-/cov-logfile.txt, but only if there was a problem in the build.
To modify these checks, edit /home/MPI/nightly/getcoverage. To add new checks, add additional runs of the getcoverage test to a cron entry. For example, the crontab line for the ch3:ssm test is

49 06 * * 4 /home/MPI/nightly/getcoverage -updateweb -quiet -device=ch3:ssm
Results from the MPICH test suite
This shows more diverse tests but run against only the MPICH test suite. As an added benefit, these results package up all relevant generated files, include config.log, from each configured subdirectory.

These tests make use of the experimental "buildsys" scripts. The local tests are controlled by scripts in /home/MPI/testing/mpich2/scripts which in turn are managed by the runlist script from buildsys. For example, the current set of tests on smash are run with a crontab entry of

21 22 * * * /home/gropp/projects/software/buildsys/src/runlist \
          -dir /home/MPI/testing/mpich2/runstates/smash \
          -joblist /home/MPI/testing/mpich2/scripts/smash.sh -endtime 5
(The command has been split across multiple lines to improve readability)

The scripts in buildsys may also be used to run these tests on remote systems and to move and install the results into /home/MPI/testing/mpich2. More information will be available.

Tests of Configure Options
This shows the results of configuring, building, and installing with a variety of configure options, on one system (usually Linux).
See Running tests of configure options for information on running or modifying these tests. It is a good idea to add tests to this file in response to user bug reports to ensure that fixed bugs stay fixed.
Problems reported by the style checker
This shows the output of codingcheck -conf=mpich2 and flags potential and real problems in the source code. See Running the coding checks for information on running these checks, including running them on particular files or directories.
Problems reported by the error message extractor
These show messages that may include English-language text. Such messages break the internationalization support in MPICH.
Non-conforming Global Symbols
These show the names and file names for any global symbols that do not conform to the established naming rules (unknown or inappropriate prefix to the routine or global variable) or are uninitialized global variables (so-called "common" symbols).
To modify this check, edit /home/MPI/nightly/checkglobs.