[LTP] [RFC PATCh] lib: redefine the overall timeout logic of test

[Cyril Hrubis]

Hi!
> > Btw, we have some tests that implicitly invoke tst_remaining_runtime,
> > for example, using the fuzzy_sync library, which also needs .runtime
> > but not .timeout.
> >
> 
> Also, tests that use 'test.runtime' directly (e.g. readahead02.c,
> set_mempolicy01.c)
> must continue to be marked as using .runtime.

I think that readahead02 is a case where we should switch to timeout
because that is exactly the situation where want the timeout to be
multiplied when the system is slower. The way the test adjust the
runtime dynamically is wrong anyways, because it increases the timeout
for each iteration. We should just put the worstcase runtime into the
.timeout instead.

And similarily for the the mempolicy it looks like we should set the
timeout dynamicaly in the testup with tst_set_timeout() instead of
runtime.

-- 
Cyril Hrubis
chrubis@suse.cz