Thanks! I was trying to look for this email, but couldn't find it. We'll need some discussion about the non-implementation specific job compilation/execution options, though. -- Pavan On 10/05/2007 01:38 PM, William Gropp wrote:
On Oct 5, 2007, at 11:44 AM, Pavan Balaji wrote:
Actually, there are some action items left. For example, some of the paths are hard-coded in there.
-- Pavan
Here's a list I found in my mail from Pavan. Are there any others? Note that (5) needs to be modified for systems that don't have compilation scripts; however, I agree that eliminating implementation-specific options is a good goal (but note also that mpiexec isn't universally available :( ).
Bill
Just making a note of the fixes that I think are necessary for the Intel test suite for your comments. I can make these changes myself once my current urgent task list is done:
1. Add a few testlists with descriptive names (e.g., complete.list, io.list, c.list, fortran.list) and get rid of all the current testlists that are available, but with very non-descriptive names.
2. Decouple compilation and testing. Currently "make" runs the tests too.
3. Add the default installation path to /usr/local or something. It currently points to one of the MCS machine directories. The user can, of course, specify any other directory with prefix.
4. Make it easier to run individual tests. I could not get this working as yet, without creating a separate testlist and modifying the Makefile.
5. Get rid of the --with-mpich2 and equivalent options. The test suite should not depend on any supported MPI implementation. It should just use "mpicc" for compilation. We can have some option for the job launcher, e.g., mpiexec, mpirun, etc.
6. Allow user to specify a timeout value for each test. If nothing is specified, the default timeout is used.
-- Pavan Balaji http://www.mcs.anl.gov/~balaji