[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 #11 from Pacho Ramos <pacho at condmat1.ciencias.uniovi.es> 2010-09-29 11:19:38 PDT ---
(In reply to comment #6)
> 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,

It looks to work ok:
# sh test/twisted/tools/with-session-bus.sh --session -- /bin/sh
Temporary bus daemon is
unix:abstract=/tmp/dbus-GCr2QAX5R4,guid=402554d18f3f9d4ba0fc27ef00009360
Temporary bus daemon PID is 16454
sh-4.0# exit
exit
Killing temporary bus daemon: 16454
# echo $?
0

> 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).
> 

In that case it looks to fail (but I am running it on sources after tests fail
to run when portage tries to run them under its building dir):
# sh test/twisted/tools/with-session-bus.sh --config-file
test/twisted/tools/tmp-session-bus.conf -- /bin/sh
usage: with-session-bus [options] -- program [program_options]
Requires write access to the current directory.

If $WITH_SESSION_BUS_FORK_DBUS_MONITOR is set, fork dbus-monitor
with the arguments in $WITH_SESSION_BUS_FORK_DBUS_MONITOR_OPT.
The output of dbus-monitor is saved in with-session-bus-<pid>.dbus-monitor-logs
# echo $?
2

> 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.

Are you referring to all tests or only part of them? In this last case, is
there any "easy" way to skip that regression tests and not the rest?

Thanks

-- 
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.