system/systemd
system/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd synced 2024-07-09 04:26:06 +00:00
Code Issues Projects Releases Wiki Activity

TEST-07-PID1: Lower TriggerLimitIntervalSec= unconditionally

Browse Source 
It shouldn't hurt to do this when KVM is enabled or we're not collecting
coverage so let's just always lower the trigger limit interval.
This commit is contained in:
Daan De Meyer 2024-05-04 13:22:53 +02:00
parent 7590e1d037
commit 733d0594f0
2 changed files with 4 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
test/TEST-07-PID1/test.sh
View File

@ -11,16 +11,6 @@ NSPAWN_ARGUMENTS="--capability=CAP_NET_ADMIN"
. "${TEST_BASE_DIR:?}/test-functions"
test_append_files() {
local workspace="${1:?}"
# We might not be fast enough to hit the limit (20 triggers per 2 secs)
# in certain environments, i.e. when running without KVM or when collecting
# coverage. Let's help it a bit in such case.
if ! get_bool "$QEMU_KVM" || get_bool "$IS_BUILT_WITH_COVERAGE"; then
mkdir -p "$workspace/etc/systemd/system/issue2467.socket.d"
printf "[Socket]\nTriggerLimitIntervalSec=10\n" >"$workspace/etc/systemd/system/issue2467.socket.d/TriggerLimitInterval.conf"
fi
image_install logger socat
}

4
test/testsuite-07.units/issue2467.socket
View File

@ -1,3 +1,7 @@
# SPDX-License-Identifier: LGPL-2.1-or-later
[Socket]
ListenStream=/run/test.ctl
# We might not be fast enough to hit the default limit (20 triggers per 2 secs)
# in certain environments, i.e. when running without KVM or when collecting
# coverage. Let's help it a bit in such cases by lowering the limit to 10 seconds.
TriggerLimitIntervalSec=10