diff mbox series

[PULL,03/17] tests/qtest: don't step clock at start of npcm7xx periodic IRQ test

Message ID 20250210161451.3273284-4-alex.bennee@linaro.org
State Accepted
Commit ff6c3b1a16ac2ee570447660526eea531d748396
Headers show
Series [PULL,01/17] tests/docker: replicate the check-rust-tools-nightly CI job | expand

Commit Message

Alex Bennée Feb. 10, 2025, 4:14 p.m. UTC 
Until there are timers enabled the semantics of clock_step_next() will
fail. Since d524441a36 (system/qtest: properly feedback results of
clock_[step|set]) we will signal a FAIL if time doesn't advance.

Reviewed-by: Hao Wu <wuhaotsh@google.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20250207153112.3939799-4-alex.bennee@linaro.org>
diff mbox series

Patch

diff --git a/tests/qtest/npcm7xx_timer-test.c b/tests/qtest/npcm7xx_timer-test.c
index 58f58c2f71..43711049ca 100644
--- a/tests/qtest/npcm7xx_timer-test.c
+++ b/tests/qtest/npcm7xx_timer-test.c
@@ -465,7 +465,6 @@  static void test_periodic_interrupt(gconstpointer test_data)
     int i;
 
     tim_reset(td);
-    clock_step_next();
 
     tim_write_ticr(td, count);
     tim_write_tcsr(td, CEN | IE | MODE_PERIODIC | PRESCALE(ps));