Hi
I traced myself through this mess and found the following:
tap-driver
- calls tap-gtester with stdout/stderr as pipes
- calls test-startup with stdout as new pipe and stderr inherited
- for each test
- starts dbus-daemon
- does test
- kills dbus-daemon _if test was sucessful_
in case of a failed test the dbus-daemon remains running and
keeps stderr open
- waits for EOF on stdout/stderr
as stderr is still open by the running dbus-daemons, this blocks
Bastian
--
It is a human characteristic to love little animals, especially if
they're attractive in some way.
-- McCoy, "The Trouble with Tribbles", stardate 4525.6
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
