01/06/2026 12:23, Luca Boccassi: > On Sun, 31 May 2026 at 19:01, Stephen Hemminger > <[email protected]> wrote: > > > > The forwarding loop was bounded by a fixed interval of 0.5ms > > but on slow or emulated platforms with a low-frequency timebase > > (e.g. RISC-V rdtime) this fails because the loop only ran once. > > The test needs two iterations to get any samples. > > > > Rearrange the forwarding loop so that a minimum number of iterations > > are required. The loop still has an upper bound on packets and time > > interval which is expanded to 10 ms. > > > > If no samples are collected, mark the test as skipped. > > Refactor the forwarding loop test so that cleanup happens on > > failure. > > > > Reported-by: Luca Boccassi <[email protected]> > > Fixes: b34508b9cbcd ("test/latency: update with more checks") > > Cc: [email protected] > > > > Signed-off-by: Stephen Hemminger <[email protected]> > > --- > > app/test/test_latencystats.c | 75 ++++++++++++++++++++++-------------- > > 1 file changed, 46 insertions(+), 29 deletions(-) > > Thanks, this has been failing consistently in riscv64 since at least > 25.11, hopefully this makes it stable. > > Acked-by: Luca Boccassi <[email protected]>
Applied, thanks.

