[00:57] <phillw> balloons: you gone awol again?
[04:15] <pitti> Good morning
[04:15] <pitti> qengho: oh, how not? I had assumed it would mostly compile for GTK2 as well, perhaps it needs some #ifdefery?
[04:15] <pitti> qengho: the gtk2 plugin should go into a new binary package, though
[06:54] <jibel> good morning
[08:41] <DanChapman> Good morning all :-)
[08:58] <slickymaster> good morning all
[15:38] <slickymaster> balloons: hi. is everything ok with http://iso.qa.ubuntu.com/? I'm getting "The resource you tried to access doesn't exist. This can happen because of an invalid link or because of a bug."
[15:38] <balloons> slickymaster, ohh.. heh, I would say not
[15:39] <slickymaster> balloons: I was doing the ISO tests for the Alpha 2 and a moment ago, after submitting a result a got that message
[15:39] <balloons> stgraber, ^^ it appears the qa.u.c domain is down
[15:40] <stgraber> balloons: applying security updates
[15:40] <stgraber> should be back in a couple of minutes
[15:40] <balloons> stgraber, :-)
[15:40] <slickymaster> stgraber: balloons thanks, the both of you
[16:40] <balloons> elopio, hmm, having trouble finding ubuntu-ui-toolkit to install.. weird
[16:40] <balloons> ahh it's been renamed :-)
[16:41] <balloons> DanChapman_, dkessel hello
[16:41] <elopio>  ubuntu-ui-toolkit-autopilot ?
[16:41] <dkessel> balloons, good evening
[16:42] <elopio> balloons: renamed to what?
[16:42] <balloons> elopio, yea.. it wasn't finding it at first..
[16:42] <balloons> i was trying to install a meta package like ubuntu-ui-toolkit and that wasn't working
[16:44] <DanChapman_> balloons, howdy. How u doing?
[16:45] <elopio> balloons: do you know about pushing an app from the qtcreator to the phone?
[16:45] <elopio> I press ctrl+f2, but get ssh: connect to host 127.0.0.1 port 2222: Connection refused
[16:45] <dkessel> oooh nice new ubuntu edge price options =)
[16:46] <balloons> elopio, yes from inside qtcreator right?
[16:47] <elopio> balloons: yes.
[16:47] <balloons> dkessel, yes, new options, but act fast if you want a lower tier :-)
[16:48] <balloons> elopio, that should work, I haven't tried it in awhile.. hmm.. does it show your devices under devices?
[16:49] <elopio> ahh, there's a big button there saying enable developer mode
[16:49] <elopio> maybe that's what I was missing.
[16:50] <balloons> elopio, so I'm looking at the final results for the emulator.. and I saw the pep8 stuff and renames.. we ready for primetime use?
[16:50] <elopio> balloons: not yet. The rename hasn't landed.
[16:50] <balloons> elopio, yes, but once the rename has landed
[16:51] <elopio> balloons: yes. And you can start using it now, just rename to ubuntuuitoolkit tomorrow.
[16:52] <balloons> elopio, well I'm going to announce some fanfare, so I'll prep everything and probably just announce tomorrow once it's complete
[16:52] <balloons> I'll probably convert an app today to demo it
[16:54] <balloons> DanChapman_, doing well.. As you can see elopio's hard work on making a proper emulator for qt has landed ;-)
[16:54] <elopio> balloons: sounds good. Let me know if you find any bugs.
[16:54] <balloons> elopio, I'm hoping it'll fix some of the bugs I've introduced :-)
[16:54] <balloons> hehe
[16:55] <elopio> balloons: well, at least, it's now easy to make tests for the bugs we find.
[16:56] <balloons> this is true.. I introduced a weird bug, but it might be on the autopilot side.. it's just hard to know.. but now, we can easily tell
[16:58] <elopio> balloons: and I've just noticed I am assuming there will be just two tabs visible. But if the label of the tab is small, more than two can appear on the header.
[16:59] <elopio> that will bite soon.
[16:59] <balloons> yes, there are apps with 3. it's not uncommon
[16:59] <balloons> why is that?
[17:01] <elopio> because I'm naive :) I assumed you would be able to switch just from the current tab to the next, without skips.
[17:02] <balloons> elopio, ahh.. I believe my tab switching logic just scrolls through things.. and you can stop at a tab index or tab label
[17:02] <balloons> so you can in theory create a spin of death where you go through things endlessly because there is no match haha
[17:02] <elopio> yes, I copied that funny feature :)
[17:03] <balloons> we could in theory stop once it's gone round once and raise an error
[17:03] <elopio> balloons: but well, make sure to mention on your post that it's a first version in heavy development :)
[17:03] <balloons> elopio, ofc ofc.. but bugs and such can be reported, and it can be updated sanely, etc
[17:04] <elopio> yes, and I think we also can factor out some other common things.
[17:04] <elopio> like a base test case class, things that are the same on all the apps.
[17:06] <elopio> and the final feature that ties everything together is what zoltan and jppiiroi1en are doing on the qt creator. It now has a template for the autopilot tests :D
[17:16] <DanChapman_> balloons, thats cool will check it out. I have basically re-written the ubiquity tests the last few days :-) it should sort the fails on jenkins. just finishing off custom partition then will move on to dual-boot
[17:21] <balloons> elopio, the autopilot template is in? wahoo?
[17:22] <balloons> DanChapman, I've been watching the results.. a bit mixed as you say, so I hope the changes solve that
[17:27] <DanChapman> balloons, it helps now i have the test runner jibel created. makes it easier to find the bugs. If your not too busy would you be able to give the tests a once over for me?? Could do with some fresh eyes on it :-)
[17:28] <balloons> DanChapman, I have a moment now sure :-)
[17:28] <DanChapman> balloons, cheers. I havn't pushed custom part up yet though https://code.launchpad.net/~dpniel/ubiquity/autopilot
[17:29] <balloons> big branch :-)
[17:32] <balloons> still going . . .
[17:32] <DanChapman> lol :-)
[17:33] <balloons> the numbers keep going up
[17:33] <DanChapman> yeah it ends some where near 120000 i think
[17:33] <balloons> I should have updated the branch I had already pulled.. lol.. a couple more mins I think I 'll have it
[17:34] <DanChapman> Ive done that a few times myself :-)
[17:36] <balloons> and done
[17:37] <DanChapman> lol
[17:37] <balloons> k, so what specifically should I look at?
[17:38] <balloons> ohh.. you should note in your readme kubuntu is special -- it has it's own installer and your stuff won't work for that
[17:38] <DanChapman> DOes it say kubuntu in it?
[17:40] <DanChapman> right the biggest problem i keep coming across is grub install fail or the installer crashes. which usually occurs during the progress bar. Can you look at the track_install_progress_bar func. Do you think thats a reasonable way of handling it?
[17:40] <balloons> it doesn't.. it just says all other flavors.. which is true, except for kubuntu ;-_)
[17:40] <DanChapman> lol i will update it.
[17:40] <balloons> so I'm curious that the ubiquity_did_install_complete test and this assert doesn't timeout normally: self.assertThat(self.complete_dialog.visible, Eventually(Equals(1)))
[17:41] <balloons> k, looking at the progress func
[17:42] <DanChapman> balloons are you wondering about the sleep?
[17:43] <balloons> ok so your throwing a message, but then have an assert about the dialog.. I'm confused at first glance what your trying to do
[17:43] <knome> balloons, you're :P
[17:43] <balloons> brilliant.. knome is going to fix me yet
[17:44] <balloons> why just today knome I noticed myself and corrected it!
[17:44] <knome> nice!
[17:44] <knome> the education works ;)
[17:44] <DanChapman> Thats more for me at the moment as when using the test runner locally you get ALL the output from the env and not just autopilot output so i stuck the message so i could spot that the func had picked up the dialog. I will remove it in the end :-)
[17:44] <balloons> DanChapman, ahh I see you sit in ubiquity_progress_bar_test before hitting ubiquity_did_install_complete
[17:45] <balloons> and it has a 300 second timeout (might not even be long enough, heh) but yea, that was my expectation of a long timeout
[17:46] <balloons> ok, so I will say why watch the progress bar? Why not just wait for the dialog to appear? Are we concerned about it hanging and we don't know it or ?
[17:47] <balloons> I would just wait for the install complete dialog to appear. And if we want to "watch" in the interim, grab the progress and assert that the progress reported changes withing X amount of time
[17:47] <balloons> can we also reliably detect if something goes awry -- aka a dialog window other than the install complete appears/
[17:50] <balloons> DanChapman, ^^
[17:50] <DanChapman> I did think of just looping waiting on the confirm dialog. But following the progress kinda shows that its updating ok.
[17:51] <DanChapman> The 300 timeout is a bit extreme as it just waits for the progress to go back to 0.0 for the install part.
[17:51] <balloons> oh it's just the copying files piece I see.. not the install
[17:53] <DanChapman> I've had no probs with the progress bar and tracking it. Its trying to catch an error dialog while stuck in the loop. As the loop never exits if it doesn't catch it.
[17:53] <balloons> DanChapman, I'm missing where self.install_progress.fraction is coming from
[17:53] <balloons> yea you have your         while progress < complete: loop that won't end right?
[17:55] <DanChapman> install_progress selects the progress bar in ubiquity_progress_bar_test
[17:56] <balloons> ahh.. there it is, ty :-)
[17:57] <balloons> ok far enough.. so we loop while waiting for complete. Each iteration we update the progress, and then check for errors.
[17:58] <balloons> so let's dig into those error checks.. you have checks for visible windows of failures and then breaks to leave the loop
[17:58] <balloons> and your finding that the loop isn't ending on failures because of the if statement check for the error is never becoming true, or it's not breaking properly?
[17:59] <balloons> if the "visible" property isn't working out so well, can we just check from existence of the object, or do they exist from the beginning?
[18:01] <DanChapman> its catching the error dialogs 'ok'. Just dnt know if there is a better way to do it. All the objects are there from the start apart from the grub install failed dialog which is created once the error occurs. hence the it being in a try
[18:05] <DanChapman> i did think to try just getting the visible window count like in the FF test and if window count increased then it would fail but i couldn't figure out how to do that. and it would have a very meaningful reason for failing as we wouldn't know what it failed on
[18:06] <DanChapman> *wouldn't
[18:09] <DanChapman> from an autopilot point of view that is. I know the install log would give details, but it would be good to see that the correct dialog appears for the correct error i suppose.
[18:09] <balloons> Heh, testing the error windows too :-)
[18:10] <balloons> yea, so since the object exists, visible works well enough. I just don't like to rely on it, but perhaps that's not well placed
[18:30] <DanChapman> balloons, just run the default test a few times and got a grub install failed and it caught it ok. So do you think leave it as it is and see how it goes. In theory it shouldn't happen often if at all anyway :-)
[18:31] <balloons> DanChapman, I think the idea is sane enough, and I like monitoring it.. I would add a timeout check though I think if nothing happens for X amount of time, aka the progress bar doesn't move
[18:32] <balloons> we don't want to loop forever without us knowing about it.. and yea, that should work
[18:35] <DanChapman> balloons, i like it. Will add a timeout check
[18:38] <DanChapman> Will sort that tomorrow. I'm calling it a day. Catch you all tomorrow
[18:40] <balloons> DanChapman, catch you on the flipside
[19:18] <balloons> good evening Letozaf_
[19:18] <Letozaf_> balloons, Hi
[19:19] <balloons> did you see the rss reader stuff landed -- it's a bit different than before :-_
[19:20] <Letozaf_> balloons, no didn't see it, I must take a look :) read you did something
[19:24] <Letozaf_> balloons, by the way did you see the sudoku tests ?
[19:25] <balloons> Letozaf_, what's up with them?
[19:25] <Letozaf_> balloons, nothing :) I hope
[19:25] <balloons> lol
[19:26] <Letozaf_> balloons, where can I see the rss reader stuff ? I was looking in my branch and the rssreader one...
[19:27] <Letozaf_> balloons, what happened to it ?
[19:36] <balloons> Letozaf_, what do you mean what happened?
[19:36] <Letozaf_> balloons, you said it's different ...
[19:37] <balloons> Letozaf_, ohh yes, the main trunk has new code in it
[19:37] <balloons> including the theme :-)
[19:38] <Letozaf_> balloons, oh I just did a bzr branch, but there is nothing in there
[19:38] <Letozaf_> balloons, :(
[19:38] <balloons> bzr branch lp:ubuntu-rss-reader?
[19:39] <Letozaf_> balloons, maybe I did something wrong:  bzr branch lp:ubuntu-rssreader-app
[19:39] <Letozaf_> balloons, yep
[19:39] <Letozaf_> balloons, oh wait I did  bzr branch lp:ubuntu-rssreader-app
[19:39] <balloons> yea, 22 revisions
[19:39] <balloons> you had it right.. I mispelled it ;-)
[19:40] <Letozaf_> balloons, but the test is only 27 lines long in it
[19:40] <balloons> Letozaf_, anyways, once you branch you can see the add and edit feed stuff are a little different
[19:41] <Letozaf_> balloons, ok I will re-branch it
[19:42] <Letozaf_> balloons, I get 20 revisions  ?
[19:42] <Letozaf_> balloons,  bzr branch lp:ubuntu-rssreader-app
[19:42] <Letozaf_> balloons, that's weired
[19:42] <balloons> Letozaf_, should be 22 revs
[19:42] <balloons> hmm
[19:42] <Letozaf_> balloons, did it twice, cancelled the directory and branched from scrap
[19:43] <balloons> Letozaf_, lol, you've got it then, sorry
[19:43] <balloons> i have post branch commits in mine
[19:43] <balloons> whoops!
[19:43] <Letozaf_> balloons, :D
[19:43] <balloons> I checked http://bazaar.launchpad.net/~ubuntu-rssreader-dev/ubuntu-rssreader-app/trunk/revision/20
[19:44] <Letozaf_> balloons, I'm curios to see what you guys did to it :P
[19:44] <balloons> looks much nicer
[19:48] <Letozaf_> balloons, I was looking for the next app to write test for ... for instance the music-app, but once you create a playlist, how do you put music in it ?
[19:48] <Letozaf_> balloons, :?
[19:48] <balloons> Letozaf_, vthompson is one of the music app authors, and I believe dkessel wrote one of the tests for it?
[19:49] <balloons> anyways, there are some tests in there, so it shouldn't be too hard to hack on it
[19:49] <balloons> on your question however, I'm not sure off the top of my head
[19:49] <balloons> we can always ask the app authors :-)
[19:49] <Letozaf_> balloons, I will take a look thanks
[19:50] <Letozaf_> balloons, oh yes sure
[19:51] <Letozaf_> balloons, but do you think I can work on it or is dkessel doing it ?
[19:51] <Letozaf_> balloons, you know that as soon as I pick something someone else has done it already :P
[19:55] <dkessel> Letozaf_, i am not working on any more music app tests at the moment
[19:57] <balloons> Letozaf_, indeed dkessel wrote just the initial test.. no one will steal your thunder on this one.. I would contact victor though. .would you like his email?
[19:58] <Letozaf_> dkessel, thanks for the info
[19:58] <dkessel> good night
[19:58] <Letozaf_> balloons, ok in case I need to ask him somethin
[19:58] <Letozaf_> dkessel, good night
[19:58] <balloons> night dkessel !
[20:14] <thomi> morning
[20:17] <Noskcaj> balloons, Do you know if anyone is going to be able to look after the testdrive hackfest between 1600 and 2000
[20:22] <balloons> Noskcaj, no takers on the thread right?
[20:22] <balloons> I'm still concerned about having it run for more than a few hours
[20:22] <Noskcaj> ok. Maybe i but it back to only 6 hours?
[20:25] <balloons> I would rather see an amazing couple hours as opposed to having 6 hours with 4 hours of downtime.. But yea, it's up to you. I wouldn't run it for longer than you can be around. Getting commitment from others to show up is excellent too, but make sure your around. The idea is to kickstart new folks on development as well as close bugs right?
[20:25] <balloons> BTW, you should send a message to ubuntu-devel as well once everything is in place
[20:25] <balloons> I saw your target work, so plan on running it for as long as it would take to finish that off, with some buffer
[20:26] <balloons> assuming of course you think you can get through the whole list :-)
[20:26] <balloons> remember you can always have another event ;-)
[20:26] <balloons> Noskcaj, I'm not remembering but how long is it going to run for atm?
[20:28] <Noskcaj> balloons, 11 hours, so i'll cut that back so howard and i can run it ourselves
[20:28] <balloons> Noskcaj, yea, that sounds like the way to go
[20:31] <balloons> good stuff mate
[20:32] <balloons> elopio, so I'm having trouble using your emulator.. perhaps you can shed some light on my python newbie blunders
[20:32] <elopio> balloons: of course. Tell me what you are doing.
[20:34] <balloons> elopio, well I'm having trouble creating a new instance of an emulator class.. For instance, toolbar
[20:35] <balloons> ie, I want to do something like  emulators.Toolbar.click_button( "newgamebutton"). I've imported I hope sanely; from UbuntuUiToolkit import emulators
[20:37] <elopio> balloons: first, you need to launch the application with the emulator.
[20:38]  * balloons facepalms
[20:38] <elopio> with the base emulator. Let me search for an example.
[20:38] <balloons> elopio, I get it I think
[20:39] <elopio> self.app = self.launch_test_application(
[20:39] <elopio>                 "/usr/lib/" + arch + "/qt5/bin/qmlscene",
[20:39] <elopio>                 "-I", get_module_include_path(),
[20:39] <elopio>                 qml_path,
[20:39] <elopio>                 emulator_base=emulators.UbuntuUIToolkitEmulatorBase)
[20:40] <balloons> elopio, yes, so more or less the __init__.py template for core apps needs to be updated to reflect this as well
[20:40] <balloons> as atm, it's handling all the launch code
[20:41] <balloons> let me see what I can do ;-)
[20:41] <elopio> balloons: yes. I think it would be better to have launch helpers on ubuntu-ui-toolkit.
[20:41] <elopio> so we have just one place to update.
[20:42] <balloons> hmmm hmm
[20:42] <elopio> also that part of get_input_device, and get_module_include_path. I see them everywhere.
[20:42] <balloons> ohh yea, it's horride
[20:43] <balloons> ok, so perhaps you can just help directly with this.. so I'm picking on dropping letters to convert over.. it doesn't have any tests, just the old layout. I was going to convert and add a test or two as the example
[20:44] <elopio> balloons: ok, and once you have the application launched with the emulator loaded, it's like:
[20:44] <elopio> self.app.select_single(emulators.MainView)
[20:45] <balloons> for the main view I take it? ;-) and then select and have fun from there?
[20:46] <elopio> balloons: yes. with the main view you can make open_toolbar, for example.
[20:46] <elopio> balloons: I'll propose a base test case, that can be inherited by all the apps.