The condition to execute that part was always evaluating to false because it compared a scheduler type with a priority. The actual test case is invalid because even for a real-time thread with the highest priority there is no guarantee that it executes at least once between the start and stop call.
@snrkiwi You added this test case in 2011. Is this something you would expect from RTT? Maybe the test would have worked back then, but a later update changed the behavior of start() in this case and this was not detected due to the wrong comparison?
The condition to execute that part was always evaluating to false because it compared a scheduler type with a priority. The actual test case is invalid because even for a real-time thread with the highest priority there is no guarantee that it executes at least once between the start and stop call.
@snrkiwi You added this test case in 2011. Is this something you would expect from RTT? Maybe the test would have worked back then, but a later update changed the behavior of
start()in this case and this was not detected due to the wrong comparison?