systemd/test/units/TEST-55-OOMD-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 'stress-ng' (trying to use a lot of memory)
# to throttle and be put under heavy pressure.
MemoryHigh=3M
Slice=TEST-55-OOMD-workload.slice
ExecStart=stress-ng --timeout 3m --vm 10 --vm-bytes 200M --vm-keep
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 18:07:22 +02:00			`# SPDX-License-Identifier: LGPL-2.1-or-later`
test: make TEST-56-OOMD service unit files static 2020-10-23 15:47:07 -07:00			`[Unit]`
			`Description=Create a lot of memory pressure`

			`[Service]`
TEST-55-OOMD: Switch to stress-ng stress-ng is available in OpenSUSE and in CentOS Stream without needing EPEL so let's switch to it instead of stress. 2024-07-05 09:58:17 +02:00			`# A VERY small memory.high will cause the 'stress-ng' (trying to use a lot of memory)`
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-02 14:41:38 -08:00			`# to throttle and be put under heavy pressure.`
TEST-55-OOMD: use 'stress' to create high pressure The test fails on my machine, running Debian stable, because testsuite-55-testbloat.service just swaps and never goes over the limit, so it's not killed. Use 'stress' instead which seems to be able to overwhelm the swap too. 2023-06-17 00:07:32 +01:00			`MemoryHigh=3M`
test: Rename testsuite-XX units to match test name Having these named differently than the test itself mostly creates unecessary confusion and makes writing logic against the tests harder so let's rename the testsuite-xx units and scripts to just use the test name itself. 2024-05-11 19:17:13 +02:00			`Slice=TEST-55-OOMD-workload.slice`
TEST-55-OOMD: Switch to stress-ng stress-ng is available in OpenSUSE and in CentOS Stream without needing EPEL so let's switch to it instead of stress. 2024-07-05 09:58:17 +02:00			`ExecStart=stress-ng --timeout 3m --vm 10 --vm-bytes 200M --vm-keep`