I guess (r32401).
George.
On Fri, Aug 1, 2014 at 12:32 PM, Ralph Castain wrote:
> I found the problem - the issue is that assert on the convertor. MPI apps
> are setting that convertor, but not non-MPI apps, and so the field is NULL.
> Can we remove that assert?
>
>
> On Aug 1, 2014, at 9:3
I found the problem - the issue is that assert on the convertor. MPI apps are
setting that convertor, but not non-MPI apps, and so the field is NULL. Can we
remove that assert?
On Aug 1, 2014, at 9:30 AM, George Bosilca wrote:
> I missed the fact that the app doesn't force it. But if this is
I missed the fact that the app doesn't force it. But if this is indeed the
case then it is extremely weird that you are seing someone else releasing
your proc.
Regarding the destruction of the proc, the OPAL layer only does in a single
place, when the local proc is set (opal_proc_local_set). Moreo
On Aug 1, 2014, at 8:27 AM, George Bosilca wrote:
> This commit brings two things. One if the renaming suggested by Gilles. The
> second one is forcing the ORTE process down on the OPAL. This doesn't fit the
> current design of the BTL move. The current design assumes that the local
> OPAL pr
This commit brings two things. One if the renaming suggested by Gilles. The
second one is forcing the ORTE process down on the OPAL. This doesn't fit
the current design of the BTL move. The current design assumes that the
local OPAL process is part of the local OMPI process.
George.
PS: If it d
