Open MPI logo

MTT Devel Mailing List Archives

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

From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2007-06-05 12:37:20


On Jun 5, 2007, at 12:25 PM, Shai Venter wrote:

> I must say, you guys are in the 'zero response time' zone !
> Great! I appreciate it a lot.

Glad to help.

> One major Q : When mtt is launched on 'host116' for example, does the
> scratch area for the ompi installation should be a shared directory
> (like a network folder) acessible to all other hosts in the setup, or
> can it be on the local 'host116' which is running the mtt?

MTT currently assumes that the scratch area is shared across all
nodes where that instance of MTT is running (e.g., a network share
folder such as NFS). We have some trac tickets open to support non-
uniform-shared setups (e.g., heterogeneous architectures where a
single shared folder will not be sufficient), but no work has
progressed on that front yet.

> What I'm trying to figure out is, how does mpi jobs run on the remote
> hosts in my setup if there's no ompi installation there?
> Or maybe I didn't fully understand the greatness of how mtt works
> behind
> the curtains.

Hah! :-)

MTT doesn't transparently install MPI on multiple machines -- it
installs it once in the scratch directory and then assumes that the
same scratch tree is available on all nodes.

>
> Once more - Thank you
>
> Regards,
> Shai Venter.
> -----Original Message-----
> From: mtt-users-bounces_at_[hidden]
> [mailto:mtt-users-bounces_at_[hidden]] On Behalf Of
> mtt-users-request_at_[hidden]
> Sent: Tuesday, June 05, 2007 7:00 PM
> To: mtt-users_at_[hidden]
> Subject: mtt-users Digest, Vol 16, Issue 2
>
> Send mtt-users mailing list submissions to
> mtt-users_at_[hidden]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
> or, via email, send a message with subject or body 'help' to
> mtt-users-request_at_[hidden]
>
> You can reach the person managing the list at
> mtt-users-owner_at_[hidden]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of mtt-users digest..."
>
>
> Today's Topics:
>
> 1. Re: mtt-users Digest, Vol 15, Issue 5 (Jeff Squyres)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 5 Jun 2007 08:13:14 -0400
> From: Jeff Squyres <jsquyres_at_[hidden]>
> Subject: Re: [MTT users] mtt-users Digest, Vol 15, Issue 5
> To: General user list for the MPI Testing Tool
> <mtt-users_at_[hidden]>
> Message-ID: <20AAAFA1-E868-4DD0-B7C3-D992D21674E6_at_[hidden]>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> Great; let us know how else we can help getting you setup on MTT.
>
>
> On Jun 3, 2007, at 3:06 AM, Shai Venter wrote:
>
>> Hard-coded indeed it was. One more hurdle overcomed.
>> Thanks and good day.
>>
>> Regards,
>> Shai Venter.
>> -----Original Message-----
>> From: mtt-users-bounces_at_[hidden]
>> [mailto:mtt-users-bounces_at_[hidden]] On Behalf Of
>> mtt-users-request_at_[hidden]
>> Sent: Monday, May 21, 2007 6:44 PM
>> To: mtt-users_at_[hidden]
>> Subject: mtt-users Digest, Vol 15, Issue 5
>>
>> Send mtt-users mailing list submissions to
>> mtt-users_at_[hidden]
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>> or, via email, send a message with subject or body 'help' to
>> mtt-users-request_at_[hidden]
>>
>> You can reach the person managing the list at
>> mtt-users-owner_at_[hidden]
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of mtt-users digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Re: mtt test build for IMB-MPI1 fails, (Jeff Squyres)
>> 2. Re: mtt test build for IMB-MPI1 fails, (Ethan Mallove)
>> 3. Re: mtt test build for IMB-MPI1 fails, (Jeff Squyres)
>>
>>
>> ---------------------------------------------------------------------
>> -
>>
>> Message: 1
>> Date: Mon, 21 May 2007 06:32:53 -0700
>> From: Jeff Squyres <jsquyres_at_[hidden]>
>> Subject: Re: [MTT users] mtt test build for IMB-MPI1 fails,
>> To: General user list for the MPI Testing Tool
>> <mtt-users_at_[hidden]>
>> Message-ID: <72EBB18F-34BC-4635-A012-A122E925B99C_at_[hidden]>
>> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>>
>> It looks like your makefile is hard-coded to use /bin/mpicc, which
>> will always be wrong for MTT. This specifies an absolute location
>> for mpicc, and does not allow the $PATH to be used.
>>
>> Where are you getting your copy of IMB from?
>>
>> The IMB 2.3 that is in the ompi_tests repository has a make_openmpi
>> that contains the following line:
>>
>> CC = mpicc
>>
>> Hence, "mpicc" is used, and therefore $PATH is used to find it.
>>
>> Can you modify your makefile this way?
>>
>>
>> On May 20, 2007, at 12:31 AM, Shai Venter wrote:
>>
>>> Hello again Mr Squyres.
>>>
>>> I am most greatfull for your answers to my questions (2).
>>> Actualy, they are both linked to the same issue: my mtt run fails
>>> in the
>>> test build phase for IMB-MPI1.
>>>
>>> It seems that the make file cannot find the mpicc to compile.
>>> It searches for it in a default path (/bin/mpicc) but it's
>>> Usless scince this path is irrelevant.
>>>
>>> I've tried this code:
>>>
>>> module = Shell
>>> shell_build_command = <<EOT
>>> cd src
>>> make clean IMB-MPI1
>>> EOT
>>>
>>> But still the same error.
>>>
>>>
>>> Lets have a look at the output of build error:
>>>
>>> --------------------------------------------------------------------
>>> -
>
>>> -
>>
>>> --
>>> ----
>>> sw169:/usr/local/mtt # cat
>>> scratch/installs/K5a_/tests/imb-2.3/test_built.ini
>>> # This file was automatically created by Config/IniFiles.pm. Any
>>> changes made manually are likely to be lost!
>>> [test_built]
>>> mpi_version=1.2.2
>>> full_section_name=test build: imb-2.3
>>> result_stdout= <<EOT
>>> /bin/rm -f *.o *~ PI* core IMB-IO IMB-EXT IMB-MPI1 exe_io exe_ext
>>> exe_mpi1
>>> touch exe_mpi1 *.c; rm -rf exe_io exe_ext
>>> make MPI1 CPP=MPI1
>>> make[1]: Entering directory
>>> `/usr/local/mtt/scratch/installs/K5a_/tests/imb-2.3/IMB-2.3/src'
>>> /bin/mpicc -I/include -DMPI1 -O -g -c IMB.c
>>> make[1]: /bin/mpicc: Command not found
>>> make[1]: *** [IMB.o] Error 127
>>> make[1]: Leaving directory
>>> `/usr/local/mtt/scratch/installs/K5a_/tests/imb-2.3/IMB-2.3/src'
>>> make: *** [IMB-MPI1] Error 2
>>> EOT
>>> refcount=0
>>> result_message= <<EOT
>>> Shell: command failed "cd src
>>> make clean IMB-MPI1"
>>> EOT
>>> mpi_install_simple_section_name=gcc
>>> test_result=0
>>> exit_status=512
>>> mpi_get_simple_section_name=ompiv1.2
>>> simple_section_name=imb-2.3
>>> srcdir=/usr/local/mtt/scratch/installs/K5a_/tests/imb-2.3/IMB-2.3
>>> start_timestamp=1179655379
>>> test_get_simple_section_name=imb
>>>
>>> --------------------------------------------------------------------
>>> -
>
>>> -
>>
>>> --
>>> ----
>>>
>>>
>>>
>>> I feel that it has some thing to do with setting up an enviroment
>>> path
>>> variable to the mpi bin dir. I could provide it as an argument to
>>> the
>>> "make" file, but I cannot know in advance where mtt creates/
>>> installs the
>>> bin dir for each and every mpi installtion.
>>>
>>> Hopefully, you'll have an insight on this.
>>>
>>> Regards,
>>> Shai Venter.
>>>
>>>
>>>
>>> -----Original Message-----
>>>
>>> Today's Topics:
>>>
>>> 1. MTT with ompiv1.2 (Shai Venter)
>>> 2. Re: MTT with ompiv1.2 (Jeff Squyres)
>>> 3. How can I know the path to mpicc ? (Shai Venter)
>>> 4. Re: How can I know the path to mpicc ? (Jeff Squyres)
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>
>>> -
>>>
>>> Message: 1
>>> Date: Thu, 17 May 2007 16:50:14 +0300
>>> From: "Shai Venter" <venters_at_[hidden]>
>>> Subject: [MTT users] MTT with ompiv1.2
>>> To: <mtt-users_at_[hidden]>
>>> Message-ID:
>>> <6C2C79E72C305246B504CBA17B5500C901825449_at_[hidden]>
>>> Content-Type: text/plain; charset="us-ascii"
>>>
>>> Hi There !
>>> Regarding the .ini file:
>>> Using setenv in the MPI Get: phase, should set me an Enviroment var,
>>> right ?!
>>> So if , let say, I write setenv = MPIHOMEDIR &shell("pwd")/install
>>> should set MPIHOMEDIR to some path as mentioned.
>>> Well, I checked for my MPIHOMEDIR in the env ( cmd line: env |
>>> grep
>>> MPI ) and got nothing.
>>> What did I not do right?
>>>
>>>
>>>
>>> Shai Venter
>>> Q.A
>>> Mellanox Technologies, Ltd.
>>> www.mellanox.com
>>> +972 (0)4 9097200 ext. 252
>>> +972 (0)50 2888637
>>>
>>> Date: Thu, 17 May 2007 07:04:22 -0700
>>> From: Jeff Squyres <jsquyres_at_[hidden]>
>>> Subject: Re: [MTT users] MTT with ompiv1.2
>>> To: General user list for the MPI Testing Tool
>>> <mtt-users_at_[hidden]>
>>> Message-ID: <4D863C26-EE6F-4F3E-9238-82480DC7D8AD_at_[hidden]>
>>> Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes;
>>> format=flowed
>>>
>>> I don't believe that we currently support setenv in the MPI Get
>>> phase, mainly because we didn't know that anyone would be using it
>>> there.
>>>
>>> What do you need to do, specifically?
>>>
>>> FWIW, MTT should handle all paths internally -- it builds everything
>>> inside the scratch tree, maintaining the different trees for all the
>>> different get's and install's.
>>>
>>>
>>> Jeff Squyres
>>> Cisco Systems
>>>
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 3
>>> Date: Thu, 17 May 2007 17:20:40 +0300
>>> From: "Shai Venter" <venters_at_[hidden]>
>>> Subject: [MTT users] How can I know the path to mpicc ?
>>> To: <mtt-users_at_[hidden]>
>>> Message-ID:
>>> <6C2C79E72C305246B504CBA17B5500C90182546D_at_[hidden]>
>>> Content-Type: text/plain; charset="us-ascii"
>>>
>>> Hi there !
>>> Using mtt, I'm trying to build and run the IMB-MPI1 test.
>>> I need to provide to the IMB make file, a path to the bin dir where
>>> mpicc compiler is.
>>> How do I do that, when mtt creat it's own directory trees for mpi
>>> installations.
>>> mtt gets the test sources for that matter, but fails to build.
>>>
>>> Shai Venter
>>> Q.A
>>> Mellanox Technologies, Ltd.
>>> www.mellanox.com
>>> +972 (0)4 9097200 ext. 252
>>> +972 (0)50 2888637
>>>
>>>
>>> Message: 4
>>> Date: Thu, 17 May 2007 07:24:06 -0700
>>> From: Jeff Squyres <jsquyres_at_[hidden]>
>>> Subject: Re: [MTT users] How can I know the path to mpicc ?
>>> To: General user list for the MPI Testing Tool
>>> <mtt-users_at_[hidden]>
>>> Message-ID: <AC772252-424C-4110-8B48-2CA41016C1B0_at_[hidden]>
>>> Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes;
>>> format=flowed
>>>
>>> mpicc should be in the path already; MTT should take care of that
>>> for
>>> you. Here's what I have in the Cisco INI file for the IMB test
>>> build
>>> section:
>>>
>>> [Test build: imb]
>>> test_get = imb
>>> save_stdout_on_success = 1
>>> merge_stdout_stderr = 1
>>>
>>> module = Shell
>>> shell_build_command = <<EOT
>>> cd src
>>> make clean IMB-MPI1
>>> EOT
>>>
>>>
>>>
>>> Jeff Squyres
>>> Cisco Systems
>>>
>>>
>>>
>>>
>>>
>>> End of mtt-users Digest, Vol 15, Issue 3
>>> ****************************************
>>>
>>> _______________________________________________
>>> mtt-users mailing list
>>> mtt-users_at_[hidden]
>>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>>
>>
>> --
>> Jeff Squyres
>> Cisco Systems
>>
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Mon, 21 May 2007 11:41:40 -0400
>> From: Ethan Mallove <ethan.mallove_at_[hidden]>
>> Subject: Re: [MTT users] mtt test build for IMB-MPI1 fails,
>> To: General user list for the MPI Testing Tool
>> <mtt-users_at_[hidden]>
>> Message-ID: <20070521154140.GC6879_at_[hidden]>
>> Content-Type: text/plain; charset=us-ascii
>>
>> Just a guess, but could this could be the source of confusion?
>>
>> https://svn.open-mpi.org/svn/ompi-tests/trunk/PMB-2.2
>> https://svn.open-mpi.org/svn/ompi-tests/trunk/IMB_2.3
>>
>> Should PMB be removed from ompi-tests? I mean, would there
>> ever be a reason to use PMB 2.2 instead of IMB 2.3?
>>
>> -Ethan
>>
>>
>> On Mon, May/21/2007 06:32:53AM, Jeff Squyres wrote:
>>> It looks like your makefile is hard-coded to use /bin/mpicc, which
>>> will always be wrong for MTT. This specifies an absolute location
>>> for mpicc, and does not allow the $PATH to be used.
>>>
>>> Where are you getting your copy of IMB from?
>>>
>>> The IMB 2.3 that is in the ompi_tests repository has a make_openmpi
>>> that contains the following line:
>>>
>>> CC = mpicc
>>>
>>> Hence, "mpicc" is used, and therefore $PATH is used to find it.
>>>
>>> Can you modify your makefile this way?
>>>
>>>
>>> On May 20, 2007, at 12:31 AM, Shai Venter wrote:
>>>
>>>> Hello again Mr Squyres.
>>>>
>>>> I am most greatfull for your answers to my questions (2).
>>>> Actualy, they are both linked to the same issue: my mtt run fails
>>>> in the
>>>> test build phase for IMB-MPI1.
>>>>
>>>> It seems that the make file cannot find the mpicc to compile.
>>>> It searches for it in a default path (/bin/mpicc) but it's
>>>> Usless scince this path is irrelevant.
>>>>
>>>> I've tried this code:
>>>>
>>>> module = Shell
>>>> shell_build_command = <<EOT
>>>> cd src
>>>> make clean IMB-MPI1
>>>> EOT
>>>>
>>>> But still the same error.
>>>>
>>>>
>>>> Lets have a look at the output of build error:
>>>>
>>>>
>> ---------------------------------------------------------------------
>> -
>>>> --
>>>> ----
>>>> sw169:/usr/local/mtt # cat
>>>> scratch/installs/K5a_/tests/imb-2.3/test_built.ini
>>>> # This file was automatically created by Config/IniFiles.pm. Any
>>>> changes made manually are likely to be lost!
>>>> [test_built]
>>>> mpi_version=1.2.2
>>>> full_section_name=test build: imb-2.3
>>>> result_stdout= <<EOT
>>>> /bin/rm -f *.o *~ PI* core IMB-IO IMB-EXT IMB-MPI1 exe_io exe_ext
>>>> exe_mpi1
>>>> touch exe_mpi1 *.c; rm -rf exe_io exe_ext
>>>> make MPI1 CPP=MPI1
>>>> make[1]: Entering directory
>>>> `/usr/local/mtt/scratch/installs/K5a_/tests/imb-2.3/IMB-2.3/src'
>>>> /bin/mpicc -I/include -DMPI1 -O -g -c IMB.c
>>>> make[1]: /bin/mpicc: Command not found
>>>> make[1]: *** [IMB.o] Error 127
>>>> make[1]: Leaving directory
>>>> `/usr/local/mtt/scratch/installs/K5a_/tests/imb-2.3/IMB-2.3/src'
>>>> make: *** [IMB-MPI1] Error 2
>>>> EOT
>>>> refcount=0
>>>> result_message= <<EOT
>>>> Shell: command failed "cd src
>>>> make clean IMB-MPI1"
>>>> EOT
>>>> mpi_install_simple_section_name=gcc
>>>> test_result=0
>>>> exit_status=512
>>>> mpi_get_simple_section_name=ompiv1.2
>>>> simple_section_name=imb-2.3
>>>> srcdir=/usr/local/mtt/scratch/installs/K5a_/tests/imb-2.3/IMB-2.3
>>>> start_timestamp=1179655379
>>>> test_get_simple_section_name=imb
>>>>
>>>>
>> ---------------------------------------------------------------------
>> -
>>>> --
>>>> ----
>>>>
>>>>
>>>>
>>>> I feel that it has some thing to do with setting up an enviroment
>> path
>>>> variable to the mpi bin dir. I could provide it as an argument to
>> the
>>>> "make" file, but I cannot know in advance where mtt creates/
>>>> installs the
>>>> bin dir for each and every mpi installtion.
>>>>
>>>> Hopefully, you'll have an insight on this.
>>>>
>>>> Regards,
>>>> Shai Venter.
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>>
>>>> Today's Topics:
>>>>
>>>> 1. MTT with ompiv1.2 (Shai Venter)
>>>> 2. Re: MTT with ompiv1.2 (Jeff Squyres)
>>>> 3. How can I know the path to mpicc ? (Shai Venter)
>>>> 4. Re: How can I know the path to mpicc ? (Jeff Squyres)
>>>>
>>>>
>>>>
>> ---------------------------------------------------------------------
>> -
>>>>
>>>> Message: 1
>>>> Date: Thu, 17 May 2007 16:50:14 +0300
>>>> From: "Shai Venter" <venters_at_[hidden]>
>>>> Subject: [MTT users] MTT with ompiv1.2
>>>> To: <mtt-users_at_[hidden]>
>>>> Message-ID:
>>>> <6C2C79E72C305246B504CBA17B5500C901825449_at_[hidden]>
>>>> Content-Type: text/plain; charset="us-ascii"
>>>>
>>>> Hi There !
>>>> Regarding the .ini file:
>>>> Using setenv in the MPI Get: phase, should set me an Enviroment
>>>> var,
>>>> right ?!
>>>> So if , let say, I write setenv = MPIHOMEDIR &shell("pwd")/install
>>>> should set MPIHOMEDIR to some path as mentioned.
>>>> Well, I checked for my MPIHOMEDIR in the env ( cmd line: env
>> |grep
>>>> MPI ) and got nothing.
>>>> What did I not do right?
>>>>
>>>>
>>>>
>>>> Shai Venter
>>>> Q.A
>>>> Mellanox Technologies, Ltd.
>>>> www.mellanox.com
>>>> +972 (0)4 9097200 ext. 252
>>>> +972 (0)50 2888637
>>>>
>>>> Date: Thu, 17 May 2007 07:04:22 -0700
>>>> From: Jeff Squyres <jsquyres_at_[hidden]>
>>>> Subject: Re: [MTT users] MTT with ompiv1.2
>>>> To: General user list for the MPI Testing Tool
>>>> <mtt-users_at_[hidden]>
>>>> Message-ID: <4D863C26-EE6F-4F3E-9238-82480DC7D8AD_at_[hidden]>
>>>> Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes;
>>>> format=flowed
>>>>
>>>> I don't believe that we currently support setenv in the MPI Get
>>>> phase, mainly because we didn't know that anyone would be using it
>>>> there.
>>>>
>>>> What do you need to do, specifically?
>>>>
>>>> FWIW, MTT should handle all paths internally -- it builds
>>>> everything
>>>> inside the scratch tree, maintaining the different trees for all
>>>> the
>>>> different get's and install's.
>>>>
>>>>
>>>> Jeff Squyres
>>>> Cisco Systems
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>> Message: 3
>>>> Date: Thu, 17 May 2007 17:20:40 +0300
>>>> From: "Shai Venter" <venters_at_[hidden]>
>>>> Subject: [MTT users] How can I know the path to mpicc ?
>>>> To: <mtt-users_at_[hidden]>
>>>> Message-ID:
>>>> <6C2C79E72C305246B504CBA17B5500C90182546D_at_[hidden]>
>>>> Content-Type: text/plain; charset="us-ascii"
>>>>
>>>> Hi there !
>>>> Using mtt, I'm trying to build and run the IMB-MPI1 test.
>>>> I need to provide to the IMB make file, a path to the bin dir
>>>> where
>>>> mpicc compiler is.
>>>> How do I do that, when mtt creat it's own directory trees for mpi
>>>> installations.
>>>> mtt gets the test sources for that matter, but fails to build.
>>>>
>>>> Shai Venter
>>>> Q.A
>>>> Mellanox Technologies, Ltd.
>>>> www.mellanox.com
>>>> +972 (0)4 9097200 ext. 252
>>>> +972 (0)50 2888637
>>>>
>>>>
>>>> Message: 4
>>>> Date: Thu, 17 May 2007 07:24:06 -0700
>>>> From: Jeff Squyres <jsquyres_at_[hidden]>
>>>> Subject: Re: [MTT users] How can I know the path to mpicc ?
>>>> To: General user list for the MPI Testing Tool
>>>> <mtt-users_at_[hidden]>
>>>> Message-ID: <AC772252-424C-4110-8B48-2CA41016C1B0_at_[hidden]>
>>>> Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes;
>>>> format=flowed
>>>>
>>>> mpicc should be in the path already; MTT should take care of that
>> for
>>>> you. Here's what I have in the Cisco INI file for the IMB test
>> build
>>>> section:
>>>>
>>>> [Test build: imb]
>>>> test_get = imb
>>>> save_stdout_on_success = 1
>>>> merge_stdout_stderr = 1
>>>>
>>>> module = Shell
>>>> shell_build_command = <<EOT
>>>> cd src
>>>> make clean IMB-MPI1
>>>> EOT
>>>>
>>>>
>>>>
>>>> Jeff Squyres
>>>> Cisco Systems
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> End of mtt-users Digest, Vol 15, Issue 3
>>>> ****************************************
>>>>
>>>> _______________________________________________
>>>> mtt-users mailing list
>>>> mtt-users_at_[hidden]
>>>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>>>
>>>
>>> --
>>> Jeff Squyres
>>> Cisco Systems
>>>
>>> _______________________________________________
>>> mtt-users mailing list
>>> mtt-users_at_[hidden]
>>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Mon, 21 May 2007 08:43:42 -0700
>> From: Jeff Squyres <jsquyres_at_[hidden]>
>> Subject: Re: [MTT users] mtt test build for IMB-MPI1 fails,
>> To: General user list for the MPI Testing Tool
>> <mtt-users_at_[hidden]>
>> Message-ID: <C75CDC08-78D4-45EE-8FB8-F9364FDA839D_at_[hidden]>
>> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>>
>> Good point. No, there is no reason to use PMB 2.2. It's older and
>> has known bugs.
>>
>> I always use IMB 2.3.
>>
>>
>> On May 21, 2007, at 8:41 AM, Ethan Mallove wrote:
>>
>>> Just a guess, but could this could be the source of confusion?
>>>
>>> https://svn.open-mpi.org/svn/ompi-tests/trunk/PMB-2.2
>>> https://svn.open-mpi.org/svn/ompi-tests/trunk/IMB_2.3
>>>
>>> Should PMB be removed from ompi-tests? I mean, would there
>>> ever be a reason to use PMB 2.2 instead of IMB 2.3?
>>>
>>> -Ethan
>>>
>>>
>>> On Mon, May/21/2007 06:32:53AM, Jeff Squyres wrote:
>>>> It looks like your makefile is hard-coded to use /bin/mpicc, which
>>>> will always be wrong for MTT. This specifies an absolute location
>>>> for mpicc, and does not allow the $PATH to be used.
>>>>
>>>> Where are you getting your copy of IMB from?
>>>>
>>>> The IMB 2.3 that is in the ompi_tests repository has a make_openmpi
>>>> that contains the following line:
>>>>
>>>> CC = mpicc
>>>>
>>>> Hence, "mpicc" is used, and therefore $PATH is used to find it.
>>>>
>>>> Can you modify your makefile this way?
>>>>
>>>>
>>>> On May 20, 2007, at 12:31 AM, Shai Venter wrote:
>>>>
>>>>> Hello again Mr Squyres.
>>>>>
>>>>> I am most greatfull for your answers to my questions (2).
>>>>> Actualy, they are both linked to the same issue: my mtt run fails
>>>>> in the
>>>>> test build phase for IMB-MPI1.
>>>>>
>>>>> It seems that the make file cannot find the mpicc to compile.
>>>>> It searches for it in a default path (/bin/mpicc) but it's
>>>>> Usless scince this path is irrelevant.
>>>>>
>>>>> I've tried this code:
>>>>>
>>>>> module = Shell
>>>>> shell_build_command = <<EOT
>>>>> cd src
>>>>> make clean IMB-MPI1
>>>>> EOT
>>>>>
>>>>> But still the same error.
>>>>>
>>>>>
>>>>> Lets have a look at the output of build error:
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> -
>
>>>>> -
>>
>>>>> --
>>>>> --
>>>>> ----
>>>>> sw169:/usr/local/mtt # cat
>>>>> scratch/installs/K5a_/tests/imb-2.3/test_built.ini
>>>>> # This file was automatically created by Config/IniFiles.pm. Any
>>>>> changes made manually are likely to be lost!
>>>>> [test_built]
>>>>> mpi_version=1.2.2
>>>>> full_section_name=test build: imb-2.3
>>>>> result_stdout= <<EOT
>>>>> /bin/rm -f *.o *~ PI* core IMB-IO IMB-EXT IMB-MPI1 exe_io exe_ext
>>>>> exe_mpi1
>>>>> touch exe_mpi1 *.c; rm -rf exe_io exe_ext
>>>>> make MPI1 CPP=MPI1
>>>>> make[1]: Entering directory
>>>>> `/usr/local/mtt/scratch/installs/K5a_/tests/imb-2.3/IMB-2.3/src'
>>>>> /bin/mpicc -I/include -DMPI1 -O -g -c IMB.c
>>>>> make[1]: /bin/mpicc: Command not found
>>>>> make[1]: *** [IMB.o] Error 127
>>>>> make[1]: Leaving directory
>>>>> `/usr/local/mtt/scratch/installs/K5a_/tests/imb-2.3/IMB-2.3/src'
>>>>> make: *** [IMB-MPI1] Error 2
>>>>> EOT
>>>>> refcount=0
>>>>> result_message= <<EOT
>>>>> Shell: command failed "cd src
>>>>> make clean IMB-MPI1"
>>>>> EOT
>>>>> mpi_install_simple_section_name=gcc
>>>>> test_result=0
>>>>> exit_status=512
>>>>> mpi_get_simple_section_name=ompiv1.2
>>>>> simple_section_name=imb-2.3
>>>>> srcdir=/usr/local/mtt/scratch/installs/K5a_/tests/imb-2.3/IMB-2.3
>>>>> start_timestamp=1179655379
>>>>> test_get_simple_section_name=imb
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> -
>
>>>>> -
>>
>>>>> --
>>>>> --
>>>>> ----
>>>>>
>>>>>
>>>>>
>>>>> I feel that it has some thing to do with setting up an enviroment
>>>>> path
>>>>> variable to the mpi bin dir. I could provide it as an argument to
>>>>> the
>>>>> "make" file, but I cannot know in advance where mtt creates/
>>>>> installs the
>>>>> bin dir for each and every mpi installtion.
>>>>>
>>>>> Hopefully, you'll have an insight on this.
>>>>>
>>>>> Regards,
>>>>> Shai Venter.
>>>>>
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>>
>>>>> Today's Topics:
>>>>>
>>>>> 1. MTT with ompiv1.2 (Shai Venter)
>>>>> 2. Re: MTT with ompiv1.2 (Jeff Squyres)
>>>>> 3. How can I know the path to mpicc ? (Shai Venter)
>>>>> 4. Re: How can I know the path to mpicc ? (Jeff Squyres)
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> -
>
>>>>> -
>>
>>>>> --
>>>>>
>>>>> Message: 1
>>>>> Date: Thu, 17 May 2007 16:50:14 +0300
>>>>> From: "Shai Venter" <venters_at_[hidden]>
>>>>> Subject: [MTT users] MTT with ompiv1.2
>>>>> To: <mtt-users_at_[hidden]>
>>>>> Message-ID:
>>>>> <6C2C79E72C305246B504CBA17B5500C901825449_at_[hidden]>
>>>>> Content-Type: text/plain; charset="us-ascii"
>>>>>
>>>>> Hi There !
>>>>> Regarding the .ini file:
>>>>> Using setenv in the MPI Get: phase, should set me an Enviroment
>>>>> var,
>>>>> right ?!
>>>>> So if , let say, I write setenv = MPIHOMEDIR &shell("pwd")/
>>>>> install
>>>>> should set MPIHOMEDIR to some path as mentioned.
>>>>> Well, I checked for my MPIHOMEDIR in the env ( cmd line: env |
>>>>> grep
>>>>> MPI ) and got nothing.
>>>>> What did I not do right?
>>>>>
>>>>>
>>>>>
>>>>> Shai Venter
>>>>> Q.A
>>>>> Mellanox Technologies, Ltd.
>>>>> www.mellanox.com
>>>>> +972 (0)4 9097200 ext. 252
>>>>> +972 (0)50 2888637
>>>>>
>>>>> Date: Thu, 17 May 2007 07:04:22 -0700
>>>>> From: Jeff Squyres <jsquyres_at_[hidden]>
>>>>> Subject: Re: [MTT users] MTT with ompiv1.2
>>>>> To: General user list for the MPI Testing Tool
>>>>> <mtt-users_at_[hidden]>
>>>>> Message-ID: <4D863C26-EE6F-4F3E-9238-82480DC7D8AD_at_[hidden]>
>>>>> Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes;
>>>>> format=flowed
>>>>>
>>>>> I don't believe that we currently support setenv in the MPI Get
>>>>> phase, mainly because we didn't know that anyone would be using it
>>>>> there.
>>>>>
>>>>> What do you need to do, specifically?
>>>>>
>>>>> FWIW, MTT should handle all paths internally -- it builds
>>>>> everything
>>>>> inside the scratch tree, maintaining the different trees for all
>>>>> the
>>>>> different get's and install's.
>>>>>
>>>>>
>>>>> Jeff Squyres
>>>>> Cisco Systems
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------
>>>>>
>>>>> Message: 3
>>>>> Date: Thu, 17 May 2007 17:20:40 +0300
>>>>> From: "Shai Venter" <venters_at_[hidden]>
>>>>> Subject: [MTT users] How can I know the path to mpicc ?
>>>>> To: <mtt-users_at_[hidden]>
>>>>> Message-ID:
>>>>> <6C2C79E72C305246B504CBA17B5500C90182546D_at_[hidden]>
>>>>> Content-Type: text/plain; charset="us-ascii"
>>>>>
>>>>> Hi there !
>>>>> Using mtt, I'm trying to build and run the IMB-MPI1 test.
>>>>> I need to provide to the IMB make file, a path to the bin dir
>>>>> where
>>>>> mpicc compiler is.
>>>>> How do I do that, when mtt creat it's own directory trees for mpi
>>>>> installations.
>>>>> mtt gets the test sources for that matter, but fails to build.
>>>>>
>>>>> Shai Venter
>>>>> Q.A
>>>>> Mellanox Technologies, Ltd.
>>>>> www.mellanox.com
>>>>> +972 (0)4 9097200 ext. 252
>>>>> +972 (0)50 2888637
>>>>>
>>>>>
>>>>> Message: 4
>>>>> Date: Thu, 17 May 2007 07:24:06 -0700
>>>>> From: Jeff Squyres <jsquyres_at_[hidden]>
>>>>> Subject: Re: [MTT users] How can I know the path to mpicc ?
>>>>> To: General user list for the MPI Testing Tool
>>>>> <mtt-users_at_[hidden]>
>>>>> Message-ID: <AC772252-424C-4110-8B48-2CA41016C1B0_at_[hidden]>
>>>>> Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes;
>>>>> format=flowed
>>>>>
>>>>> mpicc should be in the path already; MTT should take care of that
>>>>> for
>>>>> you. Here's what I have in the Cisco INI file for the IMB test
>>>>> build
>>>>> section:
>>>>>
>>>>> [Test build: imb]
>>>>> test_get = imb
>>>>> save_stdout_on_success = 1
>>>>> merge_stdout_stderr = 1
>>>>>
>>>>> module = Shell
>>>>> shell_build_command = <<EOT
>>>>> cd src
>>>>> make clean IMB-MPI1
>>>>> EOT
>>>>>
>>>>>
>>>>>
>>>>> Jeff Squyres
>>>>> Cisco Systems
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> End of mtt-users Digest, Vol 15, Issue 3
>>>>> ****************************************
>>>>>
>>>>> _______________________________________________
>>>>> mtt-users mailing list
>>>>> mtt-users_at_[hidden]
>>>>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>>>>
>>>>
>>>> --
>>>> Jeff Squyres
>>>> Cisco Systems
>>>>
>>>> _______________________________________________
>>>> 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
>>
>>
>> --
>> Jeff Squyres
>> Cisco Systems
>>
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> mtt-users mailing list
>> mtt-users_at_[hidden]
>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>>
>>
>> End of mtt-users Digest, Vol 15, Issue 5
>> ****************************************
>>
>> _______________________________________________
>> mtt-users mailing list
>> mtt-users_at_[hidden]
>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>
>
> --
> Jeff Squyres
> Cisco Systems
>
>
>
> ------------------------------
>
> _______________________________________________
> mtt-users mailing list
> mtt-users_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>
>
> End of mtt-users Digest, Vol 16, Issue 2
> ****************************************
>
> _______________________________________________
> mtt-users mailing list
> mtt-users_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users

-- 
Jeff Squyres
Cisco Systems