Fixed in https://github.com/open-mpi/ompi/pull/1959
> On Aug 11, 2016, at 6:23 PM, Gilles Gouaillardet wrote:
>
> Thanks George,
>
>
> fwiw, note the current behavior is a bit more "twisted" than that.
>
> OPAL_MODEX_RECV_VALUE() returns successfully (e.g. err == OPAL_SUCCESS) but
> the OPA
Thanks George,
fwiw, note the current behavior is a bit more "twisted" than that.
OPAL_MODEX_RECV_VALUE() returns successfully (e.g. err == OPAL_SUCCESS)
but the OPAL_PMIX_NODEID (e.g. val) value is -1.
that means orted did "push" OPAL_PMIX_NODEID, but with an unitialized
value of -1 (this
I’m working on providing the info, guys - just sitting in a branch right now.
Too many meetings...sigh.
> On Aug 11, 2016, at 10:09 AM, George Bosilca wrote:
>
> I just pushed a solution to this problem in 8d0baf140f. If we are unable to
> extract the expected information from the RTE, we sim
I just pushed a solution to this problem in 8d0baf140f. If we are unable to
extract the expected information from the RTE, we simply build a
non-reordered communicator and gracefully return.
That being said, not being able to correctly retrieve OPAL_PMIX_NODEID has
the potential to drastically dec
