summaryrefslogtreecommitdiff
path: root/test/TEST-63-PATH
diff options
context:
space:
mode:
authorFrantisek Sumsal <frantisek@sumsal.cz>2022-08-25 12:05:53 +0200
committerFrantisek Sumsal <frantisek@sumsal.cz>2022-08-25 16:21:39 +0000
commit0f1f5629747011d0401730ce81c955ec1d430e3d (patch)
tree7c1cbf8c79f86b860bc80b836a6721d9f5f58eba /test/TEST-63-PATH
parent80c2f3e4cfc2798fed11224df576139466ee467a (diff)
downloadsystemd-0f1f5629747011d0401730ce81c955ec1d430e3d.tar.gz
test: make TEST-63 more reliable on slower machines
Otherwise we might never hit the trigger limit and wait indefinitely. Found when trying to run the test on an EC2 xen machine without a nested virt in CentOS CI (in preparations for some ... unforseseen consequences).
Diffstat (limited to 'test/TEST-63-PATH')
-rwxr-xr-xtest/TEST-63-PATH/test.sh13
1 files changed, 0 insertions, 13 deletions
diff --git a/test/TEST-63-PATH/test.sh b/test/TEST-63-PATH/test.sh
index 65f41ed1de..4d132ba939 100755
--- a/test/TEST-63-PATH/test.sh
+++ b/test/TEST-63-PATH/test.sh
@@ -7,17 +7,4 @@ TEST_DESCRIPTION="https://github.com/systemd/systemd/issues/17433"
# shellcheck source=test/test-functions
. "${TEST_BASE_DIR:?}/test-functions"
-test_append_files() {
- (
- # 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/triggerlimitinterval-override.conf"
- fi
- )
-}
-
do_test "$@"