mirrors/systemd
0
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-11-24 02:33:36 +08:00
Code Issues Packages Projects Releases Wiki Activity

test: adjust MemoryHigh= on oomd extended test units

Browse Source 
On some runs `sleep infinity` run by the user manager uses over 3M of
memory, which is higher than the MemoryHigh= set on testbloat and
testmunch. If no pgscan is generated, then systemd-oomd sorts by memory
usage which leads to a situation where testchill (using 3M) could be
targeted over testbloat (1M-2M).

Fix this by setting reasonable MemoryHigh= values for all of these test
units. Even if somehow testchill throttles a bit at 3M, testbloat and
testmunch should still be trying to use over 100M at memory and will
throttle down to 5M and 6M with the new values. This should reflect
the desired state in pgscan and memory usage during the test run.

Fixes #21684
This commit is contained in:
Anita Zhang 2021-12-17 04:19:53 -08:00 committed by Frantisek Sumsal
parent 641e2124de
commit 415d7d774a
3 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
test/units/testsuite-55-testbloat.service
View File

@ -5,6 +5,6 @@ Description=Create a lot of memory pressure
[Service]
# A VERY small memory.high will cause the script (trying to use a lot of memory)
# to throttle and be put under heavy pressure.
MemoryHigh=1M
MemoryHigh=5M
Slice=testsuite-55-workload.slice
ExecStart=/usr/lib/systemd/tests/testdata/units/testsuite-55-slowgrowth.sh

1
test/units/testsuite-55-testchill.service
View File

@ -3,5 +3,6 @@
Description=No memory pressure
[Service]
MemoryHigh=3M
Slice=testsuite-55-workload.slice
ExecStart=sleep infinity

2
test/units/testsuite-55-testmunch.service
View File

@ -3,6 +3,6 @@
Description=Create some memory pressure
[Service]
MemoryHigh=2M
MemoryHigh=6M
Slice=testsuite-55-workload.slice
ExecStart=/usr/lib/systemd/tests/testdata/units/testsuite-55-slowgrowth.sh