[06:03] Good morning [07:22] good morning [07:22] morning DanChapman [07:23] hey elfy how are you? [07:24] good thanks - you? [07:33] elfy, a bit tired today but good apart from that :-) [07:36] DanChapman: such is life with young ones ;) [07:38] jibel: : you got any idea what time the images for b2 will be there? I want the url so I can start whining at my lot to test test test :p === zequence_ is now known as zequence [07:59] Good morning [08:00] hi jibel :) [08:00] elfy, I am not sure. cron builds are produced around 0800UTC, then cron will be disabled. That should be the 1rst candidates of beta2, but #ubuntu-release would know better [08:01] ok - only reason I asked you was you are on https://wiki.ubuntu.com/TrustyTahr/ReleaseTaskSignup :) [08:04] elfy, Yes, but last time I did this was for Quantal, so I need some time to get up to speed again :) [08:04] I can understand that :) [08:05] I'd need a week ... [09:02] pitti, P->T upgrades are broken due to checkbox. I'm looking into it. [10:37] jibel: how easy/intrusive is it to reduce the number of adt runners on alderamin & friends? [10:37] jibel: we keep getting failures when they get so loaded (eglibc triggered $WORLD) [10:38] pitti, it should be transparent, just change the number of executors in the configuration of the nodes. But until recently it made jenkins crash with an error 500, not sure retoaded fixed it [10:38] jibel: ah, mind if I try that? [10:39] pitti, apparently it works now, I tried on wazn [10:39] jibel: I changed alderamin from 5 to 4 [10:39] (-adt) [10:39] jibel: aldebaran-adt, too [11:00] Morning all === _salem is now known as salem_ [13:15] balloons: an idea - not sure if it is at all feasible - but you know what I'm like ... [13:15] so you go to the trackers and it gives you a list of bugs - what about if it didn't suggest bugs that were fixed 'now' [13:16] or invalid - or whatever [13:17] packages.u.c is updated [13:18] I beg to differ ... [13:18] http://packages.qa.ubuntu.com/qatracker/milestones/306/builds [13:18] oh hang on - just double check that :p [13:18] ok - I do beg to differ [13:18] http://packages.qa.ubuntu.com/qatracker/milestones/306/builds/55995/testcases [13:19] http://packages.qa.ubuntu.com/qatracker/milestones/306/builds/55995/testcases/1557/result [13:19] shows bug 1264525 which is fix released [13:19] bug 1264525 in Ubuntu Manual Tests "Mousepad testcases probably need refactoring" [High,Fix released] https://launchpad.net/bugs/1264525 [13:26] elfy, you don't get the header on that subpage [13:26] ohh, lol you are talking about bugs [13:26] haha [13:26] balloons, what is the image 'Ubuntu Touch' on the iso tracker? [13:27] jibel, pre-saucy release testing [13:27] balloons, can it be removed for T then? [13:28] it's been static since then, but I'm not sure if the intent is to resurrect it or not [13:28] I believe the recommendation your team is going to make is to use the tracker [13:28] it certainly isn't going to stay as it is now [13:46] balloons: thanks for doing the packages page header :D - and yes this is a new brainstorm courtesy of piskie ... [13:48] elfy, I would file a bug against the website, and it can be triaged / etc. It's probably a small enough change stgraber could squeeze it in assuming we wanted to make the change [13:49] ok [13:52] bug 1296735 [13:52] bug 1296735 in Ubuntu QA Website "Fixed bugs show in tracker" [Undecided,New] https://launchpad.net/bugs/1296735 [13:53] * elfy wanders off to find something else to nitpick ... [13:53] so short answer, yes it'd be great but it's not possible [13:53] bah [13:53] I wish I'd waited now lol [13:53] that's because a bug number may have any number of tasks, some of these may be marked as fixed some may not [13:54] as you only provide a bug number, the tracker will always pick the first one [13:54] ok - I can see that reasoning :) [13:54] but that one may be fixed (say, upstream) and not in Ubuntu, so the bug should still be listed... [13:54] yep [13:54] (and same goes with Ubuntu series, so just filtering for Ubuntu unfortunately doesn't quite work either) [13:56] thanks stgraber [14:07] elfy, for our sanity though, you can mark the bug as such, with the explanation by stephane [14:09] balloons: stgraber did all that :) [14:09] :-) awesome [14:10] balloons: you have mail - that's not urgent :D [15:00] good morning everybody [15:00] morning elopio [15:01] hey cgoldberg. [15:02] hi elopio === vrruiz_ is now known as rvr [15:02] morning cgoldberg and elopio [15:03] hey balloons [15:22] DanChapman, :-) http://quickgit.kde.org/?p=trojita.git&a=commit&h=4c4cc5ab2b8bb284aa031333a05c8d9833e04930 [15:22] balloons: well i couldnt resist :-) [15:33] rhuddie, rvr, alesage: joining the hangout. [15:34] I'm fighting with the headset, I'll be there in a bit [15:34] elopio, ok we're here [15:39] balloons jibel has any progress been made with the CI team taking over the current ubiquity tests? [15:51] DanChapman, no progress [15:52] jibel: ok thanks :-) === maclin__ is now known as maclin === bfiller is now known as bfiller_afk [18:21] robotfuel: I'm looking at your https://code.launchpad.net/~chris.gagnon/messaging-app/autopilot-tests-with-contacts/+merge/206554 [18:21] would it be too hard to split it in smaller branches? [18:21] elopio: most of that is the test [18:22] elopio: oops I was thinking of another mp [18:22] robotfuel: in here you are adding 7 tests. [18:22] elopio: yes, I was thinking of another mp sorry. [18:22] I would love 1 test per branch, but I'm not sure if that would be PITA because of the changes you are making there. [18:23] I want to review it, but it's scary with 1000 lines :) [18:24] elopio: I need to redo the contacts portion anyway. it depends on a branch that om26er is working on. [18:25] robotfuel: ok. I was about to touch some delete messages tests. As you are working with contacts, maybe we won't get a big merge conflict. [18:39] robotfuel, hey so it seems dialer-app does not (yet) work with the new backend, I just had a chat with boiko and he will be looking at that. [18:39] though I am working on pulling that logic into a reusable helper [18:40] om26er: the memory backend? [18:40] om26er: how about the messaging app? [18:42] om26er: there was a helper that used syncevolution in the address-book favorites mp, but they wanted the address-book to use the memory backend instead of us having a working helper :( [18:43] robotfuel, there is a point in not using the backend, that is it can lead to more failing points [18:55] om26er: make sure the backend issues get put in to the QA summary :D [18:57] robotfuel, will do, right now trying to get that resolved :) [19:09] robotfuel, need not to worry, its working now :) [19:10] om26er: do you have a branch you can share? [19:11] robotfuel, no, not yet. [19:12] robotfuel, btw do you know how can I get the exact library directory like /usr/lib/i386-linux-gnu/ etc and making it architect independent ? [19:18] om26er: it depends, ls /usr/lib/*-linux-gnu/some/thing/here will list all the i386-linux-gnu and x86_64-linux-gnu stuffs with some/thing/here [19:20] robotfuel, right, but that does not work for arm [19:25] om26er: you could also use /usr/lib/*/some/thing/here === roadmr_nothere_f is now known as roadmr === roadmr is now known as roadmr_afk === roadmr_afk is now known as roadmr === Ursinha is now known as Ursinha-afk === bfiller_afk is now known as bfiller === Ursinha-afk is now known as Ursinha [20:05] elopio I get this failure while running dash emulator test, possibly because I have some history: http://pastebin.ubuntu.com/7147981/ [20:05] elopio do you know if there's a way to clear the history, etc.? This is on my laptop btw [20:33] alesage: the history shouldn't affect that [20:33] it's failing opening the scope [20:33] alesage: did you follow the instructions from the CODING file? [20:33] if you don't compile it, you won't find the fakes, that might be the problem. [20:34] elopio, ok I'll look into, have just been using the device instead for the moment === roadmr is now known as roadmr_afk === ajmitch_ is now known as ajmitch === salem_ is now known as _salem