Difference between revisions of "Nightly Tests"

From Mpich
Jump to: navigation, search
 
Line 4: Line 4:
 
* [http://www.mpich.org/static/cron/specialtests Special Tests] - This shows the results of special tests, such as configuring, building, and testing with memory tracing (<code>--enable-g=mem</code>), logging, or shared libraries, on one system (usually Linux).  See [[Testing_MPICH#Running_the_Special_Tests|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.
 
* [http://www.mpich.org/static/cron/specialtests Special Tests] - This shows the results of special tests, such as configuring, building, and testing with memory tracing (<code>--enable-g=mem</code>), logging, or shared libraries, on one system (usually Linux).  See [[Testing_MPICH#Running_the_Special_Tests|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.
 
* [http://www.mpich.org/static/cron/errors/testoptions.htm 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 [[Testing_MPICH#Running_the_configure_tests|Running the configure 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.
 
* [http://www.mpich.org/static/cron/errors/testoptions.htm 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 [[Testing_MPICH#Running_the_configure_tests|Running the configure 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.
* [[Jenkins]] is used to run a number of test configurations on every push to certain Git repositories.  See that page for more information.
 
  
 
We are currently missing the following test result pages from the old website:
 
We are currently missing the following test result pages from the old website:

Latest revision as of 20:32, 21 June 2013

Each night we run an extensive series of tests on a set of (platform,configuration) pairs. These results can be found on the summary page.

Other testing:

  • 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.
  • 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 the configure 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.

We are currently missing the following test result pages from the old website:

  • 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.


Compilers Tested Regularly: GNU, Intel, PGI, Absoft

(SUN compilers, as well as other vendor compilers, such as the IBM XL compilers, are not included in our nightly tests but are tested on an occasional basis, depending mostly on the availability of a test platform.)


See Also