Re: [OMPI devel] MPI_Comm_spawn broken on master on RHEL7

2016-07-16 Thread Ralph Castain
I found the reason for the notification and fixed that as well - should all be done now > On Jul 16, 2016, at 10:37 AM, Ralph Castain wrote: > > Kewl - thanks! I will take care of this, but to me the most pressing issue is > why this event notification is being generated at all. It shouldn’t b

Re: [OMPI devel] MPI_Comm_spawn broken on master on RHEL7

2016-07-16 Thread Ralph Castain
Kewl - thanks! I will take care of this, but to me the most pressing issue is why this event notification is being generated at all. It shouldn’t be. > On Jul 16, 2016, at 9:11 AM, Gilles Gouaillardet > wrote: > > I finally got it :-) > > in send_notification() from orted_submit.c, info is >

Re: [OMPI devel] MPI_Comm_spawn broken on master on RHEL7

2016-07-16 Thread Gilles Gouaillardet
I finally got it :-) in send_notification() from orted_submit.c, info is OPAL_PMIX_EVENT_NON_DEFAULT, but in pmix2x.c and pmix_ext20.c, PMIX_EVENT_NON_DEFAULT is tested. If I use OPAL_PMIX_EVENT_NON_DEFAULT in pmix*, that fixes the issue Cheers, Gilles On Sunday, July 17, 2016, Ralph Castain w

Re: [OMPI devel] MPI_Comm_spawn broken on master on RHEL7

2016-07-16 Thread Ralph Castain
Okay, I’ll investigate why that is happening - thanks! > On Jul 16, 2016, at 7:45 AM, Gilles Gouaillardet > wrote: > > The parent job (e.g. the task that calls MPI_Comm_spawn) receives it. > I cannot tell whether the child (e.g. the spawned task) receives it too or not > > Cheers, > > Gilles

Re: [OMPI devel] MPI_Comm_spawn broken on master on RHEL7

2016-07-16 Thread Gilles Gouaillardet
The parent job (e.g. the task that calls MPI_Comm_spawn) receives it. I cannot tell whether the child (e.g. the spawned task) receives it too or not Cheers, Gilles On Saturday, July 16, 2016, Ralph Castain wrote: > I can fix the initialization. What puzzles me is that no debugger_release > me

Re: [OMPI devel] MPI_Comm_spawn broken on master on RHEL7

2016-07-16 Thread Ralph Castain
I can fix the initialization. What puzzles me is that no debugger_release message should be sent unless a debugger is attached - in which case, the event should be registered. So why is it being sent? Is it the child job that is receiving it? Or is it the parent? > On Jul 16, 2016, at 7:19 AM

Re: [OMPI devel] MPI_Comm_spawn broken on master on RHEL7

2016-07-16 Thread Gilles Gouaillardet
I found some time to investigate this. tscon should initialize nondefault to false in both pmix2x.c and pmix_ext20.c A better workaround is to update ompi_errhandler_callback, so it does not invoke ompi_mpi_abort if status is OPAL_ERR_DEBUGGER_RELEASE That still seems counter intuitive to me ...

Re: [OMPI devel] v2.0.1 PRs: open season

2016-07-16 Thread Siegmar Gross
Hi Jeff, I didn't find the PR for my problem in your list and I'm waiting for a solution. https://github.com/open-mpi/ompi/issues/1573 Kind regards and thank you very much for any help in advance Siegmar Am 15.07.2016 um 16:15 schrieb Jeff Squyres (jsquyres): v2.0.1 is officially open to a