Test email... please ignore...
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
You're seeing commits from me go by, but I'm still working on the scripting
infrastructure. Please be patient; this is complicated stuff...
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
I should have been clearer. This changes how the topo components are
expected to work. With this change they now MUST provide the c_topo to
the communicator before coll_select. The change is good but may be
unexpected for any vendor topo components out there (which I doubt
there are any).
-Nathan
Nathan?
On Oct 1, 2014, at 10:27 AM, George Bosilca wrote:
> I see no change in the topo interface in any of the patches attached to this
> thread. Is there any other patch related to this discussion?
>
> George.
>
>
>
>> On Oct 1, 2014, at 14:52, Jeff Squyres (jsquyres) wrote:
>>
>>> On
I see no change in the topo interface in any of the patches attached to this
thread. Is there any other patch related to this discussion?
George.
> On Oct 1, 2014, at 14:52, Jeff Squyres (jsquyres) wrote:
>
>> On Oct 1, 2014, at 6:48 AM, Gilles Gouaillardet
>> wrote:
>>
>> oops, i misse
On Oct 1, 2014, at 6:48 AM, Gilles Gouaillardet
wrote:
> oops, i missed graph and dist graph :-(
>
> the attached patch fixes this
> /* it was straightforward for graph and a bit more challenging for dist
> graph */
>
> i am fine for Nathan's patch for v1.8
> /* v1.8 and trunk have already a d
The OMPI SVN and Trac are now officially closed (i.e., in a read-only state).
The Github migration is starting. Please do not make any changes to
https://github.com/open-mpi/ompi until I send an "open for business!" email.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go t
oops, i missed graph and dist graph :-(
the attached patch fixes this
/* it was straightforward for graph and a bit more challenging for dist
graph */
i am fine for Nathan's patch for v1.8
/* v1.8 and trunk have already a different way to handle a memory leak */
/* the attached patch is vs v1.8 b
Thanks Ralph !
it did fix the problem
Cheers,
Gilles
On 2014/10/01 3:04, Ralph Castain wrote:
> I fixed this in r32818 - the components shouldn't be passing back success if
> the requested info isn't found. Hope that fixes the problem.
>
>
> On Sep 30, 2014, at 1:54 AM, Gilles Gouaillardet
>
