[tracker/sam/functional-tests-quiet: 5/15] Disable D-Bus service startup timeout
- From: Sam Thursfield <sthursfield src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [tracker/sam/functional-tests-quiet: 5/15] Disable D-Bus service startup timeout
- Date: Thu, 29 Aug 2019 17:18:08 +0000 (UTC)
commit 13533ac2793d559a4507f30d91323ba9d8ca83e9
Author: Sam Thursfield <sam afuera me uk>
Date: Thu Aug 29 17:32:35 2019 +0300
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.
tests/test-bus.conf.in | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
---
diff --git a/tests/test-bus.conf.in b/tests/test-bus.conf.in
index 5b4f51ff9..3d86f6908 100644
--- a/tests/test-bus.conf.in
+++ b/tests/test-bus.conf.in
@@ -8,6 +8,12 @@
<servicedir>@abs_top_builddir@/tests/services/</servicedir>
+ <!-- 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="*"/>
@@ -16,5 +22,4 @@
<!-- Allow anyone to own anything -->
<allow own="*"/>
</policy>
-
</busconfig>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]