So, this is STILL an issue even with a 15 second timeout:
https://jenkins.qa.ubuntu.com/job/unity-
saucy-i386-autolanding/249/consoleFull
I think something else is going on.
Maybe this in the console log is clue??????
ERROR 2013-09-18 19:29:43 unity.glib.dbus.proxy GLibDBusProxy.cpp:194 Unable to
connect to proxy: Could not connect: No such file or directory
ERROR 2013-09-18 19:29:44 unity.glib.dbus.proxy GLibDBusProxy.cpp:194 Unable to
connect to proxy: Could not connect: No such file or directory
Is this because of DBus acting up or Jenkins acting up?
** Changed in: unity
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1224643
Title:
Some TestIconLoader unit tests intermittently fail during Jenkins CI
Status in Unity:
Confirmed
Status in “unity” package in Ubuntu:
New
Bug description:
During Jenkins Continuous Integration, we get intermittent
TestIconLoader unit test failures. It's usually one or more of the
following tests:
TestIconLoader.TestGetOneIcon
TestIconLoader.TestGetAnnotatedIcon
TestIconLoader.TestGetColorizedIcon
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1224643/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
