-
Notifications
You must be signed in to change notification settings - Fork 9
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
955 Clear out uses of addAction in tests #979
955 Clear out uses of addAction in tests #979
Conversation
c6842b0
to
12cf645
Compare
12cf645
to
a5cdad1
Compare
Codecov Report
@@ Coverage Diff @@
## develop #979 +/- ##
===========================================
+ Coverage 77.35% 77.40% +0.04%
===========================================
Files 656 656
Lines 25110 25129 +19
===========================================
+ Hits 19424 19451 +27
+ Misses 5686 5678 -8
|
cb25503
to
52ece3c
Compare
52ece3c
to
ae755fb
Compare
} \ | ||
} while (false); | ||
} while (false); \ | ||
|
||
#define FN_APPLY(SEQ_HAN, SEQ_FN, NODE, MSG_TYPE, ___, IS_TAG) \ |
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.
@lifflander
Just noticing that the FN_APPLY
and CALL_EXPAND
macros are each used only once below. That makes their definition as macros seem sort of silly
For the tests you left alone, here are my thoughts:
|
Note to self: the files addressed match the files assigned |
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.
Overall, this looks good to me. I don't see any problems as long as the tests pass consistently,
@JacobDomagala Can you address any comments for change and then rebase this on develop? |
ae755fb
to
fe7f32b
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.
@JacobDomagala Should line 91 of test_callback_func be changed from runInEpochCollective([=]{
to runInEpochCollective([&}{
so that it has the proper context passed in?
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.
Looks good. @JacobDomagala If the = does not need to be replaced would you explain why? AFAIK the & operator in runInEpochCollective
is the pass the proper context to the function. This way it has access to the variables in the previous scope. Is this correct?
86b047c
to
e9dc906
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.
looks good overall to me
depending on the outcome of the discussion about proxy.destroy();
I might need to revisit test_callback_bcast_collection.extended.cc
@bradybray Both |
@JacobDomagala Is this ready to rebase and merge? |
374c982
to
8f1fc53
Compare
Yes, rebased on top of develop and it's ready to be merged. |
@JacobDomagala Github won't let you merge this because you haven't signed your commits with your GPG key. Did you set up GPG? You need to attach it to git so it adds your signature to the commits. |
… applicable and fix lambda formatting
…CallbackSendCollection instead of checking them during Collection destruction
…r checking TestCallbackSendCollection test results
8f1fc53
to
fa70854
Compare
Yes, it seems that i lost my commits signatures after i rebased the branch. Should be ok now. |
Clones added
============
- tests/unit/pipe/test_callback_send_collection.extended.cc 2
- tests/unit/pipe/test_callback_func_ctx.cc 1
Clones removed
==============
+ tests/unit/pipe/test_callback_send.cc -1
See the complete overview on Codacy |
Following tests are left unchanged (addAction() is a part of termination namespace so i thought its usage here makes sense)