[00:03] elopio, I just redid it.. https://code.launchpad.net/~nskaggs/reminders-app/newHeader2/+merge/224229. Not sure what happened on the original [00:04] notice however, jenkins blew up just like the desktop: http://91.189.93.70:8080/job/generic-mediumtests-utopic/610/testReport/junit/reminders.tests.test_reminders/RemindersTestCaseWithAccount/test_add_notebook_must_append_it_to_list_with_mouse_/ [00:05] balloons: I've just seen this one! [00:05] reminders.credentials.CredentialsException: Store operation already in progress [00:05] is that what you are getting on desktop? [00:05] yep [00:05] yay, I'm with you at least now. [00:06] I'll get your branch [00:25] ok https://code.launchpad.net/~nskaggs/reminders-app/newHeader2/+merge/224229 landed at least.. I'm off for the evening [00:25] I'm tempted to merge my branch, but I'll play tomorrow [00:32] balloons: have a good evening. I'm investigating the problem, that seems to be on delete account. === chihchun_afk is now known as chihchun [03:36] Good morning === 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 === roadmr_afk is now known as roadmr [10:07] pitti, little translation issue in apport http://paste.ubuntu.com/7694365/ (E)nvoyer (E)xaminer :) [10:08] jibel: haha [10:08] could this be fixed to it takes the second letter if 1rst is already taken? [10:09] s/to/so [10:09] jibel: would E(x)amimer be better, or E(n)voyer, or something else? [10:10] jibel: yes, the hotkey is marked with a & (KDE syntax) or _ (gettext syntax) [10:10] -msgstr "&Examiner en local" [10:10] E(x)aminer would be fine and is very common [10:10] +msgstr "E&xaminer en local" [10:10] proposal [10:10] ack [10:11] jibel: committed, thanks for pointing out [10:11] pitti, thanks for the fix === roadmr is now known as roadmr_afk [10:41] balloons, I see you spent some time on reminders, thanks! There is something I can do to help you? === roadmr_afk is now known as roadmr === _salem is now known as salem_ === roadmr is now known as roadmr_afk === roadmr_afk is now known as roadmr === salem_ is now known as _salem === _salem is now known as salem_ [14:11] pitti, I think this change of autopkgtest "Default to C.UTF-8 locale instead of C" makes graphiz test fail because fontconfig generates a warning on stderr [14:12] "Fontconfig warning: ignoring C.UTF-8: not a valid language tag" [14:12] jibel: right, just saw that [14:12] jibel: I wonder why that is, C.UTF-8 is a valid locale since precise/wheezy [14:12] same for matplotlib but it diddn't make the test fail [14:13] jibel: I was concerned that fixing the bug of not actually setting the default locale for non-root tests would make too many tests explode as they expect an UTF-8 env [14:14] so we either need to revert that back to C, or use --leave-lang, or I need to add some code to try en_US.UTF-8 > C.UTF-8 > C [14:14] * pitti -> some errands, bbl [14:14] pitti, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721275 [14:14] Debian bug 721275 in libfontconfig1 ""Fontconfig warning: ignoring C.UTF-8: not a valid language tag" floods personal X logs" [Normal,Fixed] [14:14] balloons: any details about the interview in 45 mins? [14:14] jibel: oh, nice [14:15] I'll merge that then [14:16] hm, seems we have the same version in T and U [14:30] pitti, it's happening on ubuntu on air; http://ubuntuonair.com/ [14:31] hi balloons [14:32] hi elfy [14:35] balloons: I got test dep installation into temp dir working today in adt-run ☺ [14:35] balloons: I have tests for executables, libraries, Python modules, and GI typelibs, i. e. it can locally install autopilot and friends [14:38] jibel: fontconfig bug reproduced locally (env -u LANGUAGE LANG=C.UTF-8 gedit), and fix uploaded, thanks for finding [14:58] yw === chihchun is now known as chihchun_afk === roadmr is now known as roadmr_afk [16:26] balloons do you know why 'in progress' was removed from the iso tracking system? [16:32] phillw, it's still there? [16:33] balloons, against which project should I file bugs for ubuntuonair? I'd like to watch it on the phone but the format is not supported :) [16:33] balloons: http://iso.qa.ubuntu.com/qatracker/milestones/317/builds/70577/testcases [16:33] And, yes, I'm signed in :) [16:34] weird cuz i see it here, phillw [16:34] I'll go clear my cache :) [16:34] indeed, I see it [16:34] jibel, good question.. the project in lp isn't used [16:34] cache it is, then :D Thanks :) [16:35] in progress where - because I don't see it :p [16:36] jibel, I'll track it down [16:36] elfy: click on the testcase and look under "result" [16:36] opens are failed, passed, in progress [16:36] s/opens/options/ [16:38] oh that [16:39] wonder why it's Running on the front page and In Progress inside [16:40] synonymous? [16:41] more or less - if phillw had said why is Running missing from http://iso.qa.ubuntu.com/qatracker/milestones/317/builds/70577/testcases I'd have said it's not :p [16:41] hahahah [16:41] elfy: so, it is not there... [16:42] phillw: depending on how you look at it, either running or in progress is missing, but the other one is there XD [16:42] I've cleared cache on both Chromium and F/fox [16:42] in progress isn't - it's running on that link - it's in progress if you go into a specific test [16:43] elfy: got it :) [16:43] balloons: bug 1126449 - any chance of getting that looked at before we've got hundreds of history lines to look at [16:43] bug 1126449 in Ubuntu QA Website "Getting a historical results report for a product is difficult" [Undecided,New] https://launchpad.net/bugs/1126449 [17:14] elfy: I reported it a couple cycles back... [17:18] elfy, it would depend on what stgraber's schedule looks like this cycle. We can see if he might have a few spare moments to toss at some of these problems [17:56] balloons: would be really helpful :) [19:31] balloons: do you think that anything will ever get done with all the edubuntu manual testcase bugs ? [19:31] I still have hope for the studio ones [19:33] elfy, hmm.. Well I was actually thinking about scheduling an event, but since you mentioned this, we could also schedule a hackday to work on the testcases [19:33] I was going to look at having some test and triage days.. sort of like a combined testing and bug hug day [19:34] but yea, that's the best way to close those bugs imho :-) [19:34] the studio stuff zequence and I are trying to get people involved with - if we can get people working on them it should be pretty painless [19:34] but they're all quite intensive apps === ara is now known as Guest22715 [19:35] I just look at the bug list a couple of times a week so I can let out a big sigh :p [19:35] I guess with edubuntu being lts only nothing much in the way of haste required there [19:36] great, a usb-creator issue right as the cycle starts http://launchpad.net/bugs/1325801 [19:36] Ubuntu bug 1325801 in Ubuntu Kylin "failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:" [Critical,Triaged] [19:37] balloons: on the other hand with edubuntu specifically - if no-one is ever actually going to manually test these things - is there a case for marking them invalid [19:37] wxl: cycle start? not sure where you've been but it's week 10 for me :D [19:38] elfy: well, let's say the official testing :) [19:38] O_O [19:38] elfy, edubuntu is a bit unique.. honestly, we should get stgraber's opinion [19:38] but you are right.. they won't be used for 2 years eh? [19:38] wxl: I've been working with xubuntu testers for weeks :p [19:38] balloons: yea, good to have the conversation with stgraber re them [19:39] elfy: fine, you win. [19:39] wxl: lol [19:39] wxl: that doesn't mean we've actually done much testing though - I've just been hassling them :) [19:40] elfy: i know the feeling :) [19:40] :) [19:40] wxl: you lubuntu - is that right? [19:41] elfy: yep. i'm the noob tester. [19:41] cool - good to have a name then [19:42] I found a nasty ibus bug in xubuntu last cycle - no idea what name to talk to at lubuntu then - so mailed your m/l which was pretty much a waste of my time [19:42] lubuntu-qa? [19:42] whatever mailing list I could find [19:42] might have been lubuntu-users which for such things may have been a waste of time [19:42] i'd recommend lubuntu-qa for quality issues [19:42] not sure what it was - don't think it was -qa one [19:43] well now you know for the future :) [19:43] is this bug still ongoing? [19:43] anyway - now you're idling in channel there's no need for mailing list at all :) [19:43] yeah and if for some reason i'm not here (this channel) i'm usually here (freenode) so feel free to msg [19:43] I'd guess so - but it doesn't affect us as we stopped seeding ibus for xubuntu [19:44] you wouldn't happen to know the bug number would you? [19:44] wxl: same - I'm generally online 0600UTC to ~21/2200UTC daily [19:45] bug 1284635 [19:45] bug 1284635 in ibus (Ubuntu Trusty) "IBus does not support certain keyboard layouts" [High,Triaged] https://launchpad.net/bugs/1284635 [19:45] we just gave up trying to get anywhere - no-one appeared to care *shrug* [19:49] i'll look into it thanks [19:51] I've not looked into it any further as it's not affecting us now [19:51] the problem is actually that those keyboard layouts shouldn't exist in a way [19:51] or, there is no special meaning for them in ibus [19:52] GNOME does something to turn off ibus when the layout is not found [19:52] afaik [19:52] xfce doesn't [19:52] and so ibus is still running [19:52] and manages layouts [19:52] but it doesn't know what the layout is, because it's not specified [19:52] even so - I've no real interest in it till we seed it again [19:52] the "easy" way would be to create all layouts you could ever have [19:52] so they wouldn't at least fail [19:53] but the "real" solution would be to fallback to non-ibus stuff when the layout isn't present [19:53] yep [19:53] yeah, just opening the bug for potentially interested parties [19:53] the ironic thing is that the bug doesn't really exist for people who actually *need* ibus [19:54] because their layouts *are* specified [19:54] yea [19:54] which is even more annoying [19:54] the bug only appears for people who don't need it, and the most straightforward solution for the regular user is to just uninstall ibus... === salem_ is now known as _salem