Re: [MTT users] autogen.sh in svn_post_export

2009-11-04 Thread Jeff Squyres

On Nov 4, 2009, at 4:38 PM, Ethan Mallove wrote:


> Perhaps the solution is better checking that autogen.sh executed
> properly...?  I.e., fail in the test get rather than the test  
build...?


I wonder if in the test get section, MTT isn't chdir'd into the proper
directory to run autogen.sh successfully?




Works for me...

--
Jeff Squyres
jsquy...@cisco.com



Re: [MTT users] autogen.sh in svn_post_export

2009-11-04 Thread Ethan Mallove
On Wed, Nov/04/2009 03:56:10PM, Jeff Squyres wrote:
> On Nov 4, 2009, at 3:19 PM, Ethan Mallove wrote:
>
>> Hmmm. QLogic and IU are also running into the same issue:
>>
>>   http://www.open-mpi.org/mtt/index.php?do_redir=1170
>>
>> I just filed a Trac ticket:
>>
>>   https://svn.open-mpi.org/trac/mtt/ticket/388
>>
>
> Perhaps the solution is better checking that autogen.sh executed 
> properly...?  I.e., fail in the test get rather than the test build...?

I wonder if in the test get section, MTT isn't chdir'd into the proper
directory to run autogen.sh successfully?

-Ethan

>
> -- 
> Jeff Squyres
> jsquy...@cisco.com
>
> ___
> mtt-users mailing list
> mtt-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users


Re: [MTT users] autogen.sh in svn_post_export

2009-11-04 Thread Jeff Squyres

On Nov 4, 2009, at 3:19 PM, Ethan Mallove wrote:


Hmmm. QLogic and IU are also running into the same issue:

  http://www.open-mpi.org/mtt/index.php?do_redir=1170

I just filed a Trac ticket:

  https://svn.open-mpi.org/trac/mtt/ticket/388




Perhaps the solution is better checking that autogen.sh executed  
properly...?  I.e., fail in the test get rather than the test build...?


--
Jeff Squyres
jsquy...@cisco.com



Re: [MTT users] autogen.sh in svn_post_export

2009-11-04 Thread Ethan Mallove
On Wed, Nov/04/2009 02:22:28PM, Jeff Squyres wrote:
> On Nov 4, 2009, at 1:51 PM, Ethan Mallove wrote:
>
>> I recently ran into the error "./configure: No such file or directory"
>> in my nightly test build for the ibm, mpicxx, and onesided test
>> suites:
>>
>>   http://www.open-mpi.org/mtt/index.php?do_redir=1169
>>
>> This problem had something to do with autogen.sh being run in the Test
>> get section (different environment settings, maybe?). Moving the
>> autogen.sh into the Test build section (before "configure" in the
>> shell_build_command) resolved the problem. To prevent this problem,
>> would it be too uncouth to add pre-generated configure scripts (a la
>> the nightly Open MPI tarballs) in the ompi-tests repository?
>>
>
>
> Yes, it would be uncouth.  :-)  One does not put generated code in the 
> repository.
>
> I'm not sure why moving the autogen.sh from test get to test build would 
> fix the issue for you -- are your autotools in your normal environment, or 
> do you have them in some particular environment that is loaded by an mpi 
> install phase?

Hmmm. QLogic and IU are also running into the same issue:

  http://www.open-mpi.org/mtt/index.php?do_redir=1170

I just filed a Trac ticket:

  https://svn.open-mpi.org/trac/mtt/ticket/388

-Ethan

>
> -- 
> Jeff Squyres
> jsquy...@cisco.com
>
> ___
> mtt-users mailing list
> mtt-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users


Re: [MTT users] autogen.sh in svn_post_export

2009-11-04 Thread Jeff Squyres

On Nov 4, 2009, at 1:51 PM, Ethan Mallove wrote:


I recently ran into the error "./configure: No such file or directory"
in my nightly test build for the ibm, mpicxx, and onesided test
suites:

  http://www.open-mpi.org/mtt/index.php?do_redir=1169

This problem had something to do with autogen.sh being run in the Test
get section (different environment settings, maybe?). Moving the
autogen.sh into the Test build section (before "configure" in the
shell_build_command) resolved the problem. To prevent this problem,
would it be too uncouth to add pre-generated configure scripts (a la
the nightly Open MPI tarballs) in the ompi-tests repository?




Yes, it would be uncouth.  :-)  One does not put generated code in the  
repository.


I'm not sure why moving the autogen.sh from test get to test build  
would fix the issue for you -- are your autotools in your normal  
environment, or do you have them in some particular environment that  
is loaded by an mpi install phase?


--
Jeff Squyres
jsquy...@cisco.com