systemd/test/units/testsuite-55-testbloat.service

# SPDX-License-Identifier: LGPL-2.1-or-later
[Unit]
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=5M
Slice=testsuite-55-workload.slice
ExecStart=/usr/lib/systemd/tests/testdata/units/testsuite-55-slowgrowth.sh
tests: add spdx license header to test unit/link/network/conf files Those are all consumed by our parser, so they all support comments. I was considering whether they should have a license header at all, but in the end I decided to add it because those files are often created by copying parts of real unit files. And if the real ones have a license, then those might as well. It's easier to add it than to make an exception. 2021-10-17 19:07:22 +03:00			`# SPDX-License-Identifier: LGPL-2.1-or-later`
test: make TEST-56-OOMD service unit files static 2020-10-24 01:47:07 +03:00			`[Unit]`
			`Description=Create a lot of memory pressure`

			`[Service]`
test: fix TEST-56-OOMD thresholds for linux 5.9 changes Fixes #17533 The memory pressure values of the units in TEST-56-OOMD seemed to be a lot lower after updating to linux 5.9. This is likely due to a fix from https://github.com/torvalds/linux/commit/e22c6ed90aa91abc08f107344428ebb8c2629e98. To account for this, I lowered memory.high on testbloat.service to throttle it even more. This was enough to generate the 50%+ value to trigger oomd for the test, but as an extra precaution I also lowered the oomd threshold to 1% so it's certain to try and kill testbloat.service. 2020-12-03 01:41:38 +03:00			`# A VERY small memory.high will cause the script (trying to use a lot of memory)`
			`# to throttle and be put under heavy pressure.`
test: adjust MemoryHigh= on oomd extended test units 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 2021-12-17 15:19:53 +03:00			`MemoryHigh=5M`
test: merge udev tests 2021-03-05 12:36:04 +03:00			`Slice=testsuite-55-workload.slice`
			`ExecStart=/usr/lib/systemd/tests/testdata/units/testsuite-55-slowgrowth.sh`