You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reviewing commmits to master for orte subdir to see if there are bits we will want/need to carry over to PRRTE. This was prompted by noticing some changes in Nov related to IOF that likely might need to be carried over when we move to PRRTE.
What version of Open MPI are you using? (e.g., v1.10.3, v2.1.0, git branch name and hash, etc.)
I walked through recent history for 2019 OMPI commits in theorte subdir and tried to identify items that should be taken over (TAKE), should be skipped or already exist in PRRTE (SKIP), and items where I was unsure/need a review (REVIEW).
TAKE: 4f1de51; Fri Nov 15 12:36:36 2019 -0500; Add detection for JSM direct launch
RHC: I don't think we can take this over to PRRTE as it won't do anything there. PRRTE is just daemons - there are no PRRTE-based apps and no application would ever call prrte_init. Thus, it isn't clear to me what this component would do.@jjhursey - any thoughts here?
TAKE: 9b73f6a; Sun Nov 10 14:58:55 2019 -0500; Fix misleading error message with missing #! interpreter
I guess I didn't follow up here about the JSM schizo component. That component was intended to help OMPI detect being direct launched with JSM. When we move to PRRTE then OMPI will use standard PMIx mechanisms for this detection, so it shouldn't be needed anymore. I agree it wouldn't make sense to have it in PRRTE.
Background information
Reviewing commmits to
master
fororte
subdir to see if there are bits we will want/need to carry over to PRRTE. This was prompted by noticing some changes in Nov related to IOF that likely might need to be carried over when we move to PRRTE.What version of Open MPI are you using? (e.g., v1.10.3, v2.1.0, git branch name and hash, etc.)
Details of the problem
I walked through recent history for 2019 OMPI commits in the
orte
subdir and tried to identify items that should be taken over (TAKE
), should be skipped or already exist in PRRTE (SKIP
), and items where I was unsure/need a review (REVIEW
).Steps:
orte
dirgit show SHA
), comparing against PRRTE masterMy initial review of things looks like this...
TAKE/EDIT:
MAYBE/REVIEW:
NOT-NEEDED/ALREADY-DONE:
The text was updated successfully, but these errors were encountered: