-
Notifications
You must be signed in to change notification settings - Fork 13
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
Unit tests for query_initialized #45
base: main
Are you sure you want to change the base?
Conversation
52e55f8
to
7665287
Compare
7665287
to
949c4a2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this test might be better placed somewhere like test/shmemx
since the mulitple init/finalize feature is predicted to be a part of OpenSHMEM v1.6.
1a2744e
to
6e13f1c
Compare
int finalizes_done = 0; | ||
|
||
// Check if SHMEM is initialized before calling init | ||
shmem_query_initialized(&initialized); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this should probably be shmemx_query_initialized
... At least for tests-sos v1.5.x.
If we go that route, then this test wouldn't build against your SOS implementation of course, but I think that's ok temporarily during our transition to v1.6.x.
I think let's keep the test this way (shmem_
) until we are ready to merge Sandia-OpenSHMEM/SOS#1144. Then we can test against this? Although, I'm not certain our CI covers shmemx very well... will have to check.
Sorry for the confusion...
No description provided.