On Sun, Jan 12, 2025 at 04:07:04PM +0100, Niels Thykier wrote: > > 112s FAILED tests/unit/test_clock_freq.py::test_elapsed_time_between_tick - > > assert... > > 112s ==== 1 failed, 610 passed, 106 skipped, 93 deselected, 2 xfailed in > > 28.04s ===== > > > Some options include: > * Skipping the concrete test > * Changing the limits to make it less likely (though at some point, > the extra leeway will invalidate the test) > * Mark the autopkgtests as flaky, which will make the test less likely > in catching regression.
The packaging was already trying to skip that test (#929697), but the test was renamed upstream some time ago and so the exclusion was no longer effective. I'll update it. -- Colin Watson (he/him) [cjwat...@debian.org]
