mirror of
https://github.com/morgan9e/systemd
synced 2026-04-14 08:25:20 +09:00
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: https://github.com/systemd/systemd/pull/21808#issuecomment-998927401
This commit is contained in:
committed by
Yu Watanabe
parent
e67e6691e5
commit
8470a16d6f
@@ -9,12 +9,13 @@ TEST_DESCRIPTION="https://github.com/systemd/systemd/issues/17433"
|
||||
|
||||
test_append_files() {
|
||||
(
|
||||
# Collecting coverage slows this particular test quite a bit, causing
|
||||
# it to fail with the default settings (20 triggers per 2 secs)
|
||||
# to trip over the default limit. Let's help it a bit in such case.
|
||||
if get_bool "$IS_BUILT_WITH_COVERAGE"; then
|
||||
# Tweak the trigger limit interval in case we are collecting coverage
|
||||
# or running without KVM - in both cases we might be slow enough that
|
||||
# we could miss the default rate-limit window and cause the test to fail
|
||||
# unexpectedly.
|
||||
if get_bool "$IS_BUILT_WITH_COVERAGE" || ! get_bool "$QEMU_KVM"; then
|
||||
mkdir -p "${initdir:?}/etc/systemd/system/test63.path.d"
|
||||
printf "[Path]\nTriggerLimitIntervalSec=10\n" >"${initdir:?}/etc/systemd/system/test63.path.d/coverage-override.conf"
|
||||
printf "[Path]\nTriggerLimitIntervalSec=10\n" >"${initdir:?}/etc/systemd/system/test63.path.d/triggerlimitinterval-override.conf"
|
||||
fi
|
||||
)
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user