=== chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [06:44] Good morning === _salem is now known as salem_ [13:45] hello world [13:45] hello balloons [13:46] happy monday to you knome [13:46] heh, happy monday to you too ;) [13:50] balloons: Hey dude === salem_ is now known as _salem === _salem is now known as salem_ [15:03] hi balloons [15:05] pitti: ping [15:07] pitti: http://pastebin.ubuntu.com/9385488/ <- any idea what would cause the insserv problem when installing packages in the qemu image? === salem_ is now known as _salem [15:25] dobey: old autopkgtest, it's fixed in newer releases [15:30] pitti: i still have the same problem with autopkgtest 3.8.1 though [15:32] dobey: but I strongly suppose your image was built with an older version of adt-buildvm-ubuntu-cloud [15:32] it happens at that stage, not adt-run [15:32] oh === roadmr is now known as roadmr_afk [15:51] could not import package unityclickscope: cannot import name Notify, introspection typelib not found [15:51] hmm [15:55] pitti, ohh, the image has the old version, so it matters not that dobey updated his local install? [15:55] balloons: correct [15:55] good to know. This would be the case for containers or vm's yes? === _salem is now known as salem_ === salem_ is now known as _salem === roadmr_afk is now known as roadmr === _salem is now known as salem_ === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === toddyhb is now known as toddy === roadmr is now known as roadmr_afk === salem_ is now known as _salem === roadmr_afk is now known as roadmr === txspud|afk is now known as txspud [22:49] File "/usr/lib/python3/dist-packages/autopilot/utilities.py", line 62, in _pick_backend [22:49] "Unable to instantiate any backends\n%s" % '\n'.join(failure_reasons)) [22:49] RuntimeError: Unable to instantiate any backends [22:50] X11: ImportError("No module named 'Xlib'",) [22:50] elopio, thomi: any ideas why that would happen, how to fix it? [22:50] dobey: I probably need the whole stack trace to tell you [22:51] thomi: http://pastebin.ubuntu.com/9433150/ [22:52] dobey: do you have python3-xlib installed? [22:53] elopio: not sure. it seems to have been installed on my trusty host when i did "apt-get install python3-autopilot" but i'm not sure if it got installed in the vivid qemu image [22:53] or why it wouldn't have been installed [22:54] dobey: it comes from recommends [22:55] i guess autopkgtest isn't installing the recommends inside the qemu? :( [22:56] runtime options are so annoying [22:56] anyway, i seem to have an x/upstart/dbus session running for the tests now [22:57] dobey: you would have to add: Restrictions: needs-recommends [22:57] but you shouldn't need that [22:57] I think? [22:57] so hopefully it'll work this time around after adding a dep to debian/control [22:58] dobey: I would add python3-xlib to debian/test/control [22:58] ideally, yeah, i wouldn't need to add extra deps [22:58] elopio, need some style guidance from you, find myself wanting to remove some of the assertions here, e.g. testing the title of the page, etc., for our sanity test--should I, or should I start a new test in our own repo which is less verbose? http://bazaar.launchpad.net/~system-settings-touch/ubuntu-system-settings/trunk/view/head:/tests/autopilot/ubuntu_system_settings/tests/test_security.py#L204 [23:00] alesage, if you have time, it sounds better to clean up the uss test. But that could mean splitting the test, moving helpers around and maybe even adding QML test. [23:01] elopio, ok I'll start a separate test :) ("adding a QML test" is what convinced me) [23:01] If you won't have time to get all that by Thursday, then use our branch and file bugs. [23:01] elopio, ack [23:01] veebers: the merge should be alright now [23:02] For some reason, the first run takes forever. We need a verbose option to see what's going on. [23:02] Second time it's faster. [23:06] elopio: sweet cheers, perhaps it's the packages being installed and the system getting setup which takes a while [23:06] veebers, maybe. Take a look at the two // I had to add. [23:07] That's because ubuntu-sanity-tests is not on the archive [23:07] elopio: ah, does that mean that the command will work from wherever you run it? [23:07] right [23:07] http://pastebin.ubuntu.com/9433286/ [23:07] well, that's progress i guess [23:07] so now what is the problem [23:08] veeber: I don't think so [23:09] dobey: indeed. [23:10] dobey: I've just found /use/share/autopkgtest/setup-commands/ubuntu-touch-session [23:10] *usr [23:11] You might find useful tricks there. [23:11] elopio: what is that provided by? [23:11] err [23:12] it helps to not have typos :) [23:17] :) [23:33] bah, now it's apparently not wanting to actually run the tests at all [23:33] oh there it goes [23:57] ok, still failing for now. and need to go. i guess we'll have to run Xvfb manually rather than using xvfb-run, here [23:58] will try i in the morning [23:58] later :)