tests: timer_behavior: fix a period drift logic error
An assertion statement was a bit too strict. Period drift may come about not only from kernel ticks being large but also from time conversion being inexact due to division truncation. Fixes: #55136 Signed-off-by: Nicolas Pitre <npitre@baylibre.com>
This commit is contained in:
parent
c51744c6ee
commit
b2e204e9a6
1 changed files with 3 additions and 3 deletions
|
@ -171,10 +171,10 @@ ZTEST(timer_jitter_drift, test_jitter_drift)
|
|||
TC_PRINT("test timer period (%u us) is smaller than "
|
||||
"system tick period (%u us):\n",
|
||||
CONFIG_TIMER_TEST_PERIOD, k_ticks_to_us_near32(1));
|
||||
TC_PRINT(" expected period drift %.8g us\n", expected_period_drift);
|
||||
zassert_true(expected_period_drift != 0.0);
|
||||
} else {
|
||||
zassert_true(expected_period_drift == 0.0);
|
||||
}
|
||||
if (expected_period_drift != 0.0) {
|
||||
TC_PRINT("expected period drift: %.8g us\n", expected_period_drift);
|
||||
}
|
||||
TC_PRINT("period duration statistics for %d samples (%u rollovers):\n",
|
||||
CONFIG_TIMER_TEST_SAMPLES - periodic_rollovers, periodic_rollovers);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue