[08:25] DanChapman: if you get chance today, can you look at https://code.launchpad.net/~elfy/ubuntu-manual-tests/1282154 for me [08:25] just off to work now though [08:25] elfy certainly :-) i'll get it done this morning [08:26] thanks DanChapman :) [08:26] it's an easy one :) === vrruiz_ is now known as rvr [13:39] DanChapman: Thanks :) all synced now [13:43] elfy, your welcome :-) [15:52] DanChapman: howdy [15:52] balloons, hey there how's your week going? [15:54] DanChapman: good. Chatted a bit about the ubiquity failures. jibel mentioned that we probably should add a workaround to the job while the bug is there. do you think we could go back to not tracking the job (and avoiding the bug) and instead check for the popup at the end? [16:00] balloons, that's what we tried last week, i completely skipped the progress page and just waited for the finished dialog. It caused havoc :-S One thing we could try is when the crash occurs the test continues to execute so maybe try catching the exception and handle it gracefully that way [16:01] i'm seeing alot of compiz errors [16:02] in the logs aswell atm [16:04] DanChapman: yes thomi land that support; I sent you the link last week I think? [16:05] * balloons stops talking poorly of jibel :-) [16:06] I was thinking we had increased the timeout, not skipped the progress page :-) [16:06] me and my memory [16:07] balloons, yes it always occurs on the switch to the progress page or very soon after the switch. So i stopped the tests just before and waited with the timout for the popup [16:09] so jibel ^^ thoughts? [16:10] jibel, hey [16:13] balloons, jibel when i did the change last week and it made it worse it seems that it's occurring when repetitively polling on the same object. pitti did a fix for that a while back where looping on an object caused an app/test to hang. But that didn't resolve our issue. I will have a look and see what the best way of handling it is [16:23] DanChapman: I guess yea if possible to workaround let's do it. Sadly we don't know what's really wrong. I suppose it's hard to ask for a fix for something we can't produce === pitti_ is now known as pitti [16:31] hmmmmm i wonder if it's the U1 page causing the problems balloons see http://goo.gl/MXT2AV the segfault occurs before reaching the progress page although the Traceback says it happens during the progress page. [16:31] DanChapman, hey [16:31] DanChapman: oO that's a solid thought actually.. Any install paths that cause u1 to not appear? [16:32] I seem to remember it wouldn't appear if ... it's too early here still :-) [16:33] balloons, it's there by default for Ubuntu i believe except oem if i recall. ANd it might explain why i don't think i've ever seen this particular issue on the other flavors [16:34] DanChapman, did you get time to check the issue ? [16:34] they have more niggly issues like not finding labels due to slow ui updates [16:35] balloons, i've just got to pop to the shop will investigate further when i get back === yofel_ is now known as yofel [18:16] jibel, does the testrunner use a config file on jenkins or does it use the default values? [18:37] DanChapman, sorry, which config file? [18:37] there is nothing specific to jenkins IIRC [18:52] jibel, I was wondering if I could quickly set verbose ap_opts in the runner or whether I had to bother you to do it. On a different note I've just reproduced the segfault (at last!) with the runner locally. It happens as soon as 'skip' is clicked on the U1 page [19:02] DanChapman, I cannot connect to these machines this morning :/ [19:25] om26er: https://git.gnome.org/browse/pygobject/tree/tests/test_gio.py#n41 [19:26] om26er: oh, and you need from gi.repository import GLib, Gio [19:26] om26er: and depend on python3-gi and gir1.2-glib-2.0 [19:26] pitti, thanks === fginther` is now known as fginther === knome_ is now known as knome === stgraber_ is now known as stgraber === yofel_ is now known as yofel === salem_` is now known as _salem