[04:58] <pitti> Good morning
[05:05] <jibel> good morning
[05:24] <jibel> pitti, could you have a look at bug 933199 ? it a missing mkdir when the sandbox is created, unless it has to be created manually of course.
[05:27] <pitti> jibel: looking
[05:36] <DanChapman> morning all
[05:52] <pitti> jibel: ok, finally got to this (sorry, some IRC diversions)
[05:52] <pitti> jibel: do you actually encounter this with current saucy?
[05:53] <jibel> pitti, yes, I do.
[05:56] <jibel> pitti, here is the trace on saucy http://paste.ubuntu.com/6174319/
[05:57] <pitti> jibel: merci
[06:06] <pitti> jibel: so the workaround is indeed to manually run mkdir -p on that path
[06:06]  * pitti commits fix to trunk
[06:45] <jibel> pitti, thanks
[08:08] <pitti> thomi: seems autopilot run doesn't support @unittest.skipUnless?
[08:08] <pitti> is there another way to conditionally skip a test?
[08:08] <thomi> pitti: dunno, it supports testtools.skip* decorators
[08:08] <thomi> skipIf, skipUnless
[08:09] <pitti> thomi: ah, thanks
[08:09] <pitti> (*slightly grumble*..)
[08:09] <thomi> heh
[08:11] <pitti> ok, that works
[08:13]  * thomi -> EOD
[09:05] <slickymaster> morning all
[10:02] <davmor2> Morning all
[10:04] <Noskcaj10> hey davmor2
[14:48] <elopio> good morrning.
[14:48] <DanChapman> morning elopio
[14:50] <davmor2> morning elopio I do use this channel :P
[14:51]  * balloons notes davmor2 looks familar
[14:52] <cgoldberg> morning folks.. morning davmor2
[14:53] <cgoldberg> elopio, do you think Autopilot feels slow launching and killing apps?  I've been deep in the code and I think I have a nice optimization I can implement to make it a bit faster
[14:54] <elopio> cgoldberg: I had a bug where it took 15 seconds between launching and beeing able to interact with the application.
[14:54] <elopio> but after that, it seems normal. If you make it faster, I'm sure I
[14:54] <elopio> 'll like it mroe.
[14:54] <elopio> *more.
[14:55] <cgoldberg> elopio, there is a 1 sec sleep inside launching, and another 1 sec sleep inside killing.  I think I can get rid of those and still have it work correctly
[14:55] <cgoldberg> but i need to write some tests for AutopilotTestCase first
[14:57] <elopio> cgoldberg: yes, please add the tests. With that at least we will know why we need the sleeps.
[14:57] <cgoldberg> elopio, btw..unrelated... this script is awesome... you should add it to your .bashrc:  http://iloveubuntu.net/beautify-your-terminal-screenfetch
[14:57] <cgoldberg> https://plus.google.com/114546378907380458640/posts/1wzh9o93oci
[14:59] <balloons> cgoldberg, thomi recently did some work in that area of long-launch times
[15:00] <balloons> pitti, can I request you to get this MP in this week? https://code.launchpad.net/~dpniel/autopilot-gtk/autopilotgtkemulators/+merge/187673
[15:00] <elopio> cgoldberg: :) I'll try it.
[15:00] <cgoldberg> balloons, i'll talk to him when he gets on.. thanks.  i'm gonna give my optimization a shot also.  we need tests around AutopilotTestCase anyways.. there aren't any
[15:01] <elopio> cgoldberg: hey, I got the SSD. I just forgot to order a cable... I'll install it in the afternoon.
[15:01] <pitti> balloons: sorry, was a victim of TODO overflow.. I'll try really hard
[15:01] <cgoldberg> elopio, you can probably use your existing sata cable that your old drive used
[15:01] <balloons> pitti, I know the feeling, but I'll be your reminder (at least I'll try) :-)
[15:02] <elopio> cgoldberg: I'd like to keep my old drive too. It's not completely broken.
[15:02] <cgoldberg> ah
[15:08] <balloons> so DanChapman have a pleasant weekend mate?
[15:09] <DanChapman> balloons, Yeah was nice and relaxed thanks. How about you?
[15:10] <balloons> DanChapman, same. Had a lovely spontaneous sunday afternoon drive yesterday which was very relaxing
[15:12] <DanChapman> balloons: sounds lovely. :-)
[15:14] <balloons> DanChapman, it was. It's interesting driving through a place and taking a slightly different turn on a whim. Sometimes you discover big new things that were always right there
[15:16] <elfy> hi balloons DanChapman
[15:17] <balloons> hi elfy!
[15:17] <smartboyhw> So many people around here!
[15:17] <elfy> 108
[15:17] <elfy> even ...
[15:18] <elfy> or 106
[15:18]  * DanChapman wishes he had a car again!
[15:18] <DanChapman> hey elfy o/
[15:18] <elfy> DanChapman: I've not had one for almost 2 years - not something I miss much
[15:23] <balloons> having one car is handy for trips.. But I like it purely for pleasure, not as require transport
[15:23] <balloons> *required
[15:23] <elfy> I have access to one if it's required
[16:56] <jfunk> ping ubuntu-qa - curios if there is a system level smoke test plan for the phone somewhere
[16:57] <davmor2> no idea.
[16:57] <elopio> jfunk: I'm writing the test cases for publishing, reviewing, installing and updating click apps.
[16:57] <davmor2> balloons: is this something you might know about? ^
[17:01] <balloons> jfunk, system level? what would you be after specifically?
[17:01] <balloons> elopio, ohh really? didn't realize you were doing any click stuff
[17:03] <elopio> balloons: yes, I'll be working with mmcc automating the tests for the unity app preview, the U1 integration on system settings and the click update manager.
[17:03] <jfunk> balloons, I mean a set of tests that briefly touches everything that a user touches
[17:03] <jfunk> on the phone
[17:04] <jfunk> a system wide tyre-kick
[17:04] <elopio> jfunk: that's a big set of tests :)
[17:05] <balloons> jfunk, ok, well there is nothing that can be considered definitive in that way. What you used to see on the tracker was probably the closest thing that has ever existed to such a suite
[17:06] <jfunk> tracker?
[17:06] <davmor2> jfunk: the test tracker for iso testing
[17:06] <balloons> qatracker, when the images were still managed in there
[17:06] <jfunk> right
[17:06] <balloons> as far as testing and etc go.. For the moment, they are being handled outside of that
[18:57] <thomi> good morning all
[19:10] <alesage> thomi good morning
[19:11] <thomi> morning alesage
[19:21] <elopio> fginther: some of the runs on that bug have all the tests failing.
[19:21] <elopio> I suspect that's because we couldn't open the application. So, I'll work on that test first. Make sure the app is visible before going on.
[19:22] <fginther> elopio, For each of those runs, I found a traceback that looked similar to a failed tab switch, but I didn't look beyond why that failed
[19:24] <elopio> thomi: is there a way to check if an application is on foreground?
[19:28] <elopio> fginther: yes, I've just checked that even if the app is on the background, it will say it's visible.
[19:28] <letozaf> balloons, hello
[19:29] <elopio> I'm not sure who's to blame about that. I suppose Qt, and that's going to be a pain.
[19:30] <balloons> letozaf, hello
[19:30] <balloons> letozaf, how's docviewer?
[19:31] <elopio> mzanetti: ping, you around?
[19:31] <letozaf> balloons, fine fixed that  unstable state
[19:31] <mzanetti> elopio: hi
[19:31] <letozaf> balloons, added two tests and integrated emulatro
[19:31] <letozaf> sorry emulator
[19:32] <elopio> mzanetti: hey. I've just found that we are checking if the main view of the application is visible before starting the tests. But it's always True even when it's behind another window, thus not visible.
[19:33] <elopio> mzanetti: do you know if there's a property or a way to check if it's actually being shown?
[19:33] <letozaf> balloons, yesterday I had a look at the stock ticker app, do you know two tests fail ?
[19:33] <mzanetti> elopio: yeah, QQuickView should have such a thing
[19:33] <balloons> letozaf, did you see my conversion in progress on stock ticker?
[19:33] <balloons> letozaf, https://code.launchpad.net/~nskaggs/stock-ticker-mobile-app/test-click-support/+merge/187950
[19:34] <letozaf> balloons, nope, gonne look now :p
[19:34] <letozaf> gonna not gonne
[19:34] <elopio> mzanetti: I'm looking at the properties of the QQuickView, but I can't see any of them changing when I bring the app forward.
[19:34] <balloons> letozaf, it doesn't work, lol, and I can't figure out why.. there's something funny with it
[19:35] <letozaf> balloons, :(
[19:35] <letozaf> balloons, well if you cannot find the problem I doubt I will be able :P
[19:36] <letozaf> balloons, but I can just take a look
[19:36] <balloons> letozaf, yes, go for it
[19:36] <letozaf> balloons, ok
[19:37] <mzanetti> elopio: hmm... no... there doesn't seem to be such a thing. actually how should the application know that?
[19:37] <mzanetti> elopio: its the window manager that has that information
[19:39] <elopio> mzanetti: I was hoping for the application be able to know if it was actually being rendered. But yes, sounds complex.
[19:39] <mzanetti> elopio: well, it is rendered
[19:39] <mzanetti> elopio: but it can't know it the window manager paints something on top
[19:39] <letozaf> balloons, :( I see docviewer fails too :'(
[19:40] <mzanetti> elopio: why is there something on top?
[19:40] <elopio> mzanetti: sometimes, because we don't have a desktop file so unity doesn't launch it properly.
[19:40] <elopio> other times, because we have the screen locked.
[19:40] <balloons> letozaf, you are missing a comma
[19:41] <elopio> in this case I'm debugging, I have no idea. I'm just trying to make sure no test continues if the application is not on top.
[19:41] <letozaf> balloons, thanks, let me check
[19:44] <letozaf> balloons, fixed, I really didn't see it
[19:44]  * letozaf needs to change glasses
[19:47] <letozaf> balloons, I see you put a comma at the end of the "Depends" last line : ubuntu-ui-toolkit-autopilot,       do we need a comma also on the last line ?
[19:48] <thomi> letozaf: it's good to have - means adding a new dependency only adds one diff line
[19:48] <thomi> but it's not required
[19:48] <letozaf> thomi, thanks :)
[19:48]  * balloons finds it annoying, lol
[19:49] <balloons> but ty thomi for applying some reasoning
[19:49] <balloons> so letozaf put the comma in.. for diff's sake :-)
[19:49] <letozaf> balloons, ok
[19:50] <letozaf> balloons, done
[19:55] <letozaf> balloons, OMG
[19:56] <elopio> thomi: can we get some help from mir or autopilot to tell if an app is actually being shown?
[19:56] <balloons> letozaf, ohh nice
[19:56] <balloons> letozaf, that's a weird archive issue it seems
[19:58] <letozaf> balloons, how do you fix that ?
[20:03] <balloons> letozaf, well it's odd, but it's not a problem with your merge i don;'t think. Just need to wait it out
[20:03] <letozaf> balloons, ok
[20:03] <balloons> the package will build out and be availible shortly
[20:36] <letozaf> balloons, meh! cannot find what the problem is with your conversion in pogress on stock ticker, everything looks fine but it fails to get main_view visible property
[20:37] <balloons> letozaf, yep, indeed it does
[20:37] <balloons> I suspect the qml is to blae
[20:38] <balloons> *blame
[20:42] <letozaf> balloons, going to bed it's getting late for me, sorry  could not help much :p
[20:42] <balloons> letozaf, no worries. There are other apps and things to do
[20:42] <balloons> which don't require you to pound your head at a problem
[20:42] <balloons> I like letting things sit for a bit and coming back after doing something successfully
[20:43] <balloons> I'll figure it out I'm sure
[20:43] <letozaf> balloons, ok
[20:43] <balloons> letozaf, ciao, sleep well
[20:43] <letozaf> balloons, ciao
[20:51] <cgoldberg> elopio, how do I mark an MP as a WiP?  so nobody will review it yet?
[20:51] <elopio> cgoldberg: did you already make the MP?
[20:51] <cgoldberg> elopio, yes.. just did
[20:52] <cgoldberg> i can delete it and make another?
[20:52] <elopio> ok, then on top it will say Status: Need review. Click there and change to Work in process.
[20:53] <cgoldberg> ah.. nice.  thanks
[20:53] <elopio> if you are just making the proposal, there's a checkbox with the misleading label: "Needs review". So, uncheck it.
[20:53] <cgoldberg> gotcha
[20:55] <cgoldberg> elopio, wanna look at my WiP?  I'm trying to make Autopilot stream results as tests are run.  my biggest pet peeve with AP is how you get no progress during a test run in non-verbose mode
[20:55] <elopio> cgoldberg: sure. To learn, mostly, because I missed the streaming branches on SST.
[20:55] <cgoldberg> my branch works.. even with verbose mode.. but i'm probably missing some cases, like using junitxml
[20:56] <cgoldberg> elopio, this doesn't use real streaming via subunit... it just adds a unittest.TextTestRunner
[20:56] <cgoldberg> https://code.launchpad.net/~coreygoldberg/autopilot/text-testrunner/+merge/188451
[20:56] <elopio> cgoldberg: oh, right.
[20:56] <elopio> it's small.
[20:57] <cgoldberg> yup
[20:57] <elopio> I suppose we need a way to select the runner.
[20:58] <cgoldberg> elopio, everything *should* work same as before.. plus output as the tests run
[20:58] <elopio> cgoldberg: yes, I think it's an good improvement.
[20:58] <cgoldberg> it's great if it works correctly
[20:59] <elopio> I was wondering why autopilot remained silent while running. Now I see.
[20:59] <cgoldberg> yea.. it waited for test.run(result) to return
[21:00] <elopio> cgoldberg: one thing that I always find a pain in the ass is the verbosity. You have the verbosity of the runner, and the log level of SST/Autopilot
[21:00] <elopio> and as on SST, autopilot uses -v to set the log level.
[21:00] <cgoldberg> right.. they are sorta 2 different things though
[21:01] <cgoldberg> verbosity of the runner just tells it to print dots... or testcase names
[21:08] <elopio> cgoldberg: yes. I think a runner should receive to parameters: verbosity, and log level.
[21:08] <elopio> veebers: I found an easy way to reproduce the None _Backend error.
[21:11] <elopio> https://code.launchpad.net/~elopio/ubuntu-ui-toolkit/fix1233364-assert_visible/
[21:12] <elopio> with that branch: autopilot run ubuntuuitoolkit.tests.test_base
[21:18] <veebers> elopio: awesome thanks, I'm just looking into that now
[21:42] <elopio> fginther: one good news is that the failure that looks like String(u'Tab3') != 'Tab2' is because of a change in the toolkit behavior.
[21:43] <fginther> elopio, yeah! one problem solved
[21:44] <elopio> fginther: almost. I'm going to try accessing the buttons by their index property, not just by their index on the list.
[21:51] <veebers> elopio: for me to run that branch do I need to do anything (i.e. build/install anything)? Or can I just branch and run autopilot?
[21:52] <elopio> veebers: qmake && make
[21:52] <veebers> elopio: awesome, cheers
[21:52] <elopio> veebers: hum, and maybe apt-get install build-dep ubuntu-ui-toolkit-autopilot
[21:53] <veebers> elopio: would that be the same for the gallery-app would you know?
[21:53] <elopio> veebers: I have never ran the gallery-app.
[21:53] <veebers> elopio: ack
[21:53] <elopio> generally, the apps don't need a make.
[21:54] <veebers> elopio: right ok. It seems running ap tests for gallery-app needs something extra (or I'm doing something dumb)
[21:54] <elopio> veebers: what's the error?
[21:55] <veebers> elopio: ugh lost it now (building u-u-t). but using your branch will work for what I'm doing
[22:00] <jfunk> EOD all, have a good one!
[22:14] <elopio> veebers: will this give me always the latest application I launched?
[22:14] <elopio> self.process_manager.get_running_applications()[0]
[22:16] <veebers> elopio: hmm, good question. let me refresh my memory
[22:16] <veebers> elopio: also note, this will only currently work on the deskop
[22:16] <veebers> desktop
[22:16] <elopio> really?
[22:16] <veebers> there isn't an interface to the process management on devices yet
[22:16] <elopio> that's sad.
[22:16] <veebers> yeah it's in the works
[22:16] <veebers> agreed
[22:17] <elopio> so, we basically have no way to tell if the application launched is visible and focused.
[22:17] <elopio> fginther ^
[22:17]  * fginther head -> desk
[22:18] <elopio> veebers: who
[22:18] <elopio> veebers: who's doing that work? and how do we increase its priority? :)
[22:19] <veebers> elopio: there has been some discussion recently (https://bugs.launchpad.net/unity-mir/+bug/1232054) there isn't any one person on this right now
[22:21] <elopio> critical, in progress sounds good.
[22:22] <veebers> elopio: Not sure if it helps you right now, if you're testcase inherits from unity8testcase then you can get the current focused application id
[22:22] <veebers> the application lifecycle tests in unity8 do this
[22:22] <knome> veebers, "your" :)
[22:22] <elopio> veebers: no, that won't help.
[22:22] <veebers> knome: d'oh, thanks
[22:23] <elopio> if unity provides an API to get the focused application, that would help.
[22:23] <elopio> but that would make the tests work only on unity.
[22:25] <veebers> elopio: correct. The autopilot process management stuff will be the best bet, unfortunately I don't have an eta for it right now
[22:30] <elopio> ok, I'm blocked until the SDK team wakes up, so I'm going for lunch now.
[22:30] <elopio> bbl.
[22:32] <cgoldberg> EOD.. later all o/