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

[Li Wang]

On Tue, May 27, 2025 at 7:00 PM Li Wang <liwang@redhat.com> wrote:
>
> Hello All,
>
> 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
> 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
>
> In total, running the full ltp-lite suite currently takes ~1h20m, which is a bit
> long for CI or pre-merge validation pipelines.

Forget to mention:

The 1h20min contains LTP compiling time. We now try to build rpm package
for our CI testing that would reduce some unnecessary time.

Apart from that, If we could do something to speed up the running time,
that would be great too.

>
> I'm wondering whether all these .runtime values are truly necessary to reproduce
> the intended issues (e.g., race conditions, fuzzing, sync timing issues).
> Or if we could:
>  - Set a lower threshold for .runtime on general-purpose stress/fuzz tests
>  - Introduce a runtime _policy_ for different environments (e.g., fast
> CI vs. full weekly runs)
>
> It might be beneficial to revisit the .runtime values of long-running tests and
> set a minimal yet effective duration that balances reproducibility with resource
> efficiency. This could help save time and free up test resources earlier.
>
> Any thoughts/comments would be appreciated.
>
> --
> Regards,
> Li Wang



-- 
Regards,
Li Wang