On Mon, Sep 19, 2022 at 11:27 AM Li Wang <liwang@redhat.com> wrote:

>
>
> On Mon, Sep 19, 2022 at 11:14 AM Petr Vorel <pvorel@suse.cz> wrote:
>
>> Hi all,
>>
>> > ## Build
>> > * kernel: 5.18.19
>> > * git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
>> > * git branch: linux-5.18.y
>> > * git commit: 22a992953741ad79c07890d3f4104585e52ef26b
>> > * git describe: cea142b
>> > * test details: https://qa-reports.linaro.org/lkft/ltp/build/cea142b
>>
>> > ## Test Regressions (compared to 98140f3)
>> > * qemu_i386, ltp-controllers
>> >   - cpuacct_100_100
>>
>> > * qemu_x86_64, ltp-cve
>> >   - cve-2018-1000204
>> OK, 3252ea38d ("ioctl_sg01: Add max_runtime") didn't help.
>>
>> looking at the log [1] I don't see anything obvious why test timeouts:
>>
>
> tst_pollute_memory() consume time is proportional to the amount of
> free RAM, it is hard to find one fixed value of max_runtime to fit all test
> platforms.
>
> From my experience, if you limited this test only run with small
> machine (e.g. RAM <= 32G), that performs well with whatever
> bare metal or VM, no timeout ever.
>

Btw, we did that by setting a test filter before LTP running, also we could
add a field .max_mem_avail to tst_test struct for achieving that, but not
sure if it's worth doing that at this moment.

-- 
Regards,
Li Wang