<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:small"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 19, 2022 at 11:14 AM Petr Vorel <<a href="mailto:pvorel@suse.cz">pvorel@suse.cz</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,<br>
<br>
> ## Build<br>
> * kernel: 5.18.19<br>
> * git: <a href="https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc" rel="noreferrer" target="_blank">https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc</a><br>
> * git branch: linux-5.18.y<br>
> * git commit: 22a992953741ad79c07890d3f4104585e52ef26b<br>
> * git describe: cea142b<br>
> * test details: <a href="https://qa-reports.linaro.org/lkft/ltp/build/cea142b" rel="noreferrer" target="_blank">https://qa-reports.linaro.org/lkft/ltp/build/cea142b</a><br>
<br>
> ## Test Regressions (compared to 98140f3)<br>
> * qemu_i386, ltp-controllers<br>
>   - cpuacct_100_100<br>
<br>
> * qemu_x86_64, ltp-cve<br>
>   - cve-2018-1000204<br>
OK, 3252ea38d ("ioctl_sg01: Add max_runtime") didn't help.<br>
<br>
looking at the log [1] I don't see anything obvious why test timeouts:<br></blockquote><div><br></div><div><div class="gmail_default" style="font-size:small">tst_pollute_memory() consume time is proportional to the amount of</div><div class="gmail_default" style="font-size:small">free RAM, it is hard to find one fixed value of max_runtime to fit all test</div><div class="gmail_default" style="font-size:small">platforms.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">From my experience, if you limited this test only run with small</div><div class="gmail_default" style="font-size:small">machine (e.g. RAM <= 32G), that performs well with whatever</div><div class="gmail_default" style="font-size:small">bare metal or VM, no timeout ever.</div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
tst_test.c:1524: TINFO: Timeout per run is 0h 00m 30s<br>
ioctl_sg01.c:81: TINFO: Found SCSI device /dev/sg1<br>
Test timeouted, sending SIGKILL!<br>
tst_test.c:1575: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1<br>
tst_test.c:1577: TBROK: Test killed! (timeout?)<br>
<br>
Summary:<br>
passed   0<br>
failed   0<br>
broken   1<br>
skipped  0<br>
warnings 0<br>
<br>
@lkft I haven't find dmesg after starting running tests in the test details [2].<br>
Is there any? I really like you keep the history [3], thanks! It'd be great if<br>
you could print the test name into dmesg, so that it can be visible which test<br>
caused particular message / kernel oops.<br>
<br>
Also, it'd be great if you could put some header for each test with the test<br>
name or at least blank line to separate the end of the summary.<br>
<br>
Kind regards,<br>
Petr<br>
<br>
[1] <a href="https://qa-reports.linaro.org/lkft/ltp/build/cea142b/testrun/11956785/suite/ltp-cve/test/cve-2018-1000204/log" rel="noreferrer" target="_blank">https://qa-reports.linaro.org/lkft/ltp/build/cea142b/testrun/11956785/suite/ltp-cve/test/cve-2018-1000204/log</a><br>
[2] <a href="https://qa-reports.linaro.org/lkft/ltp/build/cea142b/testrun/11956785/suite/ltp-cve/test/cve-2018-1000204/details/" rel="noreferrer" target="_blank">https://qa-reports.linaro.org/lkft/ltp/build/cea142b/testrun/11956785/suite/ltp-cve/test/cve-2018-1000204/details/</a><br>
[3] <a href="https://qa-reports.linaro.org/lkft/ltp/build/cea142b/testrun/11956785/suite/ltp-cve/test/cve-2018-1000204/history/" rel="noreferrer" target="_blank">https://qa-reports.linaro.org/lkft/ltp/build/cea142b/testrun/11956785/suite/ltp-cve/test/cve-2018-1000204/history/</a><br>
<br>
<br>
> ## Metric Regressions (compared to 98140f3)<br>
> No metric regressions found.<br>
<br>
> Reported-by: Linux Kernel Functional Testing <<a href="mailto:lkft@linaro.org" target="_blank">lkft@linaro.org</a>><br>
<br>
<br>
> ## Test Fixes (compared to 98140f3)<br>
> * qemu_arm64, ltp-controllers<br>
>   - cpuacct_100_100<br>
<br>
<br>
> ## Metric Fixes (compared to 98140f3)<br>
> No metric fixes found.<br>
<br>
> ## Test result summary<br>
> total: 12630, pass: 10739, fail: 161, skip: 1730, xfail: 0<br>
<br>
> ## Build Summary<br>
<br>
> ## Test suites summary<br>
> * log-parser-boot<br>
> * log-parser-test<br>
> * ltp-cap_bounds<br>
> * ltp-commands<br>
> * ltp-containers<br>
> * ltp-controllers<br>
> * ltp-cpuhotplug<br>
> * ltp-crypto<br>
> * ltp-cve<br>
> * ltp-dio<br>
> * ltp-fcntl-locktests<br>
> * ltp-filecaps<br>
> * ltp-fs<br>
> * ltp-fs_bind<br>
> * ltp-fs_perms_simple<br>
> * ltp-fsx<br>
> * ltp-hugetlb<br>
> * ltp-io<br>
> * ltp-ipc<br>
> * ltp-math<br>
> * ltp-mm<br>
> * ltp-nptl<br>
> * ltp-pty<br>
> * ltp-sched<br>
> * ltp-securebits<br>
> * ltp-syscalls<br>
> * ltp-tracing<br>
<br>
-- <br>
Mailing list info: <a href="https://lists.linux.it/listinfo/ltp" rel="noreferrer" target="_blank">https://lists.linux.it/listinfo/ltp</a><br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Regards,<br></div><div>Li Wang<br></div></div></div></div>