[infra-tests] [check stability] Apply DBUS configuration in C.I. (#5709)

Although `dbus-launch` will start a new DBUS daemon process, making use
of this process requires variable runtime information such as the bus
address. By default, this is provided via the process's standard output
stream.

Explicitly parse and apply the output configuration so that it may be
inherited by the Chrome and ChromeDriver processes that are subsequently
created.

@jgraham I have not been able to verify this fix locally. In fact, running it
on my desktop environment causes a different kind of failure altogether. I
suspect this may be due to the fact that my environment already has a running
DBUS daemon, and the superfluousness of the one created here causes problems.
I've spent some time trying to reproduce the problem (and prove out this fix) in
an Ubuntu virtual machine (as provided by VirtualBox), but I haven't had any
luck there. There are many subtle differences between an authentic desktop
environment and a virtualized server environment, and I don't know the
difference well enough to trigger the bug.

So this patch is really more theoretical than anything. I'm planning on
continuing investigation tomorrow, but I wanted to share my latest thinking in
case you have ideas on how we could validate it.

View on GitHub: https://github.com/w3c/web-platform-tests/pull/5709

Received on Wednesday, 26 April 2017 22:45:07 UTC