On 21 August 2018 at 18:57, Rafael David Tinoco rafael.tinoco@linaro.org wrote:
On Tue, Aug 21, 2018 at 10:49:46AM +0000, Linaro QA wrote:
Summary
kernel: 4.18.0 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git git branch: master git commit: 6b2edf27fe26c73cd67b6bf5ffb23dce882e1455 git describe: v4.18-10981-g6b2edf27fe26 Test details: https://qa-reports.linaro.org/lkft/linux-mainline-oe/build/v4.18-10981-g6b2e...
Regressions (compared to build v4.18-10721-g2ad0d5269970)
dragonboard-410c - arm64: ltp-cve-tests: * cve-2014-0196 * runltp_cve
cve-2014-0196.c:103: INFO: Attempting to overflow into a tty_struct... Test timeouted, sending SIGKILL!
15 mins not enough for this CVE test for qemu and x15 (slowest envs). Should we raise the timeout ? this is a cve related to a race condition on tty creation.
I have seen this cases and increased timeout to 45 minutes to single CVE test on x15 and qemu and the test did not finish.
We can not allocate more than 15 minutes timeout of each test case. you may ignore CVE timeouts on slow machines.
* test src: git://github.com/linux-test-project/ltp.gitltp-hugetlb-tests: * hugemmap06 * runltp_hugetlb
looks like mmap06 never ran. I can see hugemmap05 and hugeshmat01 right after.
That's interesting part in LTP execution.
It run but did not shows it's name tst_test.c:1015: INFO: Timeout per run is 0h 15m 00s mem.c:839: INFO: set nr_hugepages to 255 mem.c:848: BROK: nr_hugepages = 236, but expect 255 mem.c:839: INFO: set nr_hugepages to 0
The way i find test execution flow is from "runtest/hugetlb" file
hugemmap05 hugemmap05 hugemmap06 hugemmap06 hugemmap05_1 hugemmap05 -m hugemmap05_2 hugemmap05 -s hugemmap05_3 hugemmap05 -s -m
hugeshmat01 hugeshmat01 -i 5
hugemmap06 is an intermittent failure on db410c due to timeout after 15 minutes. https://qa-reports.linaro.org/lkft/linux-mainline-oe/tests/ltp-hugetlb-tests...
- Naresh