I tested my application with the snapshot and it works fine!
thanks.
márcia.
On Thu, Dec 17, 2009 at 6:48 PM, Ralph Castain wrote:
> Will be in the 1.4 nightly tarball generated later tonight...
>
> Thanks again
> Ralph
>
> On Dec 17, 2009, at 4:07 AM, Marcia Cristina Cera wrote:
>
> very good n
Will be in the 1.4 nightly tarball generated later tonight...
Thanks again
Ralph
On Dec 17, 2009, at 4:07 AM, Marcia Cristina Cera wrote:
> very good news
> I will wait carefully for the release :)
>
> Thanks, Ralph
> márcia.
>
> On Wed, Dec 16, 2009 at 10:56 PM, Ralph Castain wrote:
> A
very good news
I will wait carefully for the release :)
Thanks, Ralph
márcia.
On Wed, Dec 16, 2009 at 10:56 PM, Ralph Castain wrote:
> Ah crumb - I found the problem. Sigh.
>
> I actually fixed this in the trunk over 5 months ago when the problem first
> surfaced in my own testing, but it n
Ah crumb - I found the problem. Sigh.
I actually fixed this in the trunk over 5 months ago when the problem first
surfaced in my own testing, but it never came across to the stable release
branch. The problem is that we weren't serializing the comm_spawn requests, and
so the launch system gets
Hi Ralph,
I am afraid I have been a little hasty!
I remake my tests with more care and I got the same error also with the
1.3.3 :-/
but in such version the error happens after some successful executions...
because of that I did not realize before!
Furthermore, I increased the number of levels of t
Okay, I can replicate this.
FWIW: your test program works fine with the OMPI trunk and 1.3.3. It only has
a problem with 1.4. Since I can replicate it on multiple machines every single
time, I don't think it is actually a race condition.
I think someone made a change to the 1.4 branch that cre
Thank you, Ralph
I will use the 1.3.3 for now...
while waiting for a future fix release that break this race condiction.
márcia
On Tue, Dec 15, 2009 at 12:58 PM, Ralph Castain wrote:
> Looks to me like it is a race condition, and the timing between 1.3.3 and
> 1.4 is just enough to trip it. I
Looks to me like it is a race condition, and the timing between 1.3.3 and 1.4
is just enough to trip it. I can break the race, but it will have to be in a
future fix release.
Meantime, your best bet is to either stick with 1.3.3 or add the delay.
On Dec 15, 2009, at 5:51 AM, Marcia Cristina Cer
Hi,
I intend to develop an application using the MPI_Comm_spawn to create
dynamically new MPI tasks (or processes).
The structure of the program is like a tree: each node creates 2 new ones
until reaches a predefined number of levels.
I developed a small program to explain my problem as can be se
