[03:51] <smartboyhw> Noskcaj, have you asked kirkland or roaksoax about putting me in the team?
[07:01] <dkessel> good morning
[07:03] <ulitkovod> a day
[07:06] <DanChapman> Good morning all
[07:10] <jibel> good morning
[08:21] <Noskcaj> smartboyhw, no, sorry. They've not replied to me, and once again, you need to do this.
[08:55] <Noskcaj> Can someone try and confirm bug 1210040 ? It's a big one
[09:02] <dkessel> Noskcaj, any hint on how to reproduce it?
[09:02] <Noskcaj> dkessel, no, sorry. The guy didn't specify
[09:04] <dkessel> Noskcaj, apport sometimes consuming lots of memory is no big news ;) Maybe we should hint to the original reporter to delete stuff in /var/crash...?
[09:05] <Noskcaj> dkessel, can you please do that?
[09:05] <dkessel> sure
[09:07] <dkessel> Noskcaj, done. lets see what the response is...
[09:08] <Noskcaj> also, i just reported a bug that went straight to heat 158
[09:08] <Noskcaj> bug 1210053
[09:38] <xnox> balloons: jibel: DanChapman: updated lp:ubiquity with a working way to get application proxy in autopilot.
[09:40] <DanChapman> xnox, awesome! will give it a try now :-)
[09:42] <xnox> DanChapman: did you have updated tests somewhere with more refactoring, which were not merged yet?
[09:43] <DanChapman> xnox, yes but i need to run them again before MP as ap broke when i was finishing them up. If all is well I will MP today
[09:44] <xnox> DanChapman: i see, well see the fix in lp:ubiquity, the tests do run for me now on saucy =)
[09:44] <DanChapman> xnox, brilliant cheers. Just branching now
[11:52] <elopio> balloons: for when you get up, I did the calculator: https://code.launchpad.net/~elopio/ubuntu-calculator-app/emulators/+merge/179166
[12:35] <elfy> balloons: just so you know, the blank in xfce has been removed now
[13:29] <DanChapman> jibel hey, are you able to manually start the ubiquity tests on jenkins? Now the tests are running would be good to see how they do in the lab as i keep getting grub install error running locally
[13:32] <jibel> DanChapman, done
[13:33] <DanChapman> jibel, wow that was quick :-D thanks mate
[14:12] <DanChapman> jibel, hey i'm a bit confused. for the two failing tests in the gome-session log it says it branches my branch lp:~dpniel/ubiquity/autopilot but the autopilot error its displaying in the output xml file does not match up with whats in my branch.
[14:14] <DanChapman> line 28, in launch_application
[14:14] <DanChapman>     return get_autopilot_proxy_object_for_process(my_process, None). THis is no longer present in my branch or lp:ubiquity
[14:19] <jibel> DanChapman, hm, I'll have a look, there is also a strange "no space left" error
[15:13] <balloons> elopio, so do we not have any status from the object to know when we can press delete without sleep?
[15:23] <elopio> balloons: I couldn't find it.
[15:26] <balloons> elopio, can we drag that into test_simple_page.py and poll on waiting to grab the button then?
[15:26] <balloons> I would drag confirm_delete and put an assert eventually on it, polling for the button
[15:28] <balloons> elopio, does that make sense?
[15:28] <elopio> balloons: the thing is that the button is present and visible. And we can click it. Just that if we click it without the delete, it does nothing. So I'm not sure what to poll either.
[15:29] <elopio> I was thinking on asking the devs. And if they have a good method for that, implement it on _wait_for_screen_to_finish_animation
[15:29] <elopio> if they don't, file a bug.
[15:30] <balloons> elopio, wild.. so I have a calculation saved right now.. the button is present without me swiping to display it?
[15:30] <elopio> from the original tests I could just find the moving property, but it's not enough.
[15:32] <elopio> balloons: yes, the button is always present. It starts with visible = False.
[15:32] <elopio> but even if I wait for visible, there's a moment when the button is visible but not clickable.
[15:34] <balloons> elopio, sure.. but waiting for visible (and then having a small sleep if needed) is better than not :-)
[15:34] <elopio> I'm going to try that one more time.
[15:34] <balloons> to the extent possible, try and see if you can key anything off that button
[15:34] <balloons> k, I'll leave you to it :-P
[15:40] <elopio> balloons: I pushed it with the wait for and without the sleep.
[15:41] <balloons> elopio, and it works? :-)
[15:41] <elopio> all tests are passing here that way. I might have done it wrong the first time, but I would appreaciate you to run the tests to confirm.
[15:41] <balloons> ahh ok.. will do
[15:43] <smartboyhw> balloons, hey, gift each Ubuntu QA Team member an Ubuntu Edge:P
[15:43] <balloons> smartboyhw, whoa.. should I just buy a couple business packs?
[15:44] <balloons> elopio, lol, that broke like every test for me. the gestures are failing niw
[15:44] <smartboyhw> balloons, yes
[15:45] <balloons> elopio, looking at the changes, I'm confused
[15:45] <balloons> let me back out and try again
[15:45] <elopio> balloons: weird. might be the coordinates.
[15:45] <balloons> smartboyhw, it's actually impossible for me to do that.. turns out, I'm not loaded
[15:46] <smartboyhw> balloons, :P LOL
[15:46] <elopio> I've run them here like 10 times with no failures since I pushed the MP :/
[15:47] <balloons> elopio, wow.. I'm confused. if they work for you however, I'm ok with it
[15:47] <balloons> you changed one line to a wait_for and that broke all the tests? something funny must be going on with my machine
[15:48] <elopio> balloons: well, it sounds that the wait for is not enough.
[15:48] <balloons> elopio, lol.. the tests aren't hanging on the wait_for.. literally nothing is working
[15:49] <balloons> I'm re-merging back to rev 140
[15:50] <balloons> elopio, also completely broken.. gotta be something on my machine
[15:50] <balloons> I just ran that code and it worked
[15:53] <elopio> balloons: ok, if it's just because of the ghosts in your computer, it might be ok to approve the branch :)
[15:54] <balloons> elopio, I would call it something nefarious..
[15:55] <balloons> I approved it
[15:56] <elopio> balloons: thanks.
[17:07] <elopio> fginther: can you please enable the static checks on the calculator app?
[17:19] <fginther> elopio, I'll add it to my todo list
[17:19] <elopio> fginther: thanks.
[18:58] <fginther> elopio, the job has been update
[18:58] <fginther> d
[18:59] <elopio> fginther: thank you!
[20:33] <balloons> Letozaf_, evening to you. I wanted to let you know that the calendar lets you add events again (finally!)
[20:33] <balloons> on the rss stuff I haven't had a chance to speak to the devs yet sadly
[20:35] <Letozaf_> balloons, hello
[20:35] <Letozaf_> balloons, for the rss stuff no problem! there are so many changes that I have to work on the test
[20:35] <Letozaf_> balloons, to fix things, so I'm not in a hurry
[20:36] <Letozaf_> balloons, for the calendar, good!
[20:36] <Letozaf_> balloons, do I have to check the test works, do not remember quite well :p
[20:36] <balloons> Letozaf_, I was thinking the same thing.. I think it might be pretty close to ready to go as-is..
[20:37] <Letozaf_> balloons, anyway mabye I will take a look at it and see if it's ok
[20:45] <Letozaf_> balloons, nice the calendar app, look real good as it is now
[20:48] <Letozaf_> balloons, weired did you try to run the calendar app autopilot test ?
[20:49] <balloons> Letozaf_, no, I'm messing with terminal at the moment ;-)
[20:49] <Letozaf_> balloons, it fails :( ... anyway I will try to see If I understand what the problem is
[20:50] <balloons> Letozaf_, ahh.. well, it's possible to do. .make sure your running the latest trunk and then merge your branch into it ;)
[20:50] <Letozaf_> balloons, do you know what the dateutil.relativedelta module is _
[20:50] <balloons> I imagine the piece you'll have to fix is where the dates are selected
[20:50] <balloons> that changed
[20:50] <Letozaf_> balloons, I just branched it in a new directory
[20:58] <Letozaf_> balloons, I just branched the calendar app in a new directory and it looks like there is everything in the tests, so is there still the need to merge my branch into it, I mean there is nothing different between the two a part a @unittest.skip
[20:59] <balloons> ohh.. did your branch get merged?
[20:59] <balloons> lol, I can't remember
[21:01] <Letozaf_> balloons, lol :p
[21:02] <balloons> phablet
[21:09] <Letozaf_> balloons, the tests work fine after installing python-dateutil
[21:09] <balloons> well good stuff then
[21:12] <Letozaf_> balloons, well I meant the other tests not the add event one that has a unittest.skip, now, I will check that just now
[21:12] <balloons> ahh
[21:14] <Letozaf_> balloons, yep the add event need fixing :p
[21:39] <balloons> elopio, btw, your filemanager testcase is handy.. I'm hitting all of our old bug friends again :-)
[21:47] <balloons> elopio, does the popover require using a string to select an action? I suppose you didn't take it further than that eh?
[21:54] <balloons> ohh, https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1205144
[21:55] <balloons> the qml compiles with objectNames on the actions tho.. let me try :-)
[22:47] <balloons> thomi, what can model tell me from autopilot.platform? can I know if a device is a tablet, phone or desktop?
[22:52] <balloons> fail thomi my apologies; http://unity.ubuntu.com/autopilot/api/platform.html?highlight=model#autopilot.platform.model
[22:53] <thomi> balloons: yes, it can :)
[22:53] <balloons> thomi, I guess I was hoping to do a bit more tho.. I wanted to generically test a tablet layout for any device that would support it.
[22:54] <balloons> i can code in nexus 7 and nexus 10, and that's well enough
[22:54] <thomi> balloons: file a feature request against autopilot and I'll see what I can do
[22:55] <balloons> thomi, yes I guess the question is ultimately can we know in our tests just how big the device is.. perhaps this is something to just read from a qml property
[22:58] <thomi> balloons: you want physical dimensions, rather than screen resolution?
[23:00] <balloons> thomi, I'm trying to test an app that has different layouts for phone vs tablet. Not an uncommon thing. So what's the best way to know which mode I'm in and check the layout accordingly?
[23:00] <thomi> balloons: how does the app know?
[23:01] <balloons> it's a generic question, and forgive me if I'm talking in circles :-)
[23:01] <balloons> well thomi, that's my question to.. I feel like the answer is in qml, and not in autopilot
[23:01] <thomi> sure, but we might put it in both, just to make it easy for people
[23:03] <balloons> hehe, ok this is worth discussing with the rest of the qa folks
[23:03] <balloons> I'll file a generic bug and try and describe things and see what feedback we get. I'll probably file it tomorrow though.. :-)