Re: [LTP] [PATCH V3] lib: multiply the max_runtime if detect slow kconfigs

Petr Vorel
2024-12-19T12:54:24Z

Hi Li,

...
> +++ b/lib/tst_test.c
> @@ -555,6 +555,9 @@ static int multiply_runtime(int max_runtime)

> parse_mul(&runtime_mul, "LTP_RUNTIME_MUL", 0.0099, 100);

> + if (tst_has_slow_kconfig())
> + max_runtime *= 4;

FYI this change prolongs some fuzzy sync tests, e.g. setsockopt06 or writev03.
I guess this is a side effect, or not? Or does slow machine really needs to run
longer in order to trigger bug in fuzzy sync?

We have 900 sec timeout in openQA (default LTP timeout is 600 sec), but it's not enough.
Sure, the solution is to increase it to 2400 (4*600), but then we need really to
have more precise .max_runtime setup otherwise tests which got stuck will
prolong testing 4x times.

This is for syscalls, I haven't checked other runtests (specially these which
have high .max_runtime, e.g. ltp-aio-stress).

Kind regards,
Petr