Public bug reported:
Testcases
memcg_failcnt|memcg_max_usage_in_bytes|memcg_subgroup_charge|memcg_usage_in_byte
from ubuntu_ltp_controllers are failing with focal/linux-lowlatency-5.15
5.15.0-41.44~20.04.1 flavor lowlatency-64k.
memcg_failcnt 1 TINFO: timeout per run is 0h 5m 0s
memcg_failcnt 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_failcnt 1 TINFO: Setting shmmax
memcg_failcnt 1 TINFO: Running memcg_process --mmap-anon -s 0
memcg_failcnt 1 TPASS: memory.failcnt is 36, > 0 as expected
memcg_failcnt 2 TINFO: Running memcg_process --mmap-file -s 0
memcg_process: mmap(file) failed: Invalid argument
memcg_failcnt 2 TFAIL: memory.failcnt is 0, <= 0 expected
memcg_failcnt 3 TINFO: Running memcg_process --shm -s 0
memcg_failcnt 3 TPASS: memory.failcnt is 36, > 0 as expected
memcg_failcnt 4 TINFO: AppArmor enabled, this may affect test results
memcg_failcnt 4 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires
super/root)
memcg_failcnt 4 TINFO: loaded AppArmor profiles: none
This doesn't seem to be a regression as this test is failing on other
combinations of architectures/flavors with bug 1949532.
** Affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => Confirmed
** Summary changed:
- memcg_failcnt from ubuntu_ltp_controllers fails on Focal 5.15
+ memcg_failcnt/memcg_max_usage_in_bytes from ubuntu_ltp_controllers fails on
Focal 5.15
** Summary changed:
- memcg_failcnt/memcg_max_usage_in_bytes from ubuntu_ltp_controllers fails on
Focal 5.15
+ memcg_* from ubuntu_ltp_controllers fails on Focal 5.15 with mmap (Invalid
argument)
** Description changed:
- ubuntu_ltp_controllers.memcg_failcnt is failing with focal/linux-
- lowlatency-5.15 5.15.0-41.44~20.04.1 flavor lowlatency-64k.
+ Testcases
+
memcg_failcnt|memcg_max_usage_in_bytes|memcg_subgroup_charge|memcg_usage_in_byte
+ from ubuntu_ltp_controllers are failing with focal/linux-lowlatency-5.15
+ 5.15.0-41.44~20.04.1 flavor lowlatency-64k.
memcg_failcnt 1 TINFO: timeout per run is 0h 5m 0s
memcg_failcnt 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_failcnt 1 TINFO: Setting shmmax
memcg_failcnt 1 TINFO: Running memcg_process --mmap-anon -s 0
memcg_failcnt 1 TPASS: memory.failcnt is 36, > 0 as expected
memcg_failcnt 2 TINFO: Running memcg_process --mmap-file -s 0
memcg_process: mmap(file) failed: Invalid argument
memcg_failcnt 2 TFAIL: memory.failcnt is 0, <= 0 expected
memcg_failcnt 3 TINFO: Running memcg_process --shm -s 0
memcg_failcnt 3 TPASS: memory.failcnt is 36, > 0 as expected
memcg_failcnt 4 TINFO: AppArmor enabled, this may affect test results
memcg_failcnt 4 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1
(requires super/root)
memcg_failcnt 4 TINFO: loaded AppArmor profiles: none
- Summary:
- passed 2
- failed 1
- broken 0
- skipped 0
- warnings 0
-
This doesn't seem to be a regression as this test is failing on other
combinations of architectures/flavors with bug 1949532.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981070
Title:
memcg_* from ubuntu_ltp_controllers fails on Focal 5.15 with mmap
(Invalid argument)
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Jammy:
Confirmed
Bug description:
Testcases
memcg_failcnt|memcg_max_usage_in_bytes|memcg_subgroup_charge|memcg_usage_in_byte
from ubuntu_ltp_controllers are failing with focal/linux-
lowlatency-5.15 5.15.0-41.44~20.04.1 flavor lowlatency-64k.
memcg_failcnt 1 TINFO: timeout per run is 0h 5m 0s
memcg_failcnt 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_failcnt 1 TINFO: Setting shmmax
memcg_failcnt 1 TINFO: Running memcg_process --mmap-anon -s 0
memcg_failcnt 1 TPASS: memory.failcnt is 36, > 0 as expected
memcg_failcnt 2 TINFO: Running memcg_process --mmap-file -s 0
memcg_process: mmap(file) failed: Invalid argument
memcg_failcnt 2 TFAIL: memory.failcnt is 0, <= 0 expected
memcg_failcnt 3 TINFO: Running memcg_process --shm -s 0
memcg_failcnt 3 TPASS: memory.failcnt is 36, > 0 as expected
memcg_failcnt 4 TINFO: AppArmor enabled, this may affect test results
memcg_failcnt 4 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1
(requires super/root)
memcg_failcnt 4 TINFO: loaded AppArmor profiles: none
This doesn't seem to be a regression as this test is failing on other
combinations of architectures/flavors with bug 1949532.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1981070/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
