Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some really minor cleanups #1298

Merged
merged 1 commit into from
Mar 21, 2022
Merged

Some really minor cleanups #1298

merged 1 commit into from
Mar 21, 2022

Conversation

rhc54
Copy link
Contributor

@rhc54 rhc54 commented Mar 21, 2022

Don't keep setting the proc type.
Only daemonize if directly told to do so.

Signed-off-by: Ralph Castain rhc@pmix.org

Don't keep setting the proc type.
Only daemonize if directly told to do so.

Signed-off-by: Ralph Castain <rhc@pmix.org>
@rhc54
Copy link
Contributor Author

rhc54 commented Mar 21, 2022

@awlauria There is an error in the dmodex.c program:

Client ns prte-5134f3fdd8dc-156@1 rank 0: PMIx_Get prte-5134f3fdd8dc-156@1-0-remote failed: NOT-FOUND

Rank 0 is asking for remote data on itself. Remote data can only be retrieved by a proc on another node. Thus, this data can never be retrieved by the proc that posted it. May seem odd, but those are the rules.

@rhc54
Copy link
Contributor Author

rhc54 commented Mar 21, 2022

bot:ibm:gnu:retest

@rhc54
Copy link
Contributor Author

rhc54 commented Mar 21, 2022

Actually, I suppose I am somewhat confused by that output - looking at the dmodex code, there shouldn't be any way that rank N could ask for remote data on itself. Perhaps what needs to be investigated is how that request got generated?

@rhc54 rhc54 merged commit 0db143d into openpmix:master Mar 21, 2022
@rhc54 rhc54 deleted the topic/clnup branch March 21, 2022 06:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant