The "mpich2 test suite" refers to the new test harness Bill wrote that can test across 2 machines. It's probably not needed since your new test script can do that. The special tests used to be run manually via /home/MPI/nightly/specialtest. I ran them last on Jan 25th. The getcoverage tests should run 3 times a week based on the foll. cron job on triumph. I am not sure why their output is not visible. 49 06 * * 6 /home/MPI/nightly/getcoverage -updateweb -quiet 49 06 * * 4 /home/MPI/nightly/getcoverage -updateweb -quiet -device=ch3:ssm 49 06 * * 2 /home/MPI/nightly/getcoverage -updateweb -quiet -device=ch3:nemesis I see the line "To include the results of that test in the display on this page, edit todo.txt in the mpich2-web CVS module." under Coverage analysis. Not sure what that means. I believe the style checker, error message extractor, and non-conforming global symbols also used to be run manually, but they haven't been run in a while. Rajeev
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dave Goodell Sent: Wednesday, January 30, 2008 5:46 PM To: [email protected] Cc: Dave Goodell Subject: Re: [mpich2-core] other automated testing
On Jan 30, 2008, at 5:22 PM, Pavan Balaji wrote:
* mpich2 test suite: http://www.mcs.anl.gov/research/projects/ mpich2/testing/ * special tests * configure options tests
These are already present in the new script.
That's not really true. For example, we aren't running the mpich2 test suite against OS X (darwin) or against the portland group compiler right now. Also, the "mpich2 test suite" referenced above also has links to configure logs and other helpful debugging info. This functionality is not currently present in the new nightly test harness.
* code coverage analysis * style checker problems * error message extractor problems * non-conforming global symbols * list of FIXMEs
What we have for these is OK for now. They can continue to run on schwinn, etc., since these don't have any problems running on shared machines.
I'm not sure that you understood me. These tests may still be running, but their output is going nowhere right now. There's no way to see the results of any of these tests, so we're just as well off as if we weren't even running them right now.
The plan is to do the most required functionality in the new script for now and get undergrad interns to port the remaining tests over. If something is straight-forward, let's add it and leave everything else for the interns.
I wasn't proposing rolling them into the new test scripts, just to modify them such that the results are displayed on the new website.
-Dave