[LTP] [RFC] Reduce .runtime for Long-Running Tests ?

[Cyril Hrubis]

Hi!
> After reviewing some LTP HTML test reports, I noticed that the ten tests
> alone take nearly 20 minutes to complete. For example:
> 
> --------------------
> bind06           300.15s
> msgstress01      180.44s

Isn't this better after:

commit e3b85e50471b3892316a2b2c7c730e9dc8d9139e
Author: Ricardo B. Marlière <rbm@suse.com>
Date:   Wed May 21 05:31:12 2025 -0300

    syscalls/msgstress01: Set upper bound for num_messages


> fsx22            170.47s
> pty07            150.04s
> pty06            150.02s
> gf18             121.09s
> gf17             120.82s
> gf16             120.13s
> dirtyc0w_shmem   120.11s
> setsockopt07      76.47s

As Peter pointed out, most of these are fuzzy sync tests and the runtime
is callibrated in order to get reasonable chance of reproducing the
results. But indeed the runtime does not scale with the speed of the
machine and we are not setting the pair exec_loops in the tests that run
for so long, so I suppose that callibrating the number of loops for
these tests that does not make the bug less reproducible would make
things better.

-- 
Cyril Hrubis
chrubis@suse.cz