You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But if I set LTP_TIMEOUT_MUL=2 the ltp lib will multiply the set timeout e.g. -x 0.02*2.
So the test would run twice as long, or am I wrong?
I think mmap1 and maybe other tests misuse the timeout mechanism of ltp?
The text was updated successfully, but these errors were encountered:
This is known problem, timeout multiplication only increases tests runtime in this case and yes I do plan to introduce a new variable something as LTP_MAX_RUNTIME as currently there is no way how to set a test runtime for these testcases.
I've send a patchset that attempts to fix this issue http://patchwork.ozlabs.org/project/ltp/list/?series=247935 I guess that there will be some changes needed before it could be applied but it should show the direction where this is heading to.
Hello!
For me it looks like mmap1 executes its test until the test reaches the set timeout.
mmap1 will stop its execution if only n seconds are remaining until timeout.
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/mem/mtest06/mmap1.c#L228
The test argument -x 0.02 changes the test timeout.
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/mem/mtest06/mmap1.c#L219
But if I set LTP_TIMEOUT_MUL=2 the ltp lib will multiply the set timeout e.g. -x 0.02*2.
So the test would run twice as long, or am I wrong?
I think mmap1 and maybe other tests misuse the timeout mechanism of ltp?
The text was updated successfully, but these errors were encountered: