memcg_stress in ubuntu_ltp_controllers timeout on node rumford with F-intel-5.13
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-kernel-tests |
In Progress
|
Undecided
|
Po-Hsu Lin |
Bug Description
Issue found on Focal Intel 5.13.0-1010.10 with node rumford.
INFO: Test start time: Fri Mar 18 01:17:36 UTC 2022
COMMAND: /opt/ltp/
LOG File: /dev/null
FAILED COMMAND File: /dev/null
TCONF COMMAND File: /dev/null
Running tests.......
memcg_stress_test 1 TINFO: timeout per run is 1h 10m 0s
memcg_stress_test 1 TINFO: Calculated available memory 35338 MB
memcg_stress_test 1 TINFO: Testing 150 cgroups, using 234 MB, interval 5
memcg_stress_test 1 TPASS: mkdir /dev/memcg passed as expected
memcg_stress_test 1 TPASS: mount -t cgroup -omemory memcg /dev/memcg passed as expected
memcg_stress_test 1 TINFO: Starting cgroups
memcg_stress_test 1 TINFO: Testing cgroups for 900s
memcg_stress_test 1 TINFO: Killing groups
Test timed out, sending SIGTERM!
If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1
memcg_stress_test 1 TBROK: test terminated
Test is still running... 10
memcg_stress_test 1 TPASS: umount /dev/memcg passed as expected
memcg_stress_test 1 TPASS: rmdir /dev/memcg passed as expected
Test is still running... 9
memcg_stress_test 1 TINFO: AppArmor enabled, this may affect test results
memcg_stress_test 1 TINFO: it can be disabled with TST_DISABLE_
Test is still running... 8
memcg_stress_test 1 TINFO: loaded AppArmor profiles: none
Summary:
passed 4
failed 0
broken 1
skipped 0
warnings 0
Test is still running... 7
Test is still running... 6
Test is still running... 5
Test is still running... 4
Test is still running... 3
Test is still running... 2
Test is still running... 1
Test is still running, sending SIGKILL
INFO: ltp-pan reported some tests FAIL
LTP Version: 20210927
INFO: Test end time: Fri Mar 18 04:26:11 UTC 2022
This can be reproduced on F-hwe-5.13 as well.
tags: | added: 5.13 focal intel ubuntu-ltp-controllers |
Tested on node rumford with LTP_TIMEOUT_MUL=3 (timeout 1h 45m 0s) and bump the test suite timeout from 75 min to 2h. It appears that this test will pass on it.