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
Fix tests using election_scheduler::flush()
#3961
Fix tests using election_scheduler::flush()
#3961
Conversation
0769646
to
1b2b026
Compare
election_scheduler
testselection_scheduler::flush()
@clemahieu I pushed one more commit fixing more test cases using the problematic flush |
Let's remove the scheduler flush from the test cases where we fixed it. |
@dsiganos Good point, those flush calls are not needed anymore. Already pushed a commit. |
@@ -47,7 +47,7 @@ TEST (election_scheduler, activate_one_flush) | |||
system.nodes[0]->ledger.process (system.nodes[0]->store.tx_begin_write (), *send1); | |||
system.nodes[0]->scheduler.activate (nano::dev::genesis_key.pub, system.nodes[0]->store.tx_begin_read ()); | |||
system.nodes[0]->scheduler.flush (); |
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 schedule flush can go to
* Fix tests using election_scheduler::flush * Fix more tests using `election_scheduler::flush` * Remove flush calls * One more flush removed
Small fix for a missing ASSERT_TIMELY