[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
> 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.
> 
> 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.

This is exactly the reason why I want to have queries on metadata
available in kirk, e.g. "filter out all tests that have runtime >
$some_constant".

-- 
Cyril Hrubis
chrubis@suse.cz