From e999075ac74c9c6bb0342f22c907079837072678 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beat=20K=C3=BCng?= Date: Thu, 7 Mar 2019 10:38:00 +0100 Subject: [PATCH] lockstep_scheduler: fix system_sleep -> system_usleep The effect was that threads that tried to exit were unnecessarily kept running. This did not cause problems except for increased resource usage. --- .../include/lockstep_scheduler/lockstep_scheduler.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/platforms/posix/src/lockstep_scheduler/include/lockstep_scheduler/lockstep_scheduler.h b/platforms/posix/src/lockstep_scheduler/include/lockstep_scheduler/lockstep_scheduler.h index 5a3d73f0c5..10c084aa4b 100644 --- a/platforms/posix/src/lockstep_scheduler/include/lockstep_scheduler/lockstep_scheduler.h +++ b/platforms/posix/src/lockstep_scheduler/include/lockstep_scheduler/lockstep_scheduler.h @@ -26,7 +26,7 @@ private: // we need to wait until it's removed. while (!removed) { #ifndef UNIT_TESTS // unit tests don't define system_usleep and execute faster w/o sleeping here - system_sleep(5000); + system_usleep(5000); #endif } }