Re: [MTT devel] Check a v3.0 commit

2009-04-29 Thread Ethan Mallove
On Wed, Apr/29/2009 02:34:54PM, Jeff Squyres wrote:
> On Apr 29, 2009, at 2:32 PM, Ethan Mallove wrote:
>
>>> Can one of you guys sanity https://svn.open-mpi.org/trac/mtt/changeset/1283
>>> before I move it to the 3.0 branch?
>>>
>>> It should save some testing cycles if the OMPI tarball hasn't changed
>>> versions from one day to the next (and you start using the field
>>> ompi_snapshot_version_file in your INI file).
>>
>> Works for me. Just had to make sure to set force to "0" in my INI file.
>
> What do you mean?  I tried it with and without setting the field and it 
> seemed to do what I intended -- are you saying that you had to set it to 0 
> to get it to ignore the field properly?

I meant ompi_snapshot_version_file works correctly. Having "force" set
to "1" in my INI file overrode the ompi_snapshot_version_file param,
which is what was supposed to happen. Setting "force" to "0" made MTT
actually skip a tarball when the ompi_snapshot_version_file matched
the downloaded latest_snapshot.txt file.

-Ethan

>
> -- 
> Jeff Squyres
> Cisco Systems
>
> ___
> mtt-devel mailing list
> mtt-de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel


Re: [MTT devel] Check a v3.0 commit

2009-04-29 Thread Ethan Mallove
On Wed, Apr/29/2009 12:30:25PM, Jeff Squyres wrote:
> Can one of you guys sanity https://svn.open-mpi.org/trac/mtt/changeset/1283 
> before I move it to the 3.0 branch?
>
> It should save some testing cycles if the OMPI tarball hasn't changed 
> versions from one day to the next (and you start using the field 
> ompi_snapshot_version_file in your INI file).

Works for me. Just had to make sure to set force to "0" in my INI file.

-Ethan


>
> -- 
> Jeff Squyres
> Cisco Systems
>
> ___
> mtt-devel mailing list
> mtt-de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel


[MTT devel] Check a v3.0 commit

2009-04-29 Thread Jeff Squyres
Can one of you guys sanity https://svn.open-mpi.org/trac/mtt/changeset/1283 
 before I move it to the 3.0 branch?


It should save some testing cycles if the OMPI tarball hasn't changed  
versions from one day to the next (and you start using the field  
ompi_snapshot_version_file in your INI file).


--
Jeff Squyres
Cisco Systems