[LTP] [RFC PATCH] starvation: set a baseline for maximum runtime

Li Wang liwang@redhat.com
Wed Nov 27 11:56:06 CET 2024


On Wed, Nov 27, 2024 at 6:40 PM Cyril Hrubis <chrubis@suse.cz> wrote:

> Hi!
> > After thinking it over, I guess we'd better _only_ apply this method
> > to some special slow tests (aka. more easily timeout tests). If we do
> > the examination of those kernel options in the library for all, that
> > maybe a burden to most quick tests, which always finish in a few
> > seconds (far less than the default 30s).
> >
> > Therefore, I came up with a new option for .max_runtime, which is
> > TST_DYNAMICAL_RUNTIME. Similar to the TST_UNLIMITED_RUNTIME
> > we ever use. Test by adding this .max_runtime = TST_DYNAIMCAL_RUNTIME
> > that will try to find a proper timeout value in the running time for the
> > test.
>
> I was thinking to only multiply the max_runtime defined by the test in
> the library. That way only slow tests that set the max_runtime would be
> affected.
>

Ok, that also indicates the test is slower. I will apply that to non-zero
'.max_runtime'
tests and resend a patch. Thanks!

-- 
Regards,
Li Wang


More information about the ltp mailing list