-
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 #974
955 clear out uses of addAction in tests #974
Conversation
18bb1ba
to
aa8ea3d
Compare
Codecov Report
@@ Coverage Diff @@
## develop #974 +/- ##
===========================================
+ Coverage 77.24% 77.26% +0.01%
===========================================
Files 656 656
Lines 25052 25037 -15
===========================================
- Hits 19352 19344 -8
+ Misses 5700 5693 -7
|
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 is looking great to me
there's still a couple of files to be cleared, the rest is landing on Monday |
aa8ea3d
to
c97fc6f
Compare
cbd4f70
to
c6e622d
Compare
files cleared:
|
6cede9d
to
24a886c
Compare
documentation improvements:
|
ecfd4aa
to
334a7a3
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.
This looks great now, I think it's ready to merge once CI passes
Yep, I think it's good to go :) Side note: you might have seen that already, TimeTrigger tests are still failing from time to time (
plus there's one (new?) warning generated from that test:
|
Yes, I saw that it is still failing. Planning to fix |
@cz4rs Ok, can you rebase and then we can merge? |
c4bd1fc
to
4c45a7c
Compare
Here is an overview of what got changed by this pull request: Clones removed
==============
+ tests/unit/memory/test_memory_lifetime.cc -3
See the complete overview on Codacy |
rebased with the latest changes from |
runInEpochCollective([&]{ | ||
// self-send a message and then broadcast | ||
proxy[my_node].send<MyMsg, &MyObjA::handler>(); | ||
proxy.broadcast<MyMsg, &MyObjA::handler>(); |
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 I think this is a scalability problem for cases where vt is configured and compiled on a host with large numbers of cores - the message count will scale with the number of cores, which can make it take an arbitrarily long time on a very wide node
@@ -151,18 +151,13 @@ void verifyCacheConsistency( | |||
// perform the checks only at the end of the epoch | |||
// to ensure that all entity messages have been | |||
// correctly delivered before. |
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 I think this change may have fundamentally shifted the meaning of this test. Please double check
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 diff is really confusing to read. Had to go back and look.
This test is not testing the same thing at all. It's now checking the state before. I should have caught this.
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 will revert and (try to) handle this correctly in #989
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.
Fixes #955