summaryrefslogtreecommitdiff
path: root/tests/test-bus.conf.in
diff options
context:
space:
mode:
authorSam Thursfield <sam@afuera.me.uk>2019-08-29 17:32:35 +0300
committerSam Thursfield <sam@afuera.me.uk>2019-09-14 12:09:19 +0200
commitd5c4f7200f7f1b772163694731e1c2d0468e9df5 (patch)
tree442b74ff16d93ceacdb0114a133d56e7b141423d /tests/test-bus.conf.in
parentb1b130ac93ad6b6875a7e5a264388d76c5c39b53 (diff)
downloadtracker-d5c4f7200f7f1b772163694731e1c2d0468e9df5.tar.gz
Disable D-Bus service startup timeout
This timeout interferes with debugging. If you attach GDB to a daemon as it starts up and step through the code, the timeout can cause dbus-daemon to kill the process that you're debugging. We can rely on `meson test` to kill tests that actually don't finish, and the `meson test` timeout can be conveniently increased with the `--timeout-multiplier` commandline option.
Diffstat (limited to 'tests/test-bus.conf.in')
-rw-r--r--tests/test-bus.conf.in7
1 files changed, 6 insertions, 1 deletions
diff --git a/tests/test-bus.conf.in b/tests/test-bus.conf.in
index 2f4b2ef1b..f2df619e3 100644
--- a/tests/test-bus.conf.in
+++ b/tests/test-bus.conf.in
@@ -9,6 +9,12 @@
<servicedir>@abs_top_builddir@/tests/services/</servicedir>
<standard_session_servicedirs/>
+ <!-- This timeout is annoying when the service is being debugged. We rely on
+ the test harness to stop the test and kill the daemon if it does
+ get stuck.
+ -->
+ <limit name="service_start_timeout">1000000</limit>
+
<policy context="default">
<!-- Allow everything to be sent -->
<allow send_destination="*"/>
@@ -17,5 +23,4 @@
<!-- Allow anyone to own anything -->
<allow own="*"/>
</policy>
-
</busconfig>