#ubuntu-quality 2013-11-01 <davmor2> Morning all <elfy> morning davmor2 <DanChapman> morning davmor2 and elfy <elfy> DanChapman: when you're about with a few minutes ... <elfy> aaah should learn to either touchtype or look up before entering lol <DanChapman> elfy, i've got some time now, so fire away :-) <elfy> ok - really is quite simple - autopilot and the tests we're hoping to be running by milestones <elfy> what 'exactly' will this be testing? <elfy> will it just test that the image is ok and runs? <elfy> will it test that an image will install properly? <elfy> what about things like resizing testing? <DanChapman> elfy it will test all of the above. Basically the tests cover multiple aspects of the install so pretty much follows the same processes as the current manual tests do. So checking each page has the correct entries,labels, images etc which varies depending on the install scenario i.e lvm, manual partition etc. The plan is to cover all possible scenarios so resize testing is the next on my list. <elfy> ok - thanks DanChapman - I'm planning trusty and just needed to know that <elfy> so - the test 'should' cover, at some point, all the current scenarios <DanChapman> now the tests atm only cover up till the installation is finished and the VM is then shutdown so there is no tests for testing the install after a reboot. But i think there is plans to do a reboot and say run the desktop autopilot tests or some other tests to check the installation was successful in that respect <elfy> DanChapman: ok <DanChapman> yes at 'some point' they should cover all feasible scenarios :-) <elfy> :) <elfy> we'll still want at least some eyes on it <elfy> but knowing that it has been at least tested will be a bit of a load off of shoulders <DanChapman> elfy indeed, manual testing will always be needed :-) <elfy> yep <elfy> DanChapman: seems that I've got some takers for app autopilots for us as well * elfy wants quietly brush that off his hands ... <DanChapman> elfy, nice! We need more folks writing tests for the desktop apps <elfy> yea indeed - and 'we' need them writing tests for things that aren't phone :) <elfy> just like the manual test situation I suspect we'll be up near the front again lol <elopio> hello. <samgabbay> Hello World Of Ubuntu! Hello Ubuntunians and Canocalians #ubuntu-quality 2013-11-02 <PhilDick> anyone available to help me understand testdrive-gtk? <Noskcaj> PhilDick, I'm the maintainer, so sure <Noskcaj> The two identical looking entries are probably i386 (32-bit) and amd64 (64-bit) <PhilDick> thanks Noskcaj... neither work <PhilDick> I have VirtualBox installed... it says cache empty. <Noskcaj> You have to download the iso first. tick the box then click "sync" <Noskcaj> And make sure that the VM is set to virtualbox, in the preference dialog <PhilDick> Gotcha, I was downloading iso now, saw where I could point it at an iso <PhilDick> thanks for the time/response, I wish I had time to track all the answers down myself, but am trying to get active ASAP. <Noskcaj> PhilDick, https://wiki.ubuntu.com/QATeam/Testdrive has most of the info. If you can add screenshots, please do <Noskcaj> Some videos guides: http://www.youtube.com/channel/UCMfoypEyUFq8TDjSwxswjGw <PhilDick> Thanks, I'll try to be active enough to share back to wikis, figure my learning curve could be shared... right now I'm dumping notes in an abiword file, on my testing partition (where I'm going to setup testdrive) while I wait for my dayjob workstation to reboot... <Noskcaj> And the classroom session logs: figure my learning curve could be shared... right now I'm dumping notes in an abiword file, on my testing partition (where I'm going to setup testdrive) while I wait for my dayjob workstation to reboot... <PhilDick> and catch.com seems to be down, which doesn't help <Noskcaj> crap, stupid xchat <Noskcaj> https://wiki.ubuntu.com/Testing/Activities/Classroom/Saucy <PhilDick> at least emailing myself is always an option... ;) <Noskcaj> PhilDick, When iso testing, don't expect much to work this month. All the funny bugs appear at the start of the cycle <PhilDick> I don't expect it to go smoothly, but I hope to learn how to do this stuff now so I can contribute when development gets more meaty. <PhilDick> afk, brb <Noskcaj> bye #ubuntu-quality 2013-11-03 <ztrainjetsfan> Hey I have a bug to report from the install of trusty. When trying to install trusty when you are given the chance to attach a ubuntu one account to the install it stalls after clicking continue <Noskcaj> ztrainjetsfan, Was your internet connected? <ztrainjetsfan> Yes <Noskcaj> Then i am out of ideas, thanks for the info though. Maybe try search for the error on launchpad? <ztrainjetsfan> Ok, thank you. Also, the install works when you just skip that step <Noskcaj> yeah, it's meant to be optional <elfy> /chanopt confmode off <alexbh> Hi, i just downloaded the daily of 20131103... I ran it as Live USB but there is an issue with the graphic interface <melodie> hi ubuntu-quality people <elfy> evening melodie <melodie> hi elfy, could someone help me decide if opening a new bug report for this reason is the right thing? I was first wondering if my question was relevant: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1247496 <ubot5> Ubuntu bug 1246664 in linux (Ubuntu) "duplicate for #1247496 "Buffer I/O error on device zram0, logical block 515067"" [Medium,Confirmed] <melodie> "While I am here, I do have a question: shouldn't an init config file have a "stop" line after the "start" line?" <melodie> because I am unsure about the possible consequences of that line missing, if it can have any consequence <melodie> I thought I would come ask here, perhaps some people with dev knowledge would be here and able to tell me? <melodie> dev knowledge and upstart insights <elfy> I'm neither of those :) <TheLordOfTime> lol elfy <elfy> thanks for the support :p <elfy> melodie: as far as the whether to start a new bug for a duplicate - I guess no unless it's different bug <melodie> elfy I am not talking about the duplicate <melodie> I was seeking for a duplicate, didn't find one, I posted, but there is a duplicate I had not seen, end of line, new question: <melodie> "While I am here, I do have a question: shouldn't an init config file have a "stop" line after the "start" line?" <melodie> and this man tells me to open a new bug report for the stop start lines <melodie> so my question to you is simple: is that lack of a stop line in the script possibly the cause of issues in the way zram behavior creates freezes and crashes in the X session? <elfy> I've no idea - I did say I've no knowledge of dev or upstart <melodie> if it can cause malfunctions in the session, then I think it would not be relevant to create a separate bug report for this <melodie> I might have to ask at #ubuntu-devel then? <elfy> nor do I have any knowledge of zram - we don't use it <elfy> melodie: that's probably where I'd start <melodie> elfy thanks! <elfy> welcome <melodie> bbl #ubuntu-quality 2013-11-04 <pitti> Good morning <jibel> Good morning <pitti> jibel: FYI, fixing the ubuntu-drivers-common autopkgtest now <jibel> pitti, I looked at python-csb, besides the test creates data in dist-package which is wrong, the main issue with the autopkgtest part is a python path order. But then the package requires scilab which is not installable. So I'll have a another look when this get fixed. <pitti> jibel: thanks <davmor2> Morning all <elfy> morning davmor2 <elopio> good morning everybody. <balloons> morning elopio <elfy> hi balloons <balloons> hello elfy <elfy> good weekend I trust <balloons> elfy, yes, it's nice to get outside :-) <elfy> it is - though it was windy and wet here - so it was nice to stay indoors :p <balloons> heh.. we had a couple really nice days. Yesterday was the first "cooler" day here of the season.. we're in fall now <davmor2> morning elopio <elfy> balloons: yep it's definitely autumnal <alesage> pitti hi, a question about dbusmock--when setting a property on a battery, e.g., wouldn't we expect to be able to see those properties in d-feet? <pitti> alesage: FYI, "properties set on mocked batteries don't show up in d-feet" <pitti> alesage: known, as dbusmock doesn't generate introspection for properties ATM <pitti> alesage: (it's not actually that easy to do so) <alesage> pitti ok interesting, this 'introspection' is new to me <pitti> alesage: as for replacing the actual upower instance: sudo killall upowerd; sudo PYTHONPATH=. python3 -m dbusmock -t upower <pitti> (from trunk checkout) <pitti> alesage: you can leave out the PYTHONPATH for running from the installed package, of course <alesage> pitti right, I'm able to show that I think by killing and running those tests <pitti> alesage: more detailled answer will have to wait for tomorrow, I'm afraid <pitti> (i. e. reviewing your branch, etc.) <alesage> pitti, ok thanks--that gives me an opportunity to add more to review :) <pitti> alesage: but it's a bit unfriendly, and needs root privs, so better run the tests on a private bus <alesage> pitti, my theory is that I need to run as authentic to trick unity, what do you think? <pitti> alesage: if you can (re)start unity for the tests, running a private system bus should be fine <pitti> alesage: if you need to deal with an existing running instance, then not, indeed <alesage> pitti ok interesting, will follow up tomorrow thx :) <samgabbay> Greetings and salutations to all canonicallians and ubuntunians <Letozaf_> balloons, Hello :D <Letozaf_> balloons, just wanted to let you know that my adventure with ubiquity ended here: bug number 1247359 take a look at the screenshot I attached to the bug report <Letozaf_> bug 1247359 <ubot5> bug 1247359 in autopilot (Ubuntu) "garbled screen when trying to install python-autopliot on Virtualbox VM" [Undecided,New] https://launchpad.net/bugs/1247359 <balloons> Letozaf_, hello <balloons> doug5, howdy howdy <balloons> Noskcaj, hello to you too :-) <Noskcaj> hey balloons <doug5> balloons, hello! <elopio> balloons: can you review here, please? https://code.launchpad.net/~elopio/ubuntu-clock-app/qmlscene_launch/+merge/193842 <balloons> elopio, oO.. is this the first? <elopio> balloons: first of what? <balloons> elopio, I thought you had some others as well <doug5> balloons, how is it going? <balloons> doug5, excellent, yourself? <doug5> balloons, not too bad :) <doug5> balloons, going to make a coffe and then check the mp <balloons> doug5, perfect. I'm trying to find it in the list, haha <balloons> did you make the tweaks? <balloons> nvm, found it <TheLordOfTime> balloons: ping. <balloons> TheLordOfTime, pong <TheLordOfTime> balloons: RE: QA/BugSquad merger blueprint, I added a section for "Other Concerns" based on the last message to the mailing lists by AG Restringere. <TheLordOfTime> can you comment on that? (RE: Bug Control and this merger, which was targeted for Bug Squad) <TheLordOfTime> because when you and I last spoke on it, the general idea I got was that Bug Control would be left alone in the merger, because of the separate application procedures and enhanced bug permission sets. <TheLordOfTime> also, forgive some... lagginess... in the messages I'm sending to IRC, my client's still sifting through its initial connection-sending buffer to the channels :/ <elfy> that's what I'd assumed - conversation certainly appeared to be of the 'not touching those perms with a barge pole' <elfy> TheLordOfTime: ^^ <TheLordOfTime> elfy: that was my assumption as well <TheLordOfTime> just want to confirm that. <elfy> yep <elopio> balloons: no, I haven't noticed that was a problem in the apps. Maybe I'll need more branches like this one. <TheLordOfTime> elfy: I did make a note of the distinction on the MLs to AG, so the only issue here is whether my assumptions were correct <TheLordOfTime> and I modified the blueprint for it adding an "Other Concerns" section where responses could be posted by the masters of the blueprint <elfy> I tend to glaze over with blueprints unless they are xubuntu ones :) <TheLordOfTime> heh <balloons> elfy, TheLordOfTime I saw the message today ,but have not digested it <Letozaf_> balloons, I ran ubuntu-rssreader-app autopilot tests on my PC and on the device, I have different failures in different parts of the tests <TheLordOfTime> balloons: hehe, no problem, I was just confirming the information I gathered from the discussion you and I had shortly after the first message in the lists was sent :) <TheLordOfTime> that bugcontrol wouldn't be touched during the merger <Letozaf_> balloons, I must admit I am a bit confused :P <balloons> TheLordOfTime, yes, that's my thoughts, but its open to discussion @ vUDS certainly <balloons> Letozaf_, :-( different failures? <Letozaf_> balloons, yes, on my PC sometimes the toolbar behaves in a strange way making the test fail <Letozaf_> balloons, instead on the device this does not happen <balloons> Letozaf_, well, we should fix things like that <Letozaf_> balloons, is it better for me to wait for you guys to migrate to 1.4 or what? <TheLordOfTime> balloons: indeed, I've added to the blueprint about "Concerns" (separate than thoughts) but based on the general discussion, I was pretty certain that we were identifying Bug Squad and Bug Control as separate distinct entities in this. <TheLordOfTime> I think hggdh has a similar observation, but I would highly contest merging bugcontrol with qa, if only because the QA team doesn't necessarily have elevated bug permissions similar to Bug Control has (this same distinction applies to Bug Control vs. Bug Squad) <TheLordOfTime> (so far that discussion hasn't happened, but it's also not my call :P) <balloons> TheLordOfTime, excellent. Thanks for putting all that into the blueprint <balloons> good stuff <balloons> Letozaf_, the best scenario is the tests work well before the migration <balloons> so after you migrate you have a baseline to ensure it still works :-) <hggdh> balloons: hi <balloons> hggdh, hello <Letozaf_> balloons, yes but the toolbar strange behavior, how do I cope with that ? <hggdh> balloons: I have been unable to answer your proposal due to the lack of a working system. I can only access IRC via a convoluted setup, while I wait for the replacement laptop to arrive <hggdh> (a System76! YEAH!) <balloons> hggdh, funzies! <hggdh> balloons: but so that at least I have something said: I all all for the merge of bugsquad (hell, *I* suggested it to you ;-) <hggdh> for bugcontrol, I am not sure -- I think it should be left aside, at least for the moment, since it affects many more people than bugsquad <TheLordOfTime> +1 for hggdh's opinions <hggdh> er. "many more people" should be understood as "many more people with higher access, not necessarily dealing with QA" <TheLordOfTime> exactly my concern too. <hggdh> yeah, just reading the backlog now <elfy> TheLordOfTime: so where is this blueprint? * elfy ought to look ... * hggdh goes AFK -- meeting <balloons> elfy, https://blueprints.launchpad.net/ubuntu/+spec/community-1311-quality-bugsquad <elfy> balloons: thanks <TheLordOfTime> sorry for not giving it to ya, elfy, I was distracted by other things <TheLordOfTime> namely responding to AG on the bugsquad list <TheLordOfTime> speaking of which, hggdh, when you get a chance, I'd like your input on his suggestions on the bugsquad ML. <TheLordOfTime> no rush though, I made my concerns noted. * Letozaf_ is rebooting PC <balloons> doug5, did you see victor's response? <doug5> balloons, yep, working on it <knome> balloons, allÃ¶ <balloons> knome, allo <knome> balloons, starting to have the plans for QA ready soon? <balloons> knome, what do you mean? <knome> objectives for 14.04 <knome> and how's the team merging goin on? <knome> *going too <balloons> knome, ohh.. indeed, there's a blueprint for vUDS <balloons> https://blueprints.launchpad.net/ubuntu/+spec/community-1311-quality-bugsquad <balloons> I sent back a mail reply.. perhaps I should make a thread just for this <balloons> elfy didn't see it either and he sees everything <balloons> i'll just add it to the general psa on blueprints <knome> mhm <knome> i'm not following -quality or -bugs or anything like that <knome> :P <doug5> balloons, ok, patch is done, I will finalize it tomorrow <balloons> doug5, sounds like working ? <doug5> balloons, yeah, a little bit tricky though. Actually, I can push it right now so you can have a look <balloons> ohh cool #ubuntu-quality 2013-11-05 <pitti> Good morning <jibel> Good morning <davmor2> Morning all <jibel> balloons, do you know anything about Dan's ubiquity tests. I fixed the runner to work with his latest branch and trusty, but default installation is in Finnish. Do you know if it is expected? <xnox> jibel: it picks a random language (from a few sane ones) and executes test in different language each time. <xnox> jibel: i think that's good =) it's a bit of fuzzy testing ;-) <xnox> (sane, meaning that the first char of the language name in in ASCII, so no weird languages) <jibel> xnox, okay I see, but perhaps we should have a default installation in English so we have a base of comparison when this 'fuzzy' testing fails? <xnox> jibel: why? =) are the logs all in Finish as well? as a developer the messages I care about are emitted in english I think. <xnox> jibel: it would be nice to override a language, and force tests in a particular language. E.g. this jenkins job always tests english, this one french, and this one does a random one. <jibel> xnox, some of them are in Finnish, but the main issue I see is that we have no reference and don't know if it fails because of the language or because the core is broken (i.e it takes more time to identify the cause of the problem) <xnox> jibel: ack. <pitti> jibel: thanks for doing the discard tests! I'm slightly confused about them, particularly why the "read compiled tree" test is so much slower <pitti> jibel: AFAICS, "discard" should mostly make a difference (much slower) on deletion; without discarding, writing gets slower over the weeks/months, but reading should always be equally fast no matter how much garbage there is on the disk or whether or not you use dicard <jibel> pitti, agreed. The test does an os.walk on the kernel tree and a sync() at the end. The sync might explain the bug difference between the default options and noatime but I don't see why it would make a difference when adding discard. <jibel> s/bug/big/ <elopio> good morning. <njin> ubuntukylin <jibel> balloons, I'm activating autopilot test of ubiquity for lubuntu, xubuntu and edubuntu. any other flavor you'd like to see? <balloons> oO :-) umm.. I believe you can do it for ubuntu gnome also <elfy> oooh - I like the sound of that :) <xnox> jibel: excellent. once they run green for a while, we'd want to start blocking proposed -> current migration, unless autopilot passes. <samgabbay> Hello Canonicallians And Ubuntunians <samgabbay> you have to be kidding me -_- <DanChapman> evening all :-) <elfy> hey DanChapman <DanChapman> heya elfy :-) hows things? <elfy> pretty good thanks <elfy> I am going to try and get to the membership meeting on the 7th to shout from the sidelines :) <elfy> DanChapman: word from the wise, or old, whichever you prefer - make sure your reference on https://wiki.ubuntu.com/Membership/Boards actually points to you :) <DanChapman> elfy thanks :-) Oh i'm sure i did it correctly I'll fix that now. What does a membership meeting entail anyway? <elfy> well from memory - I went - answered some questions and that was it <elfy> might want to try and scrounge some testimonials up - even if you have got 2 excellent people there already lol <DanChapman> elfy yes I was going to get on that. Ive just got back from a trip to birmingham so just getting my self back in order :-) <elfy> yep - r/l trumps everything else :) <elfy> you like working with OU? I did some of that before I managed to go to a uni fulltime <DanChapman> The OU is ok I suppose it seems a bit of a long winded load of heatherjohnson@example.com. I was up in birmingham at computeach training centre i'm doing some extra courses with them something a bit more practical than theoretical stuff :-) <elfy> DanChapman: yea - I found that - but it is supposedly part time - I was glad I was in a position to go fulltime <elfy> even if I was 38 <DanChapman> elfy I decided to study full-time doing the maximum amount of modules a year with them as I had funding for it and I could spend more time at home with the kids this way :-) <elfy> not too bad then - and time at home is great :) <balloons> DanChapman, howdy <balloons> did you see this? https://jenkins.qa.ubuntu.com/job/autopilot_ubiquity-devel/lastCompletedBuild/ARCH=i386,TESTNAME=test_custom_install,label=rabisu/testReport/ubiquity_autopilot_tests.tests.test_custom_install/CustomInstallTestCase/test_custom_install/ <DanChapman> balloons, howdy :-) There running again, YAY! <TheLordOfTime> balloons: remind me about these vUDS things, when are they and where are they held? <elfy> on the interwebs TheLordOfTime <elfy> just saying ... <balloons> TheLordOfTime, uds.ubuntu.com <TheLordOfTime> elfy: yes, i know that, but *where* on the interwebs :P <elfy> community track generally <balloons> yes, elfy is correct again <balloons> 2/2 <elfy> that's this week sorted then :p <TheLordOfTime> balloons: expect me to be in attendance, is this having a corresponding hangout? <balloons> TheLordOfTime, yes, irc and g hangout <TheLordOfTime> might i ask who all's in the hangout so far? (if you even know) <elfy> not me * elfy is unloved <TheLordOfTime> heh <balloons> haha, he could join if he wanted <elfy> :) <balloons> you can mute your video :-) <balloons> audio only is fine.. anyways, whoever wants to enter the hangout can do so <elfy> he turns up - he lurks on irc - he has no webcam :p <TheLordOfTime> hehe, well, i asked because i wouldn't mind being in attendance there, but of course, if there's people higher up the chain who need to be there then that's fine. <TheLordOfTime> now, if only i could tell the system that I was going to be in attendance >.> <balloons> DanChapman, yes they are running.. xnox and jibel had a bit of conversation this morning about them.. basically they want to start blocking migrations from proposed once they are fully vetted <balloons> so we've arrived.. I'm wondering why the non-fatal error occurs that we see <DanChapman> balloons, that non-fatal is the catching the known bug that for the 'Something else' page title switching back to the title of the page before :-) <balloons> Ohh.. :-) It wasn't obvious as the ref and actual are the "same" <DanChapman> balloons, yes ref and actual should not be the same on that one. I actually need to sort the error messages a bit to make them clearer :-) <elopio> can I get a review here, please? <elopio> https://code.launchpad.net/~elopio/ubuntu-weather-app/fix1248296-button_objectName/+merge/193997 <elopio> I don't know... maaaybeee, balloons? <balloons> o, o, pick me, pick me.. file manager hates me right now <elopio> :) <davmor2> elopio: don't pick balloons he seems to eager <balloons> davmor2, sadly it was a 2 line change.. i get no respite <davmor2> balloons: oh well that's okay then :D <davmor2> balloons: Filemanager hates me too so I don't think you are specifically singled out ;) <balloons> davmor2, :-) <balloons> buonasera Letozaf_ <Letozaf_> balloons, buonasera :-) <Letozaf_> balloons, yay!! <Letozaf_> balloons, I fixed one of rssreader-app tests <balloons> Letozaf_, excellent ;-) <Letozaf_> balloons, I will propose for merge <balloons> tested on the phone eh? <Letozaf_> balloons, argh! not yes just on the desktop, I will do it now :P <Letozaf_> balloons, on the phone I got one failure on 3 tests now, used to be 3 <balloons> Letozaf_, excellent <dkessel> good evening. does it help to get a bug fixed if i convince people to say "i am affected by this bug" on launchpad? balloons ? ;) <dkessel> oh... there goes indicator-datetime again.... <balloons> dkessel, that turns up the bug heat <balloons> high heat / priority bugs would get looked at sooner :-) But developers are developers.. <dkessel> mhh :/ well bug 1179180 is both old and annoying and has heat of 94 already.... <ubot5> bug 1179180 in empathy (Ubuntu) "Impossible to open Empathy contact list window if already started with '-h' option" [Undecided,Confirmed] https://launchpad.net/bugs/1179180 <dkessel> try convincing your gf that ubuntu is easy to use and she can simply chat with you by clicking..... "oh, well that does not work... let me see..." .... <dkessel> ok checking the list... heat of 94 is nothing for the empathy package... top heat entry is 1586... <balloons> dkessel, weird bug <dkessel> annoying one :p <balloons> nice workaround someone posted, heh <dkessel> yup :) we can make that a patch for the empathy package then :p... a modified .desktop file <balloons> lol.. I use pidgin :-) <balloons> althought honestly I mostly just use IRC.. <balloons> which is netheir pidgin nor empathy <dkessel> thinking of switching back to pidgin too... <balloons> elopio, wjat <balloons> is up with the weather app? <dkessel> sigh... finding my phone using my laptop's bluetooth is broken too... <samgabbay> anyone know how to decrpt a openpgp key? <samgabbay> for launchpad <elopio> balloons: it's using a lot of indexes, that now are not returning the right components. <elopio> thomi: I think you can also approve the clock branch. <balloons> elopio, everything is still unamed eh? <balloons> dkessel, broken as in broken by the update to saucy or ? <elopio> balloons: yes, this is not an easy app. <dkessel> balloons, not sure if it was already broken in raring tbh <elopio> take a look at my workaround: today_item.get_parent().get_children_by_type('QQuickItem', focus=False, z=1) <balloons> elopio, whoa.. is that for the search <elopio> I'm not proud of what I'm doing :( <elopio> that's because we have two quickitems, one for today and one for tomorrow. <elopio> I don't know how to assign the object names for them on QML. I'll report a bug, but for now we need to work it around for autopilot 1.4. <balloons> elopio, which <elopio> balloons: which what? <elopio> sorry, I didn't see the ping. <elopio> https://code.launchpad.net/~elopio/ubuntu-weather-app/autopilot-1.4/+merge/194036 <elopio> is it too bad? ^ * balloons looks <balloons> hmm.. we should be able to get objectnames for labels <elopio> balloons: yes, but I'm not sure how to do that. robotfuel has a branch that adds an emulator for the comboboxes <elopio> but he's also using the text of the labels. <balloons> elopio, I can add them.. * balloons grabs branch <elopio> :D <robotfuel> balloons: ping me if you want help :D <robotfuel> elopio: you have to add the OptionSelectorDelegate and ListElement options as a dictionary <elopio> that sounds nice. <robotfuel> elopio: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/view/head:/examples/ubuntu-ui-toolkit-gallery/OptionSelectors.qml if you look at the custom model here you can see where it needs the objectName <elopio> robotfuel: I think the optionselector emulator is pretty high priority. Would you be able to push that branch this week? <robotfuel> elopio: I have a bug open ithikar said we were not suppose to update the examples <robotfuel> elopio: the devs had to do it. <balloons> robotfuel, elopio it seems the objectnames exist for what i'm seeing atm in your branch elopio <robotfuel> elopio: after 1.4 stuff lands I will push the branch <elopio> thanks robotfuel <elopio> balloons: like where? the unit combo boxes? <balloons> OptionSelector { <balloons> id: unitsSelector <balloons> objectName: "UnitsSelector" <balloons> indeed you are doing units_selector.select_single <robotfuel> balloons: I think he means the labels in the option selector does not have object names. <robotfuel> elopio: ^ you want objectNames for the labels in the option selector? <elopio> robotfuel, balloons, yes, for the options in the selector. <balloons> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1234020 <ubot5> Ubuntu bug 1234020 in Ubuntu UI Toolkit "gallery example app: OptionSelectors should have objectName property to make it testable." [Undecided,Fix committed] <balloons> I'm not sure I've ever needed to go beyond that.. hmm <balloons> I think I tried to abstract it a bit more and grab based on the order #ubuntu-quality 2013-11-06 * balloons wonders about specifying a delegate <balloons> ah-ha, yeppers <balloons> I think I got you elopio :-) <elopio> :) that's the kind of english that I don't get. <elopio> balloons: do you mean that you could add the objectNames, or that you couldn't? <balloons> elopio, lol :-) Yes, I believe I can add the objectnames by adding a delegate, and defining the listmodel <balloons> it sounds more confusing that it is.. <balloons> let me confirm now <elopio> awesome. <balloons> woot <balloons> got it.. <balloons> so you can grab the delgate by objectname and check there text values <balloons> or whatever you want <elopio> balloons: that's just what I want. <elopio> will you propose a merge against trunk that I can use as a prerequisite? <balloons> sure thing <elopio> balloons: oh, wait, no, because I already have a prerequisite. <balloons> elopio, I'll just pass you the qml <balloons> you can adjust your merge then <elopio> balloons: or propose your branch against mine. <elopio> whatever you prefer. <balloons> i'll push a branch, you merge to yours, commit and we'll go with your mp <balloons> shoot <balloons> the short version didn't work and i didn't commit the long one.. haha.. redoing <balloons> there is one caveat, it break internationalization, if I have to do the other way... <balloons> elopio, lp:~nskaggs/ubuntu-weather-app/optionselector-objectnames <balloons> I think I have to define the listmodels again, which breaks internationalization due to some weird thing with qt not liking me using non literal values <balloons> see if that's enough or not <elopio> balloons: I think that's not what I need, I might be explaining it bad. I need the option with text "Millimeters" to have an objectName="milimetersOption", or something like that. <balloons> yes elopio I know.. I'm going to have to add the listmodel's too <balloons> just sucks because it won't let me assign the internationalized strings <elopio> I think I need a break, I'm just going slower and slower. <elopio> and while the maguros are stuck, there isn't much I can do. <elopio> or do you need me now for something else thomi? <balloons> elopio, ok, pushed the version with listmodels <balloons> you can select like OptionSelectorDelegate, objectName = WindUnitsSelectorDelegate <balloons> you'll get multiple returns, you can check the text, and see which one is selected <balloons> selected = True <thomi> elopio: sure, I'm just approving branches as they come up <elopio> I'm sorry balloons, I'll check it after a little rest. <elopio> be back in a while, <balloons> this bug sucks: https://bugreports.qt-project.org/browse/QTBUG-20631 <balloons> elopio, alrighty, whenever you are back around. int'l string support works again.. ugh, so silly <balloons> that was my qml limit for the day <elopio> balloons: still around? <elopio> veebers: the keyboard tests failed: http://(502)257-5948:8080/job/autopilot-trusty-master/58/ <elopio> can you please take a look? It might be because of this autopilot-trusty-master environment. <veebers> elopio: d'oh, sure can <elopio> thomi: I left rss and weather apps running on autopilot-trusty-master <elopio> I'm going to have dinner, and then I'll be back to check how they went. <thomi> cool <elopio> it's all updated on the etherpad in case you guys want to give them a push. <elopio> bbl. <DanChapman> morning all <elfy> hi DanChapman <DanChapman> hey elfy :-) <Noskcaj> hey DanChapman <DanChapman> Noskcaj, hey mate :-) <Noskcaj> Have you got time to finish off the testdrive gtk3 work? I'll try to port to python3 when you finish (breaks quickly), so it's probably not worth starting from scratch like you did. All that still needs doing should be fixing glade's files and adding gsettings <DanChapman> Noskcaj, I've just got to take my boy to school can i talk to you about it when i get back? <Noskcaj> DanChapman, Sure, as long as i'm not asleep then <Noskcaj> bye <DanChapman> jibel, hey i read on yesterdays logs you had some concerns with the ubiquity tests picking a random language each time. Would it be better if I was to create a 2 testcases for each scenario 1 in english and the other picks a random language?? <davmor2> Morning all <elopio> hello everybody. <TheLordOfTime> o/ <davmor2> morning elopio <elfy> DanChapman: does autopilot work with thunderbird? lderan is too scared to ask :p <balloons> elfy, I get Gtk-Message: Failed to load module "autopilot" <DanChapman> elfy it does but only using process manager which means we are unable to introspect it like other autopilot tests and can only check things like the window title and window visible etc. <balloons> so I would say no introspection support <elfy> thanks guys :) <elfy> probably the same with mousepad then - I think was the same issue <balloons> autopilot launch -i Gtk leafpad <balloons> Gtk-Message: Failed to load module "autopilot" <elfy> I can see us getting a lot of that :) <elfy> on another related note - how's autopilot and images looking for the likes of us? <DanChapman> same with mouspad "Gtk-Message: Failed to load module "autopilot"" <balloons> elfy, thunderbird is not a surprise butthe others are <balloons> might be able to fix those with some investigating <elfy> balloons: cool <DanChapman> is mousepad gtk2? <elfy> I thought gtk3 - but I could be wrong * elfy really ought to do himself a list <lderan> DanChapman & balloons thank you :) <DanChapman> Your welcome lderan :-) <balloons> not sure what I did ;-) but you are most welcome <DanChapman> elfy i missed your question just then. Last i read on image testing for your lot was jibel was activating it yesterday. I'm not sure what the status is on that today though <elfy> aah yes - I remember seeing that now - sorry <DanChapman> :-) <elfy> I don't even know where to go to see results lol <DanChapman> elfy, https://jenkins.qa.ubuntu.com/job/autopilot_ubiquity-devel/ <elfy> DanChapman: thanks <DanChapman> elfy no problem. Thats the ones that are running atm. When the ones for the flavors come up i'll send you the link :-) <elfy> woohoo :) <balloons> DanChapman, re: language.. yes english + random <balloons> imho <DanChapman> balloons, ok mate easy enough to do <balloons> great.. jibel can toss in, but I believe that was the idea.. having an english install keeps things consistent between tests <elopio> balloons: they merged the weather without your objectName changes. I think now it would be good to wait for the optionselector emulator, and fix it in the nicest way possible <elopio> what do you think? <balloons> elopio, I saw that :-( <balloons> as far as the emulator, wouldn't you still need to define the objectnames? <elopio> balloons: yes. We need both. So what I'm asking is if you want me to continue your object names branch and merge it today, or would you prefer to wait for the emulator and do the objectNames+emulator when it's ready. <balloons> elopio, I'd put it in now, may as well.. in case any work is done in that section of the qml <balloons> leaving it out means it may not merge clean later <elopio> balloons: ok, I'll grab your branch now or I will forget. <elopio> balloons: today and tomorrow I'll be cleaning tests everywhere I can :D If you want something, assign a bug to me. <balloons> elopio, ;-) got t <TheLordOfTime> balloons: ping <TheLordOfTime> has that session RE: bugsquad/QA merging had a specific time/date set? <balloons> TheLordOfTime, setting it now.. and I'm expanding the session list as it's been pointed out I was thinking rather superhumanly that I could get the whole agenda done in one session <elfy> http://summit.ubuntu.com/uds-1311/meeting/21987/community-1311-quality-bugsquad/ <balloons> http://summit.ubuntu.com/uds-1311/meeting/21987/community-1311-quality-bugsquad/ <elfy> ahah - didn't see you there balloons :) <balloons> lol.. that was in sync <elfy> spooky * elfy should be about (ish) on the Tuesday/Wednesday - try and get a bit more involved this year - as much as is possible with only IRC <TheLordOfTime> balloons: awesome, now that this is on my calendar i can see i have to be awake before 2. <TheLordOfTime> which is easy. <balloons> elfy, IRC works fine ;-) just having you around would be lovely <elfy> balloons should tell the rest of the people in his team that if they aren't talking then they should be checking IRC channels as people often get ignored ;) <elfy> well - it does up to a point :) <balloons> it's hard to multi-task sometimes if I'm doing the talking as well <balloons> but I'm getting better <elfy> I wasn't saying you :) <elfy> tbh - anyone on any of these sessions who's there on video that isn't talking should be aware of IRC :) <elfy> balloons: there - does that sound like I'm not pointing fingers now :) <balloons> elfy, lol.. I speak only for me <elfy> usually when I say something on IRC - it get's noticed too late and the talkers are then talking about something else <balloons> no finger pointing felt <elfy> probably should have said this in #u-c-t :) <elfy> so I did :) <balloons> nice <elfy> I think that makes sense :) * elfy keeps thinking about getting a webcam - but the cost of getting a balaclava at the same time just tips it over the edge :) <balloons> elfy, I'll kindly remind you that you can join audio only <balloons> webcam is not required.. but a mic is :-) <elfy> yep - I know that - then I'd have to buy earplugs ... :) <balloons> elfy, TheLordOfTime see my last email to the qa list for an updated look at the sessions <elfy> when I actually do it - I'll do both :) <balloons> let me know if it makes sense :-) <elfy> stupid tbird filters - mails are in -release ... <phillw> balloons: ping <balloons> phillw, pong <elfy> balloons: looks fine to me - though "Let's talk about revamping calls for testing to let everyone in the community schedule there own" doesn't make sense unless you're mother tongue is English and you read the sentiment rather than the sentence <balloons> mmm.. well noted.. thank you <phillw> balloons: with the dropping of cadence from ubuntu, are you going for the alpha / beta stream, or just testing "whenever" until RC? <phillw> btw, hi elfy I also hope you are well! <elfy> hey phillw - I'm almost always well - I trust you are kicking too :) <balloons> phillw, I hope this is thoroughly covered and communicated in exploratory testing session, https://blueprints.launchpad.net/ubuntu/+spec/community-1311-quality-community-exploratory-testing, however yes <balloons> in other words.. I'd like to have people testing all of the time, all cycle <balloons> and using the release as there daily driver <phillw> balloons: and for the flavours who prefer milestones? <balloons> also allowing for people to schedule there own calls for testing, so rather than cadence weeks, perhaps we'll have more special calls for testing <balloons> https://blueprints.launchpad.net/ubuntu/+spec/community-1311-quality-calls-for-testing <balloons> phillw, for flavors on milestones, nothing changes.. you will do your milestones as usual.. <balloons> as will ubuntu ofc <balloons> we simply opt out of the earlier ones <elfy> HA - I'm trying to sort out cadence type testing for us lol <balloons> i think that is a sane enough way to think of it <elfy> which is more than we've done before <elfy> I sort of hope to get people on the packages.qa bandwagon and just test test test <phillw> elfy: I tried it with lubuntu, it was a big failure. nothing like a dead line to stir the testers into action :) <balloons> elfy, yep <elfy> so - a bit of the old and a bit of let's try this for us and see how it goes <balloons> you might consider pushing exploratory testing, using the release all the time, and then have specific calls for testing <balloons> aka, like milestones for packages <balloons> heh <elfy> phillw: well we did get all the package testing we'd asked for done <balloons> ^^ rather impressively <elfy> balloons: from our point of view - we are going to have very specific things land needing testing - but mostly it is abouit get more than 20 people testing stuff <phillw> balloons: elfy as package testing <> iso testing, when a new release of a package arrives, it is justifiable to ask for a test of it. <elfy> I'm trying to look ahead at the same time as deal with LTS <elfy> phillw: up to a point <elfy> we want more people testing - more people = different ways of using an app <elfy> a test can only cover so much <elfy> so ... constant testing/specific tests for specific issues/someone available to fix them <elfy> it's really about eyes <phillw> elfy: as balloons just said, do we have more than 20 testers to descend on a test? I think not, certainly for the flavours. Smoke testing, however, is a better route IMHO. <elfy> well I plan to have more than 20 by the time LTS releases <phillw> for 14.04 lts, we need some sort of 'stable' pre-release (alpha) and get people to actually USE it, not try to write tests :) <elfy> I do not want Xubuntu to release with something like the sound indicator issue again <elfy> phillw: agreed :) <elfy> we'll not be writing tests :) <phillw> elfy: we had issues with lubuntu as well :) http://ubuntuforums.org/showthread.php?t=2182038 <phillw> stuff that we never smoke tested. <elfy> oh I know other's had issues - but they are, while important, not as much so to me :) <phillw> I had only the zram issue which was solved.. It is not until people actually start using the release do we find out that all the work on auto-tests etc. count for nothing as they can not simulate "real life" :D <phillw> Never try to 2nd guess a user :P <elfy> indeed - it's trying to get the few happy to run a dev and released version at the same time <phillw> good evening from the UK Noskcaj <elfy> takes someone willing to play with fire a bit - at least someone without a /home ;) <elfy> hi Noskcaj <elfy> I'll be running tahr properly next time I get week off <phillw> elfy: IMHO, I do think that is doable... <elfy> I do as well with some cajoling <phillw> elfy: these were my thoughts, which got copied over... https://wiki.ubuntu.com/QATeam/Overview/TheStages <phillw> we do now have a decent set of instructions for using VM's. <phillw> goes and fines some super-glue for Noskcaj <balloons> the goal with exploratory testing is to get more eyes on the release sooner.. <balloons> there's no reason to not be running trusty right now for quality team members :-) <elfy> there is here balloons - I've not had time to set up the media mount properly ... <TheLordOfTime> thanks for the +1 on my answer about private bug triage, on Ask Ubuntu, elfy xD <TheLordOfTime> sorry to add noise, though, to the channel :) <qengho> phillw: Heya. I'm interested in getting help testing chromium-browser for stable releases. <qengho> phillw: I've been using the distro development edge to look for and fix problems, but that doesn't get the right bug reports to me quickly enough. <qengho> phillw: Have any advice? <elfy> TheLordOfTime: welcome :) <phillw> qengho: I'm only a tester now! But... the guy looking after chromium is a good guy from my previous involvements with him. https://launchpad.net/~chromium-daily/+archive/stable Chad is his name, and from memory, he would like people to test and report back. I always do. <elfy> TheLordOfTime: it actually is ontopic in here anyway :) <TheLordOfTime> indeed. <TheLordOfTime> elfy: i quoted information and put it there, but the wiki and "HOw to Triage" is the best guide out there <elfy> aaand really easy to read ;) <qengho> phillw: Oh, er, I'm Chad. And thanks. :) <elfy> TheLordOfTime: just saying :p <elfy> qengho: lol <TheLordOfTime> elfy: heheh <TheLordOfTime> elfy: true. The answer on AskUbuntu is a TL;DR version of the how to triage guide xD <phillw> qengho: oops! But I will continue to test chromium for you :) <TheLordOfTime> at least, specifically for crash bugs <elfy> yep <TheLordOfTime> IDK about security bugs or other projects, because i'm not on the security team, and because other projects have their own guidelines xD <elfy> :) <phillw> qengho: I'm currently on Version 30.0.1599.114 Ubuntu 13.10 (30.0.1599.114-0ubuntu1~cm0saucy) do you want me to try a newer version? <qengho> phillw: hah, thank you. I'm going to try to get most recent LTS and most recent stable release updated really often in a place where I can just hand tested results to security team to release. <phillw> qengho: I did install 14.04 pre-alpha today for lubuntu, let me just fire it up and see what version it has <phillw> qengho: ah, we switched back to firefox! Would it be helpful for me to install it and check what version it is on? <qengho> phillw: Well, for now that'd be precise and saucy that I'm most interested in. I'm dev/trusty at least has my eyes already. <phillw> qengho: I'm running 13.10 as my system (have been since alpha 1 was passed for smoke testing). The only issue I have with chromium is that it has run-aways in CPU usage with facebook. <qengho> phillw: huh. Report that Facebook problem? Shift-ESC to list processes. <qengho> My Facebook tab gets 2% to 0% CPU. <phillw> qengho: I just kill the process and restart the tab :) <elopio> balloons, robotfuel: review please: https://code.launchpad.net/~elopio/ubuntu-weather-app/fix1248648-options_object_names/+merge/194217 <robotfuel> elopio: this is for 1.3? <elopio> robotfuel: no, 1.4. <elopio> ahh, right, it's full of Eventually(Is(Not(None))) I need to clean that up too. <robotfuel> self.assertThat(lambda: self.main_window.select_single('OptionSelector', objectName='TemperatureUnitsSelector'), Eventually(Not(Is(None)))) should just be wait_select_single <elopio> robotfuel: I'll clean that in a different branch so we keep issues separate. <balloons> :-) <balloons> elopio, makes sense.. one thing at a time <robotfuel> elopio: I don't like that it's using an index <elopio> balloons: I basically reordered the things you had. How can I be sure if I'm not screwing the i18n ? <robotfuel> elopio: can you give an object name to the item in the option selector? <elopio> robotfuel: index where? That's precisely what I'm trying to avoid. <robotfuel> current_option = units_selector.select_many('ShapeItem')[1] <robotfuel> for example <elopio> robotfuel: yes, that's bad. But again, I would prefer that for a future clean up. <elopio> I would like to split the tests, and get most of those methods on a settings page emulator. <balloons> elopio, I see.. I too had tried to re-use a generic unitsSelectorDelegate but had trouble with it <robotfuel> elopio: ok <balloons> elopio, the int'l thing is that you need to translate in the delegate.. that was the magical secret. listelements can't use functions to set properties <balloons> too me awhile to come around to that conclusion :-) <dkessel> good evening <balloons> dkessel, guten tag <dkessel> guten abend balloons <balloons> guten abend I suppose <balloons> :-) <dkessel> yay, new indicator package updates... finally =D <dkessel> and lightdm... +1 :) * slickymaster is away: (Dinner time) <elopio> balloons: I would also like to get reviews from the app devs, so they know how and why we are cleaning things. <elopio> who can I get from the weather app? <balloons> elopio, mbo is the man for weather <balloons> let's ping him <balloons> not around :-( <balloons> we can email him <elopio> balloons: thanks, I'll send an email. <balloons> elopio, need the email? <elopio> balloons: I can dig for it on launchpad. No need to take more of your time :) <elopio> balloons: would it be a good policy to have an approval from one QA and one dev on every branch? <elopio> or would it be too slow? <balloons> elopio, we should think about that.. for this 1.4 stuff, let's get it in <balloons> moving forward, I think it would be good <balloons> in the past it's been 50/50.. I don't see every merge that doesn't affect tests and vice versa for devs <elopio> ok, I suppose this is part of the things we will try this cycle focusing on two projects at a time. * elopio eats. <balloons> dkessel, still on saucy right? <dkessel> balloons, yup... I am. why are you asking? <balloons> just curious.. I'm not going to ask you to jump through any hoops ;-) <balloons> gonna be able to make the vUDS stuff? <dkessel> the vUDS stuff ?-) <dkessel> oh i see. <dkessel> no i guess not... i have to work <balloons> :-( That work thing <dkessel> so now I placed a reminder in my calendar to review the videos/results after it :) <balloons> dkessel, that works too.. feel free to add comments in advance on the blueprints or pad <dkessel> ok fine :) <balloons> hehe.. I value your opinion.. <balloons> Letozaf_, buonasera <Letozaf_> balloons, buonasera <balloons> come stai? <Letozaf_> balloons, :-) bene e tu ? <balloons> bene :-) <balloons> rss reader treating you well? <Letozaf_> balloons, no :( I merged this evening before continuing yesterday's work and found some new failures, I'm trying to fix them :P <dkessel> balloons, is this about usb-creator-gtk? https://wiki.ubuntu.com/ubuntu-usb-startup-creator <balloons> dkessel, heck ya.. cool stuff huh? <dkessel> balloons, mh. well... partly :) improving the usability - yes. not allowing me to create booting usb devices from other linux OS'es - definately no <balloons> well, this is a community proposal.. I didn't catch the plan to only support ubuntu and nothing else <dkessel> i like the "making stuff easier idea" - but the unetbootin approach also has a plus... maybe it would be possible to talk with the authors if they would accept a "simple mode" <balloons> certainly the ubuntu use case is the primary one <balloons> anyways, do add your thoughts to the proposal <balloons> we'll discuss them <balloons> Letozaf_, how's about you? going to be able to make vUDS? <dkessel> balloons, yes it is a community proposal :) I'll comment on it <Letozaf_> balloons, hope so, maybe I will be a little late but I won't miss <balloons> me <3's community
{'channel': 'ubuntu-quality', 'month': 11}