Skip to content

Commit 8470a16

Browse files
mrc0mmandyuwata
authored andcommitted
test: tweak TriggerLimitIntervalSec= if we're running w/o KVM as well
since in that case we might be also slow enough to miss the rate-limit window. However, let's not set the trigger limit unconditionally to still have coverage for the unaltered path unit (but without sacrificing CI stability). See: systemd#21808 (comment)
1 parent e67e669 commit 8470a16

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

test/TEST-63-ISSUE-17433/test.sh

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,12 +9,13 @@ TEST_DESCRIPTION="https://github.com/systemd/systemd/issues/17433"
99

1010
test_append_files() {
1111
(
12-
# Collecting coverage slows this particular test quite a bit, causing
13-
# it to fail with the default settings (20 triggers per 2 secs)
14-
# to trip over the default limit. Let's help it a bit in such case.
15-
if get_bool "$IS_BUILT_WITH_COVERAGE"; then
12+
# Tweak the trigger limit interval in case we are collecting coverage
13+
# or running without KVM - in both cases we might be slow enough that
14+
# we could miss the default rate-limit window and cause the test to fail
15+
# unexpectedly.
16+
if get_bool "$IS_BUILT_WITH_COVERAGE" || ! get_bool "$QEMU_KVM"; then
1617
mkdir -p "${initdir:?}/etc/systemd/system/test63.path.d"
17-
printf "[Path]\nTriggerLimitIntervalSec=10\n" >"${initdir:?}/etc/systemd/system/test63.path.d/coverage-override.conf"
18+
printf "[Path]\nTriggerLimitIntervalSec=10\n" >"${initdir:?}/etc/systemd/system/test63.path.d/triggerlimitinterval-override.conf"
1819
fi
1920
)
2021
}

0 commit comments

Comments
 (0)