memcg_max_usage_in_bytes from controllers in LTP failed with TFAIL: memory.max_usage_in_bytes is 4456448, 4206592-4341760 expected

Bug #2016957 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
New
Undecided
Unassigned

Bug Description

This test seems to be a bit flaky, issue found with focal/linux-lowlatency-hwe-5.15/5.15.0-70.77~20.04.1 on node riccioli.

INFO: Test start time: Tue Apr 11 07:36:29 UTC 2023
COMMAND: /opt/ltp/bin/ltp-pan -q -e -S -a 161804 -n 161804 -f /tmp/ltp-PRgphNVxJK/alltests -l /dev/null -C /dev/null -T /dev/null
LOG File: /dev/null
FAILED COMMAND File: /dev/null
TCONF COMMAND File: /dev/null
Running tests.......
memcg_max_usage_in_bytes_test 1 TINFO: timeout per run is 0h 5m 0s
memcg_max_usage_in_bytes_test 1 TINFO: set /sys/fs/cgroup/memory/memory.use_hierarchy to 0 failed
memcg_max_usage_in_bytes_test 1 TINFO: Test memory.max_usage_in_bytes
memcg_max_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304
memcg_max_usage_in_bytes_test 1 TINFO: Warming up pid: 161889
memcg_max_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 161889
memcg_max_usage_in_bytes_test 1 TPASS: memory.max_usage_in_bytes is 4206592-4341760 as expected
memcg_max_usage_in_bytes_test 2 TINFO: Test memory.memsw.max_usage_in_bytes
memcg_max_usage_in_bytes_test 2 TPASS: echo 8388608 > memory.limit_in_bytes passed as expected
memcg_max_usage_in_bytes_test 2 TPASS: echo 8388608 > memory.memsw.limit_in_bytes passed as expected
memcg_max_usage_in_bytes_test 2 TINFO: Running memcg_process --mmap-anon -s 4194304
memcg_max_usage_in_bytes_test 2 TINFO: Warming up pid: 161907
memcg_max_usage_in_bytes_test 2 TINFO: Process is still here after warm up: 161907
memcg_max_usage_in_bytes_test 2 TPASS: memory.memsw.max_usage_in_bytes is 4206592-4341760 as expected
memcg_max_usage_in_bytes_test 3 TINFO: Test reset memory.max_usage_in_bytes
memcg_max_usage_in_bytes_test 3 TINFO: Running memcg_process --mmap-anon -s 4194304
memcg_max_usage_in_bytes_test 3 TINFO: Warming up pid: 161925
memcg_max_usage_in_bytes_test 3 TINFO: Process is still here after warm up: 161925
memcg_max_usage_in_bytes_test 3 TFAIL: memory.max_usage_in_bytes is 4456448, 4206592-4341760 expected
memcg_max_usage_in_bytes_test 3 TPASS: memory.max_usage_in_bytes is 0-135168 as expected
memcg_max_usage_in_bytes_test 4 TINFO: Test reset memory.memsw.max_usage_in_bytes
memcg_max_usage_in_bytes_test 4 TPASS: echo 8388608 > memory.limit_in_bytes passed as expected
memcg_max_usage_in_bytes_test 4 TPASS: echo 8388608 > memory.memsw.limit_in_bytes passed as expected
memcg_max_usage_in_bytes_test 4 TINFO: Running memcg_process --mmap-anon -s 4194304
memcg_max_usage_in_bytes_test 4 TINFO: Warming up pid: 162008
memcg_max_usage_in_bytes_test 4 TINFO: Process is still here after warm up: 162008
memcg_max_usage_in_bytes_test 4 TPASS: memory.memsw.max_usage_in_bytes is 4206592-4341760 as expected
memcg_max_usage_in_bytes_test 4 TPASS: memory.memsw.max_usage_in_bytes is 0-135168 as expected
memcg_max_usage_in_bytes_test 5 TINFO: AppArmor enabled, this may affect test results
memcg_max_usage_in_bytes_test 5 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root)
memcg_max_usage_in_bytes_test 5 TINFO: loaded AppArmor profiles: none

Summary:
passed 9
failed 1
broken 0
skipped 0
warnings 0
INFO: ltp-pan reported some tests FAIL
LTP Version: 20220527
INFO: Test end time: Tue Apr 11 07:36:37 UTC 2023

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.