tests: drivers: counter: counter_basic_api: allow equality in assert

ABOSTM · carlescufi · commit b2a7397a170a · 2020-05-18T19:13:04.000+02:00
Since introduction of #24374 this test fails on STM32 boards. Due to 1Hz frequency of RTC used, the 'diff' could be 0. But then 'counter_us_to_ticks(dev, processing_limit_us)' is also 0. We should allow the equality in the assert. Signed-off-by: Alexandre Bourdiol <alexandre.bourdiol@st.com>
diff --git a/tests/drivers/counter/counter_basic_api/src/test_counter.c b/tests/drivers/counter/counter_basic_api/src/test_counter.c
@@ -276,7 +276,7 @@ static void alarm_handler(struct device *dev, u8_t chan_id, u32_t counter,
 			(counter + top - now) : (counter - now);
 	}
 
-	zassert_true(diff < counter_us_to_ticks(dev, processing_limit_us),
+	zassert_true(diff <= counter_us_to_ticks(dev, processing_limit_us),
 			"Unexpected distance between reported alarm value(%u) "
 			"and actual counter value (%u), top:%d (processing "
 			"time limit (%d us) might be exceeded?",

Original file line number	Diff line number	Diff line change
`@@ -276,7 +276,7 @@ static void alarm_handler(struct device *dev, u8_t chan_id, u32_t counter,`
`276`	`276`	`(counter + top - now) : (counter - now);`
`277`	`277`	`}`
`278`	`278`
`279`		`- zassert_true(diff < counter_us_to_ticks(dev, processing_limit_us),`
	`279`	`+ zassert_true(diff <= counter_us_to_ticks(dev, processing_limit_us),`
`280`	`280`	`"Unexpected distance between reported alarm value(%u) "`
`281`	`281`	`"and actual counter value (%u), top:%d (processing "`
`282`	`282`	`"time limit (%d us) might be exceeded?",`