[LTP] [PATCH V3] lib: multiply the max_runtime if detect slow kconfigs
Petr Vorel
pvorel@suse.cz
Thu Dec 19 14:25:15 CET 2024
> On Thu, Dec 19, 2024 at 9:19 PM Cyril Hrubis <chrubis@suse.cz> wrote:
> > Hi!
> > > > Sounds like we need to have two different runtime values in the tests,
> > > > max_runtime which is the timeout for the test and just runtime which is
> > > > for how long will the test loop.
> > > Agree, if we define the looping runtime in a separate value, that would
> > be
> > > helpful.
> > There was a problem with having the two different values in a single
> > variable before as well. We do have the LTP_RUNTIME_MUL which multiplied
> > both the timeout and runtime. These should be separate multipliers as
> > well which multiplied both the timeout and runtime. These should be
> > separate multipliers as well.
> I noticed that tests using max_runtime to control the test time
> always use another function tst_remaining_runtime(), so maybe
> we can utilize this to bypass that.
> Later I will look into details, now I have a meeting in the coming 2h.
> @Petr, @Martin, Feel free to revert the two patches if you needed.
> 2da30df24e676d5f4cfcf0b11674cbdf11a19b8a
> 64e11fec079480179aa9473ae5e1e8ad78ef9ac3
Thanks. OK, we can wait a bit (few days) until revert. There will be Xmas, thus
not much busy time for us.
Kind regards,
Petr
> > --
> > Cyril Hrubis
> > chrubis@suse.cz
More information about the ltp
mailing list