[00:14] elopio: good question, I print_tree'd the unity proxy object and found it that way [00:15] elopio: I'll see if I have any logs left over that I cn use to find ie, otherwise I'll have to suggest you generate the log sorry (don't have a device handy right now) [00:15] veebers: that's ok. I can do the print and grep. [00:16] elopio: ah, I found this snippet, I presume it's correct :-) http://paste.ubuntu.com/9826927/ [00:16] elopio: sorry I couldn't be of any more direct help [00:17] I tried that and didn't work. I'll retry, I might have done something wrong. [00:18] elopio: hmm, also try grep __orientationAngle in the ubuntu ui tk sources [00:45] balloons, until i forget this... i think we should have two main "paths" in the QA docs [00:46] balloons, the other being for new contributors, that's the "Roles" path, which is pretty well laid now up until the actual documentation on how to get started [00:46] balloons, and the other being the "toolbox" for advanced people working with stuff [00:46] balloons, the latter should have probably most of the links to tutorials and stuff handy at least [00:47] balloons, but in a more concise format... and if anything is explained there, then we should be able to expect they know the basics already [00:48] balloons, in addition to those, we'll of course have the calendar and contact stuff, but that's just general information [00:53] balloons, and as you might have noticed, didn't mention the FAQ... because i believe it was only needed (if it was) because the new contributor documentation was a bigger mess than it is now, and what we want to make it [01:41] knome, interesting. I'm not sure how this toolbox would look, and it's interesting you would want to put tutorials in the advanced section [01:41] i'm ok with the thought on the faq [01:42] balloons, don't overthink it... just consider it as a landing page for most of the content we have scattered around [01:43] hmm ok, I'm seeing something [01:44] again, since it's for people who are already sticking around, we don't need the bling, we just need it to work [01:46] veebers: it's finally working the rotation. [01:46] elopio: oh cool, what was the issue [01:47] the set up is a little complex, we need two threads running at the same time. [01:47] ricmm has pushed the code. I have some details in my phone that I will push, and then I will ask you to make a new review. [01:48] I need to clean up my tweaks to use threading instead of thread, and a wait instead of a sleep. [01:48] but I could use the four orientations and the app turns around. [01:54] elopio: why the 2 threads? Also, I refreshed the MP and I'm a little concern that the fixture is starting unity but UnityTestCase start unity by default (unless you set an obscure member variable). I think that should be improved [01:54] but I don't have an answer for it right now [01:54] veebers: UnityTestCase doesn't start unity. IndicatorTestCase does. We need to change that. [01:54] perhaps (if it doesn't already exist) create a decorator for the unity tests to wrap around the setting of that flag [01:55] and the thread is because while unity is starting, we need to put some content on the sensors fifo. [01:55] otherwise, unity will wait forever. [01:55] and we can't put the info before because the fifo file needs the unity pid. [01:56] elopio: ah right, I could have sworn that the testcase started unity (I had to do something with the sanity tests suites from prev sprint [01:56] ) [01:57] I'm going to take a big break now. bbl. [01:57] elopio: I might not be online when you get back [01:58] have a good weekend elopio. You did great work this sprint! [01:59] veebers: yeah, I will probably finish tomorrow, but this won't land before your monday. You will have plenty of time to look at it and request more things from ric. [01:59] veebers: thanks! you too. [02:17] elopio: fyi have re-reviewed (and by accident 'approved' it (then re-commented with the NFing) [02:22] off to sleep, nighty everybody and balloons, get some rest as well, you sleepy man ;) [02:26] night knome ! === chihchun_afk is now known as chihchun [12:32] balloons knome - front page for manual testcases - or at least a start ... https://wiki.ubuntu.com/Elfy/Sandbox [12:36] elfy, looks good to me [12:37] though i'd probably cut off the contact stuff and just go on with the actual content if this was to be the testcases startpage [12:37] the page will have the QA header where we have the contact link anyway [12:38] the learn more bits? [12:38] If you want to talk to someone about manual testcases then there are 2 main ways to do so. [12:38] We recommend subscribing to the Ubuntu Quality mailing list. [12:38] Also consider stopping by on IRC and saying hello in realtime! We hang out in the #ubuntu-quality IRC channel on the Freenode IRC network. [12:38] that [12:39] and unless you plan to extend the previous section, that too probably [12:39] since we go through what is required to do X in the roles documentation [12:39] oic - well I did think about that - but I added them because someone might bookmark that page and not others [12:39] in that case we should have the contact info on every page [12:39] but not that bothered on the otherhand [12:39] that gets repetitive quickly [12:40] and if it's always at the top... it'll look like we only care about those things, not the content [12:40] ok - can see that [12:40] if we feel like that's needed, we can design a contact footer or sth [12:40] how about on pages that aren't the front page - making Ubuntu Quality at the top a link to the main page [12:40] but tbh i'd just trust people being able to connect the dots and see the contact page :P [12:41] just include the QATeam header on every page that is in the QATeam tree/path [12:41] unless it's clearly a common page, in which case just leave it [12:42] and by tree/path i mean every page that is discoverable just by looking at the QA wiki and wondering what you should do [12:44] looks ok with the header imo [12:44] changed it [12:44] yep [12:45] \o/ [12:46] need seperate pages for manual and automated perhaps now [12:46] this one being the new manual page [12:46] well, you could also lay them on top of each other [12:46] but sure, many of the actual content links are different [12:46] but i'm not opposed to separating them either [12:47] no idea what you mean - currently both are at https://wiki.ubuntu.com/QATeam/ContributingTestcases [12:47] yeah, that's icky [12:47] just separate [12:47] as long as the content is good... :) [12:47] https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual_Testcases [12:48] that? [12:48] you lost me [12:48] :D [12:49] that ok as the new page url? [12:49] just overwrite the current [12:49] mmm [12:49] we'll save one redirect [12:49] the current includes automated [12:50] https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual [12:50] nope [12:50] hmm, right, that's used for a different usecase [12:50] that's the page linked to from the front page at Writing :) [12:50] just move that under /Writing [12:51] and replace it with the new page [12:51] ok [12:51] if people have bookmarks, it's easy enough to update them since the new page is clean [12:51] you're making no sense - need tea ... [12:51] heh [12:51] once that's done, let's link directly to that page from the testwriter role page [12:51] currently we link to the mishmash page [12:52] that being https://wiki.ubuntu.com/QATeam/ContributingTestcases [12:56] https://wiki.ubuntu.com/QATeam/ContributingTestcases/Writing being the new page ? [12:56] no [12:56] let me try to be clear:D [12:56] that'd help :D [12:57] ~ = ContributingTestcases [12:57] that clear? [12:57] yep [12:57] so move ~/Manual to ~/Manual/Writing [12:57] then replace ~/Manual with your new landing page [12:57] right [12:58] I did the one you said no to - so that'll need deleting :p [12:58] then let's link directly to ~/Manual, not ~, from the role page (i can do that) [12:58] oki, i'll do that [12:58] done [12:59] hang on [12:59] yes? [12:59] I can't replace /Manual with the new landing page [12:59] you must manually copy the contents [12:59] not what I mean [12:59] oh... [12:59] why can't you then? :) [13:00] oh right - just need to update links in the new landing page - as one of those links to /Manual currently [13:00] heh, yeah [13:00] I've got so many wiki pages open currently ... [13:00] i know [13:00] it's horrible [13:00] especially with only one monitor.. [13:00] yea :) [13:02] updated https://launchpad.net/ubuntu-manual-tests [13:03] eh [13:03] not that! [13:03] https://wiki.ubuntu.com/QATeam/ContributingTestcases [13:03] that [13:03] now only has a link to that new landing page and to the lp project page [13:05] ok - done that now [13:05] goodie [13:05] it's good to see things moving forward again.. [13:05] so /Manual is now a landing page [13:05] yep [13:05] and /Man/Writ has the old stuff in it [13:05] and it's linked to from https://wiki.ubuntu.com/QATeam/Roles/TestWriter directly [13:05] so no more detour [13:05] ++ [13:06] yep [13:06] i'll give https://wiki.ubuntu.com/QATeam/ContributingTestcases/Launchpad a slight nudge next [13:07] I'm just going to work through the pages on the new landing page today [13:07] so you can leave that if you like [13:07] nah, [13:07] it'll only need a visual update tbh [13:08] ok - I'll wait and see what you do then before I fiddle with the others - at least make pages we're freshening up look the same (ish) [13:08] if nothing else we'll all know which ones have been looked at :p [13:08] i'll make it look like https://wiki.ubuntu.com/QATeam/DevelopmentSetup [13:09] right [13:09] lunch time I think [13:09] ok, bon appetit :) [13:47] knome: so at the moment - the new landing page is a bit circular - points to contributing test cases - which then points to it [13:48] though contributing does include automated as well [13:49] heh [13:49] i'd say remove all links back to the upper level [13:49] so - lose the first box [13:51] yea was trying - that's the trouble with complicated wiki syntax and copy pasting it [13:52] so I gave up for the moment :) [13:52] hehe [13:52] i can do it [13:53] what happened [13:53] oh [13:53] heh [13:53] i fail [13:54] only took three edits :) [13:54] heh [13:54] and fourth to fix the padding [13:55] really not sure about the contact icon ... perhaps it's me - but it looks like it's stoned [13:56] haha [13:56] a bit [13:56] fortunately we can change it ;) [14:04] fwiw, i think QATeam/ContributingTestcases/Launchpad should be renamed to probably QATeam/DevelopmentToolsSetup [15:19] knome: yea - I'd probably agree with that - I'd say that QATeam/ContributingTestcases/ManualStyleGuide/test_case_format_script could be on the same page tbh [15:19] yep [15:20] so maybe the page should be named DevelopmentTools [15:21] the launchpad one? [15:22] and add the script to that - makes sense to me [15:22] yep [15:23] then it could be the number one place for all development tools [15:23] yep +1 to that [15:25] working on that now [15:27] actually... [15:28] i think the script should be in the ubuntu-manual-tests repository [15:28] that's a different kettle of fish altogether [15:31] sure, i can handle that [15:32] where's the qa tracker for Alpha 2? (lost bookmarks due to hardware glitch) [15:32] alpha 2 is released [15:32] knome: i still need the tracker :P [15:32] for future [15:33] * teward lost the link in bookmarks and history due to disk corruption [15:33] which qa tracker? ISO? [15:33] yep [15:33] http://iso.qa.ubuntu.com/ [15:33] knome: thank you kindly === alexabreu is now known as alex-abreu [15:34] knome: main reason for wanting it was to see what bugs were happening. [15:34] :) [15:34] http://iso.qa.ubuntu.com/qatracker/reports/defects [15:35] would be better then - that's got reported bugs on it [15:35] elfy: wanted to see it with the specific testcases [15:35] either works [15:36] * balloons sees more boxes :-) [15:36] just set up QATeam/DevelopmentToolsSetu [15:36] +p [15:36] I see ticky tacky balloons [15:36] knome: stuck on Windows, otherwise I would. [15:36] * knome pops a balloon [15:36] * teward isn't on his own computer right now [15:36] teward, would what? [15:37] knome: set up the dev tools on that page [15:37] can't do anything from campus systems >.> [15:37] no.. i meant i just set that page up. [15:37] ahh [15:37] oh joy, my computer asploded >.> [15:37] balloons, so, what about pushing the format testing script to the branch? [15:38] "sudo mv test-case-format /usr/local/bin" is.... uhh [15:38] knome, elfy I would be down for including a readme in the branch as well explaining it, etc :-) [15:38] * balloons doesn't move it to bin [15:39] i'm sure there would be other ways to check the markup than having to depent on vim too === roadmr is now known as roadmr_afk [15:50] Hello guys, I applied some grammar fixes this wiki page, https://wiki.ubuntu.com/QATeam/Overview/TheStages#preview. Have a look at it. [15:57] thanks sak [15:58] welcome ;-) === chihchun is now known as chihchun_afk [16:04] balloons: I had a question a while back which I'd forgotten - unfortunately for you I've now remembered it :) [16:05] what is all this stuff doing sitting in testcase/images? especially all the ones un-numbered and I guess not on the tracker [16:05] http://bazaar.launchpad.net/~ubuntu-testcase/ubuntu-manual-tests/trunk/files/head:/testcases/image/ubuntu%20touch/ [16:06] If I installed an alpha release using a CD/DVD disc to test on hardware, but would like to test other milestone releases, can I update my installed release to the next milestone release? [16:08] elfy, how interesting. I guess at some point it was to be used. We could remove it [16:08] as you said, it is not on the tracker === chihchun_afk is now known as chihchun [16:08] sak, yes once you've installed it, update it like any other normal installation of ubuntu. The updates just come in much more often :-) [16:09] if you wish to test the next version via installation, you can do that at that time as well [16:09] sak: there is no milestone for testing now until beta 1 [16:09] depends on the flavor, but for ubuntu, nothing until final beta [16:10] as soon as it's a new day and new updates - your using the daily === roadmr_afk is now known as roadmr [16:10] balloons: and that too :) [16:12] Ok, balloons and elfy. I read that is recommended to test milestone releases on actual hardware not just a virtual machine. Yet, I don't have a usb drive at the moment. Plus I prefer to use hardware. [16:12] I will only test milestones on hardware, dailies on a virtual machine [16:18] elfy, "you're" [16:18] pffft [16:18] I'm lazy :p [16:28] Lazy is good :-) [16:31] WHOA! present for me.. someone else on the internet used your for you're [16:32] * balloons feels SLIGHTLY less bad about his inability to speak his native language [16:35] I have it on the phone balloons [16:35] speeling or grummer error now and again to cheer balloons and knome up :) [16:49] elopio I see that our two pairing tasks are still marked as todo, do we intend to move them over? [16:54] alesage: not sure. We didn't define a good acceptance criteria for those. [16:55] ok, round two for https://wiki.ubuntu.com/Jams/Testing. I'm happy with it now [16:55] alesage: charles said that his bootstrapping was succesful [16:55] elopio, yes in our last Wed. meeting [16:55] indeed [16:56] paulliu: do you think that with the work we did these two weeks, you'll be able to keep writing these tests and teach your team how to do it? [16:59] elopio, I took the liberty of moving charles' and my card [16:59] alesage: yes, thanks. [16:59] alesage: pdf should go back to the TODO pile, right? [17:00] balloons, it's under review, waiting on Jenkins https://code.launchpad.net/~canonical-platform-qa/autopilot/pdf-build/+merge/247249 [17:00] oops elopio ^^ [17:00] was just going to welcome a balloons review of that pdf generation for autopilot docs [17:10] alesage, care to add json in there too, hehe? [17:10] I have a bug for getting json output, and since it's post sprint and you are adding things . . . [17:10] balloons let's make a new card for that :) #rainmakingFTW === chihchun is now known as chihchun_afk === rigved is now known as Guest11155 [18:02] balloons: hi. do you know how i can have adt-run use the tests from the local tree on a click package? [18:06] or anyone? [18:06] dobey, indeed. pass the folder as the first argument to adt-run [18:06] balloons: so adt-run . --click=../foo.click? [18:07] yep [18:07] someone needs to fix the docs if that's true [18:08] because --click-source=. doesn't seem to work, and that's what --help suggests to use [18:09] ohh really? bug filing time if so.. the args can be specified multiple ways generally [18:38] hmm, does self.launch_click_package() require the full app triplet with version #? [18:54] balloons: ok. so --click-source works, but only if it's *before* the --click argument. :( [18:55] so that seems like a bug, yeah [18:58] dobey, ahh.. I always used it before and parse order is clearly important. I wonder if it has to be [19:00] balloons: there's no good reason for these arguments to be required to be in a specific order [19:01] balloons: anyway, i filed bug #1414122 about it [19:01] bug 1414122 in autopkgtest (Ubuntu) "adt-run arguments are order dependent" [Undecided,New] https://launchpad.net/bugs/1414122 [19:01] excellent [19:02] now, why is self.launch_click_package('') timing out [19:02] hmm, maybe i can't use that === roadmr is now known as roadmr_afk [19:20] dobey, should just be app_proxy = self.launch_click_package( "com.ubuntu.music") [19:21] balloons: maybe it's because for payui to 'work' we have to actually pass it a uri? [19:22] dobey, you can pass it a uri too [19:22] http://paste.ubuntu.com/9838894/ [19:23] ah ok === roadmr_afk is now known as roadmr [19:51] gah, argument parsing order dependence strikes again :( [20:08] ** (run.py:4869): WARNING **: Unable to connect to Upstart bus: The given address is empty [20:08] hrmm, and that's not helpful :( === roadmr is now known as roadmr_afk === roadmr_afk is now known as roadmr === pgraner is now known as pgraner-afk [21:37] balloons, hi [21:37] https://code.launchpad.net/~carla-sella/ubuntu-rssreader-app/fixing-flaky-test/+merge/247482 [21:38] balloons, I am trying to fix the flaky tests, but now they pass :) and I fixed only one of them theoretically [21:38] balloons, what do you do in these cases ? [21:41] Letozaf_, fixing one might have been enough.. sometimes the following tests failed because of one. That said, keep going if there's more to fix [21:41] balloons, ok [21:41] trunk *sometimes* did work, so :-) [21:42] balloons, yeah that's why I was wondering what to do, how do I know if it will fail again :-P [21:46] Letozaf_, getting it to pass locally in the sandbox is a good start [21:46] I can help try to break it once you are done :-) [21:47] balloons, ok thanks, on my desktop it passes also in sandbox when I've finished I will let you try to break it [21:48] that sounds awesome :-) [21:48] :)