On Wed, Jul 10, 2024 at 02:04:55PM +0100, Mark Brown wrote:
# # RUN rtc.date_read_loop ... # # rtctest.c:95:date_read_loop:Continuously reading RTC time for 30s (with 11ms breaks after every read). # # rtctest.c:122:date_read_loop:Performed 2954 RTC time reads. # # OK rtc.date_read_loop
Bisection points to "selftests/harness: Fix tests timeout and race condition" but this looks like a test bug, the timeout for tests is 30s and the test tries to run for 30s which obviously doesn't add up. Previously the test would pass because the bug the patch is fixing is that timeout had no effect. I'm also running the test on other platforms without it triggering new timeouts, it's just this one specific platform that triggered which is a bit worrying.
I'll send a patch for the test.
Sorry, spoke too soon on that - the test is explicitly overriding the timeout to be longer so there's something else going on here.