[Bug 29334] >=telepathy-mission-control-5.2.5: test fail

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=29334

--- Comment #6 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-08-02 07:44:50 PDT ---
(In reply to comment #0)
> Temporary bus daemon is
> unix:abstract=/tmp/dbus-yaXuS4ECiH,guid=a53636006cb5fcde686f33ed000031fa
> Temporary bus daemon PID is 14843
[...]
> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoServer: Failed to
> connect to socket /tmp/dbus-yaXuS4ECiH: Connection refused
[...]
> Killing temporary bus daemon: 14843
> ./tools/with-session-bus.sh: line 57: kill: (14843) - No existe el proceso

I think the problem is with your dbus-daemon or its configuration. If you run:

    sh test/twisted/tools/with-session-bus.sh --session -- /bin/sh

you should enter a shell that's in a new D-Bus session; the temporary
dbus-daemon (process 14843 in the above quoted text) shouldn't exit until you
exit from the shell, at which point with-session-bus.sh will kill it. It looks
as though dbus-daemon opens its socket, forks, writes its address and pid
through file descriptors 5 and 6 as intended, and then dies.

If that invocation succeeds, try this one, which is closer to what we actually
use for the tests:

    sh test/twisted/tools/with-session-bus.sh --config-file
test/twisted/tools/tmp-session-bus.conf -- /bin/sh

(for that one, you need to be in a telepathy-mission-control tree in which you
have run ./configure).

I wouldn't recommend running the Mission Control regression tests as part of a
BSD-ports-style build system: they're a bit twitchy and prone to race
conditions.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.