[06:38] <DanChapman> good morning all
[06:42] <elfy> hi DanChapman
[06:43] <DanChapman> elfy howdy :-)
[07:04] <jibel> good morning
[10:08] <slickymaster> morning all
[10:08] <DanChapman> morning slickymaster :-)
[10:08] <slickymaster> DanChapman: hi Dan, ;)
[10:09] <slickymaster> elfy: ping
[10:10] <davmor2> Morning all
[10:13] <DanChapman> morning davmor2
[10:18] <slickymaster> morning davmor2
[10:25]  * DanChapman is well impressed with the autopilot sandbox :-)
[11:06] <elfy> slickymaster: pong
[11:09] <slickymaster> elfy: good morning. I was planning on taking a stab at Forum Wiki Team, but it seems that there's nothing going on in team, is it stalled?
[11:09] <elfy> I think so - I've not had anything to do with it for a year
[11:10] <slickymaster> but do you think it's worthwhile?
[11:11] <hkker> hello
[11:11] <hkker> i want to get involved in QA, but my computer is so old that it's processor doesn't support virtualizing 64bit systems in virtualbox
[11:12] <hkker> is there any other way i can contribute?(32bit is way too slow in virtualbox, basically freezes my computer)
[11:12] <hkker> like maybe test live cd-s
[11:14] <DanChapman> hkker you can always run Saucy on your computer. were getting close to Beta now so its pretty stable and report any bugs you come across.
[11:15] <slickymaster> elfy: but do you think it's worthwhile?
[11:16] <elfy> well ... possibly if you can find a thread that could be wikified - not sure the team is worth resurrecting, the thread/wiki converter should still work
[11:18] <hkker> DanChapman : fortunately i have two hard drives so i can even install it OR i can make a LVM partition using the live cd. which one is more preferred in QA? in my view it shouldn't make a difference
[11:18] <slickymaster> elfy: I see. Well I won't waste much time on it, then. But if I do find one I'll do it then
[11:18] <slickymaster> thanks
[11:18] <elfy> welcome :)
[11:20] <DanChapman> hkker:  Everyway you can think of is 'preffered'. It all has to be tested somehow. :-) You could also get involved with contributing tetcases if your computer is not up to it https://wiki.ubuntu.com/QATeam/ContributingTestcases
[11:21] <DanChapman> hkker: and here is an overview of some more stuff you can contribute to https://wiki.ubuntu.com/QATeam/Overview
[11:21] <hkker> oh also, i have never ever tested anything so i might need some mentoring from someone who has the time
[11:22] <hkker> but i'm more or less quite fast learner, i just need some guidance at first. as i have read from these pages you linked, there should be enough information for now.
[11:24] <DanChapman> hkker, read those links also check out here http://iso.qa.ubuntu.com/ to see how we record our testing. And just fire any questions you have in here and someone will be about to help
[11:25] <hkker> thanks DanChapman
[11:25] <DanChapman> hkker: your welcome :-)
[11:25] <hkker> okay, ill do it later, i have a lecture
[11:28] <hkker> funny enough, the courses name is "Operating systems" and we are using win8(which i hate for obvious reasons) and 13.04 ubuntu. i just love it so i want to contribute somehow :)
[12:26] <pitti> Good morning
[12:26] <DanChapman> hey pitti o/
[12:26] <jibel> Good morning pitti
[12:27] <pitti> hey DanChapman, how are you?
[12:27] <pitti> bonjour jibel, comment ça va ?
[12:28] <jibel> pitti, ça va bien et toi? Comment se déroule plumbers?
[12:28] <DanChapman> pitti, I'm good thanks and yourself?
[12:29] <pitti> jibel: c'est bien, mais les derniers jours sont calmes
[12:29] <pitti> jibel: most of the talks happened Mo - Wed, yesterday and today are mostly workgroups
[12:30] <pitti> mais après deux semaines de conférences j'attends avec impatience à rentrer à maison
[12:34] <jibel> pitti, I can imagine :) Do you know if there are any videos/slides of the  talks? I didn't find any online.
[12:35] <pitti> jibel: they said they'll publish the videos etc. after the conf
[12:35] <pitti> jibel: slides are downloadable from the schedule, and I guess people put them into other places together with the notes
[12:35] <pitti> (I did so with umockdev)
[12:42] <pitti> thomi: having fun with https://code.launchpad.net/~thomir/autopilot/1.3-fix-warning/+merge/186640 ?
[12:42] <pitti> thomi: so is that now the first unit test which actually assumes having a running session bus?
[12:43] <thomi> pitti: fun?
[12:43] <pitti> thomi: i. e. which you need to run through dbus-launch --exit-with-session?
[12:43]  * thomi is confused
[12:43] <pitti> thomi: or should that be a functional test instead?
[12:44] <thomi> pitti: ahhh, I hadn't actually seen that
[12:44] <thomi> hmmmm
[12:44] <pitti> thomi: fun> I thought the PS test rejected that like 5 times already
[12:44] <thomi> I'll provide a fake instead I guess
[12:44] <pitti> but that could have been on another MP
[12:44] <thomi> yeah, first rejection
[12:48] <thomi> ugh, too hard to fake. Will make it a functional test instead
[12:49] <rvr> thomi: Trying to run an autopilot test on the phone "Tests running... Ran 1 test in 0.208s OK", so seems that it didn't run any
[12:49] <rvr> thomi: Any tip?
[12:50] <thomi> rvr: run with -v and see what test ids it's actually running
[12:51] <rvr> 12:51:00.558 ERROR __init__:63 - Unity doesn't appear to be running, exiting.
[12:55] <thomi> pitti: I wonder if you could do a quick review of this please? I just moved the test case: https://code.launchpad.net/~thomir/autopilot/1.3-fix-warning/+merge/186640
[12:55] <thomi> pitti: of, and if you could top-approve it when you're done, that would be awesome
[12:56] <asac> hey
[12:57] <asac> who is leading the avengers testing efforts if jfunk isnt on?
[12:58] <thomi> asac: I don't think anyone is nominated. jfunk should be on about now though
[12:59] <asac> ok i wait for a moment :)
[12:59] <pitti> thomi: meeting now, but queueing
[12:59] <thomi> elopio: ping?
[12:59] <thomi> pitti: thanks
[13:01] <pitti> thomi: ah, easy one, approved
[13:01] <thomi> pitti: I wonder if you could do this as well? It's kind of urgent: https://code.launchpad.net/~thomir/autopilot/1.3-fix-click-packages/+merge/186779
[13:01] <thomi> my merging from 1.3 <-> trunk introduced a regression in click package support :-/
[13:02] <thomi> top of my TODO list for 1.4 is to refactor that code so we can get it under test
[13:02] <thomi> but for now, I want to get it fixed and released into saucy
[13:04] <asac> mzanetti: ok so build 57 will go out as the regression seem to have happened in the latest we landed today. so next build is blocked
[13:04] <asac> mzanetti: i commented on the bug
[13:05] <asac> it seems reproducible against build 57 by first apt-get update
[13:05] <asac> and then installing the unity8 autopilot
[13:05] <mzanetti> ah... ok... didn't do the apt-get upgrade.
[13:05] <mzanetti> that's why I couldn't reproduce so far
[13:05] <asac> mzanetti: dont do an upgrade ... just apt-get update; apt-get install unity8-autopilot
[13:05] <asac> mzanetti: thats enough
[13:06] <asac> the dist-upgrade will bring you more stuff in and who knows what other funny behaviour you might be fighting first then
[13:07] <asac> jfunk-otp: hi
[13:07] <asac> jfunk-otp: importnat thing
[13:08] <pitti> thomi: yep, queueing
[13:15] <pitti> thomi: done
[13:16] <thomi> pitti: thanks!
[14:00] <elopio> good morning!
[14:00] <elopio> thomi: pong.
[14:00] <thomi> elopio: hey, sorry, I wanted some reviews, but I got pitti to process them
[14:01] <thomi> elopio: wasnt' sure what time you started :)
[14:01] <elopio> thomi: no problem.
[14:01] <elopio> I almost always start at this time.
[14:03] <thomi> I'll have to re-learn what that time is when I get home :)
[14:10] <elopio> thomi: do you return today?
[14:10] <thomi> elopio: I fly out tomorrow morning
[14:10] <thomi> get home on Monday morning
[14:14] <rvr> thomi: Do autopilot needs any kind of setup to run on the phone, besides su - phablet?
[14:14] <rvr> Like setting dbus session
[14:15] <thomi> rvr: don't think so, but you're probably better off using phablet-test-run, since (AFAIK) that's what the CI team uses, so any magic that's required would be encoded in that script
[14:15] <mzanetti> asac: if you do a dist-upgrade. is the crash still there?
[14:15] <thomi> rvr: and really you want 'sudo -i -u phablet'
[14:16] <thomi> rvr: oh, sorry, I misread that - disregard
[14:16] <thomi> it's early :)
[14:17] <rvr> lol
[14:20] <cgoldberg> thomi, quick MP: https://code.launchpad.net/~coreygoldberg/autopilot/change-tox-tests/+merge/186806
[14:20] <thomi> cgoldberg: on it
[14:20] <cgoldberg> thomi, I had to leave early yesterday.. do you still have AP reviews you need looked at?
[14:22] <thomi> cgoldberg: when I run 'tox' I get lots of flake8 issues
[14:22] <thomi> cgoldberg: I wonder if we should fix those in a separate MP
[14:23] <cgoldberg> thomi, i was running into that.  it's running clean for me now though.  try `$ rm -rf .tox` and run again
[14:23] <thomi> cgoldberg: since I just branched your branch, shouldn't it be clean to begin with?
[14:23] <cgoldberg> yup true
[14:23] <cgoldberg> hmm
[14:25] <cgoldberg> thomi, strange.. i get no flake8 errors.  "flake8: commands succeeded"
[14:26] <thomi> cgoldberg: http://pastebin.ubuntu.com/6132919/
[14:35] <thomi> pitti: or elopio - easy review: https://code.launchpad.net/~thomir/autopilot/fix-warnings/+merge/186639
[14:35] <thomi> that's the trunk version of the last fix
[14:41] <elopio> iahmad: I left a comment on your textfields branch.
[14:41] <asac> mzanetti: yes its still there
[14:41] <asac> mzanetti: check with ogra.
[14:42] <elopio> thomi: I'm looking at your MP, but I don't understand it. I'll read some more code.
[14:43] <thomi> elopio: pitti acked the first one - maybe just push it to his plate :)
[14:43] <elopio> yes. I'll still try to understand what this part of the code does.
[14:45] <elopio> thomi: and one PITA detail, according to pep257, the first sentence of a docstring should be just one line.
[14:46] <thomi> elopio: I know, and we should fix that, but this MP isn't about that, and it does make it *more* compliant than it was :)
[14:48] <elopio> thomi: agree.
[14:48] <cgoldberg> thomi, ok.. i can reproduce the flake8 errors you see now..  want me to fix them in this branch, or in a future one?
[14:51] <thomi> cgoldberg: I'm happy either way
[14:51] <thomi> cgoldberg: if you'd rather do it in a separate MP let me know and I'll approve your current one now
[14:52] <cgoldberg> thomi, umm.. I'll just push them in the same branch
[14:52] <cgoldberg> so feel free to reject the MP :P
[14:53] <thomi> nah, I'll just leave it un-approved
[14:53] <thomi> makes you look better :)
[14:56] <elopio> thomi: did you get my message about bug #1225026 still open?
[14:56] <thomi> elopio: nope
[14:57] <elopio> thomi: I upgraded using the experimental ppa, and it happens the same.
[14:57] <thomi> elopio: ahh, the experimental PPA is old, and needs to be deleted, sorry
[14:57] <thomi> or actually, maybe I should just update the build recipies
[14:57] <thomi> elopio: you need trunks
[14:58] <thomi> elopio: *or* autopilot from saucy
[14:58] <pitti> thomi: re
[14:58] <elopio> thomi: ok, let me try.
[14:59] <pitti> thomi: ah, LGTM; acking
[15:28] <elopio> thomi: yes, it works now. I'll mark the bug as fixed.
[15:28] <thomi> elopio: \o/
[15:29] <pitti> cgoldberg: reviewed your branch
[15:29] <elopio> thank you thomi.
[15:29] <thomi> :)
[15:29] <elopio> om26er: that was the bug that made the webbrowser tests to fail on my machine, in case you were wondering :)
[15:30] <thomi> elopio: can you close the bug for me please?
[15:30] <elopio> thomi: I marked it as fix released. Is that ok?
[15:30] <thomi> elopio: yup, thansk
[15:31]  * elopio goes out to feel the sunshine.
[15:31] <elopio> bbs.
[15:37] <cgoldberg> thomi, fixed all flake8 issues.. *all* were in docstrings/doctests
[15:41] <thomi> heh
[15:58] <thomi> does anyone know where I can find a list of all the indicators that should appear on the phone? It seems like today's build is missing bluetooth and messaging indicators, but I'd like to be able to confirm that before filing bugs
[15:59] <thomi> iahmad: balloons ^^ ?
[16:01] <davmor2> thomi: from what I understand messaging is a bug but bluetooth is dropped apparently
[16:04] <thomi> davmor2: OK. thanks
[16:54] <thomi> cgoldberg: your docstring changes to autopilot are incorrect I'm afraid
[16:54] <thomi> cgoldberg: for example: 36	+        >>> from autopilot import press
[16:55] <thomi> cgoldberg: that's not a correct import
[17:17] <cgoldberg> thomi, ah.  i'll fix
[17:50]  * elopio going for lunch.
[18:04] <thomi> cgoldberg: did you get anywhere with this? https://bugs.launchpad.net/autopilot/+bug/1206805 if not, I'll look in to it now
[18:27] <cgoldberg> thomi, not yet.. was gonna look at it this afternoon.  go ahead if you want :)
[18:28] <thomi> cgoldberg: OK, I'm on it
[18:34] <cgoldberg> thomi.. for those docstrings where I botched the import.. like: from autopilot import press.  what's proper way to import "press" for example
[18:34] <thomi> cgoldberg: well, it's a method on the class
[18:34] <thomi> cgoldberg: so I guess you'd need to show the entire process of creatingthe class, like:
[18:34] <thomi> from autopilot.input import Mouse
[18:34] <thomi> m = Mouse.create()
[18:34] <thomi> m.press()
[18:35] <thomi> for example
[18:35] <cgoldberg> thomi, most of the doc doesn't use doctests anyways... I could leave them as documentation examples, and remove the ">>>" so flake8 doesn't complain.. and revert the imports I used
[18:36] <cgoldberg> unless you want fuller examples in docstrings
[18:36] <thomi> cgoldberg: Right, I think maybe the best way is to not make them docstrings, but make sure we still get syntax highlighting in the docs
[18:36] <thomi> I bet you can't run them as doctests anyway
[18:36] <rvr> Good weekend, everyone!
[18:37] <cgoldberg> yea.. i can just put them as code snippets that sphinx will like (they mostly already are.. except for the ">>>")
[18:37] <cgoldberg> ... and i hate doctests anyway :)
[18:42] <jfunk-afk> balloons, we're talking about having a lightning talk next tuesday, is "Gating process" &/OR "Unity/SDK/Apps Integration Failures (and what we should do about them)" something you think anyone wouyld be interested in attending?
[18:42] <jfunk> nm - will email
[19:00] <thomi> hmmmm
[19:00] <thomi> cgoldberg: agreed onn doctests being awful
[19:01] <thomi> so I have confirmed this bug, but I'm not sure what the desired behavior should be
[19:01] <thomi> if, in the middle of us processing an assertion the dbus backend dissapears (probably because the application is no longer running), what should we do?
[19:01] <thomi> currently we raise ann unhandled dbus exceptiion
[19:02] <thomi> we could raise a RuntimeError, but then we'd probably want to do that everywhere, which is a significant amount of finger-work
[19:02] <thomi> I'm starting to think that this might be something to delay until 1.4
[19:02] <thomi> cgoldberg: any thoughts?
[19:02] <cgoldberg> 1 sec :)
[19:12] <cgoldberg> thomi, im not sure I follow.  sounds like raising a dbus exception is the right thing, no?
[19:13] <thomi> cgoldberg: well, yes, except it's not exactly obvious to the test author what went wrong
[19:13] <thomi> I think changing it in some places only is probably worse than not changing it at all
[19:13] <thomi> better to be consistent.. for 1.3 anyway
[19:14] <cgoldberg> sounds reasonable
[19:14] <cgoldberg> thomi, btw, I re-pushed my branch.. ditched the doctests and bad imports and just made them code samples
[19:15] <cgoldberg> pitti, i also made a change on that branch so you can pass a test arg to tox.  "$ tox -- autopilot.tests.unit"
[19:15] <thomi> cgoldberg: ok, reviewing now
[19:15] <cgoldberg> and "tox" alone to run them all
[19:16] <thomi> I still think we should just run the unit tests by default, but I'll defer to pitti's better judgment
[19:16] <thomi> approving now
[19:16] <thomi> approved
[19:16] <cgoldberg> ta
[19:30] <pitti> thomi: not necessarily better, we just seem to disagree on that; but it's not a dealbreaker either way
[19:30] <thomi> pitti: yeah, it's no biggie :)
[19:30] <pitti> cgoldberg: anyway, thanks for the adjustments, it's really nice now as you can do both (or just single tests)
[19:31] <cgoldberg> np
[19:41] <elopio> om26er: I'm back. Do you still need help with the set up?
[19:41] <om26er> elopio, I'll work on that tomorrow, I am stuck in other stuff today :/
[19:41] <om26er> well Monday ofcourse
[19:42] <elopio> om26er: ok.
[19:42] <om26er> Its been a looong week.