Open MPI logo

MTT Devel Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [MTT devel] Check a v3.0 commit
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2009-04-29 15:15:59

Ah -- I parsed your original comment wrong. I get it now. :-)

On Apr 29, 2009, at 3:15 PM, Ethan Mallove wrote:

> 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
>>>> 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-devel_at_[hidden]
> _______________________________________________
> mtt-devel mailing list
> mtt-devel_at_[hidden]

Jeff Squyres
Cisco Systems