Open MPI logo

MTT Devel Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all MTT Users mailing list

Subject: Re: [MTT users] How to test just one MPI version?
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2008-05-13 16:37:01


My entire Cisco setup is completely automated; I have a schedule of
what I run every night, etc. It's kinda complex and somewhat kludgey,
but it works. :-\

Have a look in the ompi-tests SVN repository:

        trunk/cisco/mtt/

I run the "nightly.pl" script via cron on a cluster that is managed by
SLURM.

On May 13, 2008, at 4:29 PM, Rafael Folco wrote:

>
> Nice. Thanks.
>
>
> On Tue, 2008-05-13 at 16:20 -0400, Jeff Squyres wrote:
>> FWIW, I heavily use the --section and --[no]-<phase> command line
>> arguments in my automated Cisco MTT setup.
>>
>>
>> On May 13, 2008, at 4:12 PM, Ethan Mallove wrote:
>>
>>> On Tue, May/13/2008 02:54:46PM, Rafael Folco wrote:
>>>> Hi,
>>>>
>>>> I appreciate if anyone can give me some help.
>>>>
>>>> How to run MTT tests just against one specific MPI version ? It is
>>>> running against all MPI versions: ompi-nightly-v1.1, ompi-nightly-
>>>> trunk,
>>>> and ompi-nightly-v1.2.
>>>>
>>>> I've already tried to use the following configurations. Did I miss
>>>> anything ?
>>>>
>>>> MPI Get phase:
>>>> ==============
>>>> [MPI get: OpenMPI-1.2.5]
>>>> mpi_details = Open MPI 1.2.5
>>>> module = AlreadyInstalled
>>>>
>>>>
>>>> MPI Install phase:
>>>> ==================
>>>> [MPI install: OpenMPI-1.2.5]
>>>> module = Analyze::OMPI
>>>>
>>>>
>>>> Test Build phase:
>>>> =================
>>>> skip_mpi_get = ompi-nightly-v1.1, ompi-nightly-trunk, ompi-nightly-
>>>> v1.2
>>>> skip_mpi_install = ompi-nightly-v1.1, ompi-nightly-trunk,
>>>> ompi-nightly-v1.2
>>>>
>>>>
>>>> Command line:
>>>> =============
>>>>
>>>> # client/mtt -d --force -f samples/ompi-core.ini
>>>> alreadyinstalled_dir=/usr/lib64/openmpi/1.2.5-gcc
>>>>
>>>>
>>>> Thanks in advance.
>>>
>>>
>>> You can skip sections in the INI file by inserting
>>> a text string (e.g., "skip") into the section names. E.g.,
>>>
>>> [SKIP MPI get: ompi-nightly-v1.1]
>>> ...
>>> [SKIP MPI get: ompi-nightly-v1.2]
>>> ...
>>> [SKIP MPI get: ompi-nightly-trunk]
>>> ...
>>>
>>> There's also a "--[no]-section" option if you'd rather leave your
>>> INI file clean. E.g.,
>>>
>>> $ client/mtt -d --force -f samples/ompi-core.ini \
>>> alreadyinstalled_dir=/usr/lib64/openmpi/1.2.5-gcc \
>>> --section "OpenMPI-1.2.5 trivial ibm intel mpicxx"
>>>
>>> MTT will do a pattern match on each INI section, and execute
>>> only the sections listed in your --section argument. In the
>>> above example, sections matching either "OpenMPI-1.2.5",
>>> "trivial", "ibm", "intel", or "mpicxx" will be run.
>>>
>>> -Ethan
>>>
>>>>
>>>> --
>>>> Rafael Folco
>>>> OpenHPC / Brazil Test Lead
>>>> IBM Linux Technology Center
>>>> E-Mail: rfolco_at_[hidden]
>>>>
>>>> _______________________________________________
>>>> mtt-users mailing list
>>>> mtt-users_at_[hidden]
>>>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>>> _______________________________________________
>>> mtt-users mailing list
>>> mtt-users_at_[hidden]
>>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>>
>>
>
> --
> Rafael Folco
> OpenHPC / Brazil Test Lead
> IBM Linux Technology Center
> E-Mail: rfolco_at_[hidden]
>
> _______________________________________________
> mtt-users mailing list
> mtt-users_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users

-- 
Jeff Squyres
Cisco Systems