Only schedule OnRun callbacks right after construction in aos
OnRun is meant to be a place to do work right before the event loop
starts to run. On ShmEventLoop, this is the case, and restarting the
loop isn't all that well supported, so this doesn't make sense there
either. A lot of our tests have used this behavior since it was easy
and not disallowed.
A follow-up commit will explicitly dis-allow this behavior.
Change-Id: If50dcc0e737725129ef36cb27e07be774d96c691
Signed-off-by: James Kuszmaul <james.kuszmaul@bluerivertech.com>
diff --git a/aos/events/logging/realtime_replay_test.cc b/aos/events/logging/realtime_replay_test.cc
index 4118550..dd4aaf0 100644
--- a/aos/events/logging/realtime_replay_test.cc
+++ b/aos/events/logging/realtime_replay_test.cc
@@ -88,11 +88,10 @@
TEST_F(RealtimeLoggerTest, RealtimeReplay) {
{
- std::unique_ptr<EventLoop> logger_event_loop =
- event_loop_factory_.MakeEventLoop("logger");
-
event_loop_factory_.RunFor(std::chrono::milliseconds(95));
+ std::unique_ptr<EventLoop> logger_event_loop =
+ event_loop_factory_.MakeEventLoop("logger");
Logger logger(logger_event_loop.get());
logger.set_separate_config(false);
logger.set_polling_period(std::chrono::milliseconds(100));
@@ -123,11 +122,10 @@
// is included on a single node config
TEST_F(RealtimeLoggerTest, SingleNodeReplayChannels) {
{
- std::unique_ptr<EventLoop> logger_event_loop =
- event_loop_factory_.MakeEventLoop("logger");
-
event_loop_factory_.RunFor(std::chrono::milliseconds(95));
+ std::unique_ptr<EventLoop> logger_event_loop =
+ event_loop_factory_.MakeEventLoop("logger");
Logger logger(logger_event_loop.get());
logger.set_separate_config(false);
logger.set_polling_period(std::chrono::milliseconds(100));