-
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
1111 Fix for large message sends #1113
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #1113 +/- ##
===========================================
+ Coverage 79.28% 79.45% +0.16%
===========================================
Files 716 718 +2
Lines 27037 27241 +204
===========================================
+ Hits 21436 21643 +207
+ Misses 5601 5598 -3
|
Currently failing unrelated tests:
Edit: should all be fixed now |
All the test failures should be fixed now. |
db4dc1f
to
24d9355
Compare
0af808f
to
e0f9bc8
Compare
auto& holder = theEvent()->getEventHolder(ret_event); | ||
for (auto&& child_event : events) { | ||
holder.get_event()->addEventToList(child_event); | ||
} |
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.
This block seems a bit awkward, but it's inconsequential
Reading on my phone, so I can't get a great overview at the moment. I think we're close on this |
@@ -485,6 +485,18 @@ void ArgConfig::addConfigFileArgs(CLI::App& app) { | |||
a2->group(configGroup); | |||
} | |||
|
|||
void ArgConfig::addRuntimeArgs(CLI::App& app) { |
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.
Not a problem, but why is this 'RuntimeArgs' instead of 'MessengerArgs'?
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.
Could be either. I just happened to choose that one.
At least some of the failing tests are quite real - there's a memory leak reported of an allocation in |
Here is an overview of what got changed by this pull request: Clones removed
==============
+ src/vt/messaging/active.cc -2
See the complete overview on Codacy |
aff8bfa
to
90c9305
Compare
Fixes #1111
Start with tests that fail for serialized/non-serialized messages
Make a major improvement to how tests are being dispatched. Currently, tests are being ignored due to deficiencies in the gtest cmake. Pull in the latest gtest cmake and fix the bugs in that version of the cmake. This is causing "new" tests to fail on this PR that weren't running before which I am systematically trying to fixImplement "multi-sends" for serialized and non-serialized messages (now passing!)
Add a new runtime argument
--vt_max_mpi_send_size=X
that defaults to1ull << 30
.Use the new argument injector to set the size for testing to
16384
bytes