← Back to team overview

canonical-ubuntu-qa team mailing list archive

[Bug 2037027] [NEW] memcg_max_usage_in_bytes from controllers in LTP failed with TBROK: timed out on memory.usage_in_bytes

 

Public bug reported:

This is not a regression, found this issue with f/gcp-5.15
5.15.0-1043.51~20.04.1 on instance e2-highmem-16.

Test failed with:
memcg_usage_in_bytes_test 2 TBROK: timed out on memory.usage_in_bytes 131072 4202496 4194304

Test log:
INFO: Test start time: Fri Sep 15 12:47:18 UTC 2023
COMMAND:    /opt/ltp/bin/ltp-pan -q  -e -S   -a 163327     -n 163327  -f /tmp/ltp-K08Taudo2h/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_usage_in_bytes_test 1 TINFO: timeout per run is 0h 5m 0s
memcg_usage_in_bytes_test 1 TINFO: set /sys/fs/cgroup/memory/memory.use_hierarchy to 0 failed
memcg_usage_in_bytes_test 1 TINFO: Test memory.usage_in_bytes
memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304
memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 163420
memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 163420
memcg_usage_in_bytes_test 1 TPASS: memory.usage_in_bytes is 4202496-4337664 as expected
memcg_usage_in_bytes_test 2 TINFO: Test memory.memsw.usage_in_bytes
memcg_usage_in_bytes_test 2 TPASS: echo 8388608 > memory.limit_in_bytes passed as expected
memcg_usage_in_bytes_test 2 TPASS: echo 8388608 > memory.memsw.limit_in_bytes passed as expected
memcg_usage_in_bytes_test 2 TINFO: Running memcg_process --mmap-anon -s 4194304
memcg_usage_in_bytes_test 2 TINFO: Warming up pid: 163439
memcg_usage_in_bytes_test 2 TINFO: Process is still here after warm up: 163439
memcg_usage_in_bytes_test 2 TPASS: memory.memsw.usage_in_bytes is 4202496-4337664 as expected
memcg_usage_in_bytes_test 2 TBROK: timed out on memory.usage_in_bytes 131072 4202496 4194304
memcg_usage_in_bytes_test 2 TINFO: AppArmor enabled, this may affect test results
memcg_usage_in_bytes_test 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root)
memcg_usage_in_bytes_test 2 TINFO: loaded AppArmor profiles: none

Summary:
passed   4
failed   0
broken   1
skipped  0
warnings 0
INFO: ltp-pan reported some tests FAIL
LTP Version: 20230516
INFO: Test end time: Fri Sep 15 12:47:31 UTC 2023


The test passed after retest, looks like it's flaky.

** Affects: ubuntu-kernel-tests
     Importance: Undecided
         Status: New


** Tags: 5.15 focal sru-20230904 ubuntu-ltp-controllers

-- 
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2037027

Title:
   memcg_max_usage_in_bytes from controllers in LTP failed with TBROK:
  timed out on memory.usage_in_bytes

Status in ubuntu-kernel-tests:
  New

Bug description:
  This is not a regression, found this issue with f/gcp-5.15
  5.15.0-1043.51~20.04.1 on instance e2-highmem-16.

  Test failed with:
  memcg_usage_in_bytes_test 2 TBROK: timed out on memory.usage_in_bytes 131072 4202496 4194304

  Test log:
  INFO: Test start time: Fri Sep 15 12:47:18 UTC 2023
  COMMAND:    /opt/ltp/bin/ltp-pan -q  -e -S   -a 163327     -n 163327  -f /tmp/ltp-K08Taudo2h/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_usage_in_bytes_test 1 TINFO: timeout per run is 0h 5m 0s
  memcg_usage_in_bytes_test 1 TINFO: set /sys/fs/cgroup/memory/memory.use_hierarchy to 0 failed
  memcg_usage_in_bytes_test 1 TINFO: Test memory.usage_in_bytes
  memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304
  memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 163420
  memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 163420
  memcg_usage_in_bytes_test 1 TPASS: memory.usage_in_bytes is 4202496-4337664 as expected
  memcg_usage_in_bytes_test 2 TINFO: Test memory.memsw.usage_in_bytes
  memcg_usage_in_bytes_test 2 TPASS: echo 8388608 > memory.limit_in_bytes passed as expected
  memcg_usage_in_bytes_test 2 TPASS: echo 8388608 > memory.memsw.limit_in_bytes passed as expected
  memcg_usage_in_bytes_test 2 TINFO: Running memcg_process --mmap-anon -s 4194304
  memcg_usage_in_bytes_test 2 TINFO: Warming up pid: 163439
  memcg_usage_in_bytes_test 2 TINFO: Process is still here after warm up: 163439
  memcg_usage_in_bytes_test 2 TPASS: memory.memsw.usage_in_bytes is 4202496-4337664 as expected
  memcg_usage_in_bytes_test 2 TBROK: timed out on memory.usage_in_bytes 131072 4202496 4194304
  memcg_usage_in_bytes_test 2 TINFO: AppArmor enabled, this may affect test results
  memcg_usage_in_bytes_test 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root)
  memcg_usage_in_bytes_test 2 TINFO: loaded AppArmor profiles: none

  Summary:
  passed   4
  failed   0
  broken   1
  skipped  0
  warnings 0
  INFO: ltp-pan reported some tests FAIL
  LTP Version: 20230516
  INFO: Test end time: Fri Sep 15 12:47:31 UTC 2023


  The test passed after retest, looks like it's flaky.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2037027/+subscriptions