[02:01] <blankley> So I just tried my very first testdrive of a nightly saucy ISO, using testdrive and Virtualbox, and I'm getting a PAE kernel error on boot
[02:03] <blankley> My host device is a Toshiba laptop from 2007, with an Intel Core 2 Duo T5250
[02:05] <blankley> Any workarounds to be able to test ISOs using this laptop?
[02:15] <blankley> If someone is curious, I found an existing bugreport for my problem: #940755
[02:57] <blankley> Alright, I've found a solution to that bug in the testdrive source code, but I don't know how to create submit a patch
[07:15] <abc> hi
[07:26] <jibel> Good morning
[08:11] <DanChapman> Good Morning all
[08:14] <Noskcaj> evening DanChapman
[08:15] <Noskcaj> Are you able to move your branch from /+junk to /testdrive yet? It would make watching it a lot easier
[08:15] <DanChapman> Hey Nosckaj, its already in lp:testdrive mate
[08:15] <DanChapman> well i think it is..... just checking
[08:16] <DanChapman> yeah its there
[08:25] <Noskcaj> DanChapman, ok, i'll take a look later.
[09:25] <slickymaster> morning all
[09:25] <Noskcaj> hey slickymaster
[09:26] <slickymaster> Noskcaj: hi, feelling good?
[09:26] <DanChapman> morning slickymaster
[09:26] <slickymaster> DanChapman: DanChapman ;)
[11:18] <DanChapman> xnox, ping
[12:37] <pitti> Good morning
[12:37] <DanChapman> morning pitti
[12:37] <pitti> hey DanChapman
[12:38] <DanChapman> pitti, if you get a chance at all today could you run your eyes over this for me https://code.launchpad.net/~dpniel/autopilot-gtk/autopilotgtkemulators
[12:39] <pitti> DanChapman: sorry, I've been on conferences last and this week, and today is packed (I'm speaking, too)
[12:39] <pitti> DanChapman: I'm afraid that will have to wait at least until Friday (depending on the schedule) or next wek
[12:39] <jibel> Good morning pitti and DanChapman
[12:40] <DanChapman> pitti, ok mate thats not a problem. :-) Enjoy your day
[12:40] <pitti> bonjour jibel
[12:40] <pitti> DanChapman: thanks
[12:40] <DanChapman> hey jibel
[12:43] <thomi> good morning all
[12:43] <DanChapman> morning thomi
[12:43] <JackYu> good night, thomi:)
[12:43] <JackYu> It's 8:43pm here:)
[12:44]  * thomi makes the most of his time in the USA
[12:44] <jibel> it is always morning somewhere anyway
[12:45] <jibel> or good mornoon might fit all
[12:45] <JackYu> :)
[13:39] <thomi> balloons: hey - who was it who reported the saucy autopilot slowdown?
[13:40] <DanChapman> thomi it was senan, but I can confirm it aswell. Its not the case for all applications though
[13:40] <thomi> well, I fixed it yesterday
[13:41] <balloons> ohh did you?
[13:41] <thomi> in a typical case, test speed went from 15 seconds to under 5 seconds. It landed in 1.3 trunk last night, should get released to distro sometime soon
[13:41] <thomi> fixed it but good :)
[13:41] <DanChapman> thomi, awesome :-)
[13:42] <thomi> you can try it out manually until then: lp:autopilot/1.3 is th branch to grab
[13:47] <balloons> just yesterday I had a 13 min run.. I'm curious to see if this fixed it :-)
[14:17] <elopio> good morning avengers.
[14:29] <SergioMeneses> elopio, \o morning
[15:13] <elopio> hello SergioMeneses.
[15:13] <elopio> SergioMeneses, are you guys doing a Software Freedom Day in Colombia?
[15:14] <SergioMeneses> elopio, yes, but in another cities not mine
[15:43] <thomi> elopio: or pitti: could I ask one of you to review this please? https://code.launchpad.net/~thomir/autopilot/forward-port-changes/+merge/186369
[15:43] <thomi> elopio reviewed it yesterday, but I had to make some changes, re-merge in some new features and re-submit
[15:44] <thomi> but this branch will bring trunk in line with the 1.3 series
[15:50] <om26er> anyone with a mako. can you confirm bug 1226672
[16:06] <balloons> om26er, looking
[16:06] <balloons> om26er, there seems to be a non-smooth transition with the dimming/un-dimming stuff
[16:06] <balloons> turning it on displays the same symptoms
[16:07] <thomi> cgoldberg: perhaps you could review this for me please? https://code.launchpad.net/~thomir/autopilot/forward-port-changes/+merge/186369
[16:08] <om26er> balloons, yeah, for me if the screen is dimmed and i touch it afterwards it take like a second for it to comeback to bright state
[16:08] <om26er> its a recent regression like ~1week old
[16:08]  * balloons confirmed
[16:16] <cgoldberg> thomi, sure
[16:16] <thomi> cgoldberg: thanks - it's tricky getting stuff reviewed in this timezone :)
[16:18] <cgoldberg> thomi, I was just looking at AutoPilot.  you know how test results only get printed in batches after the run? (rather than as the tests execute)
[16:18] <thomi> cgoldberg: yes
[16:18] <cgoldberg> I think I can change that without using subunit... just using a TextTestRunner
[16:19] <cgoldberg> and you'll get results as they execute
[16:19] <thomi> cgoldberg: yeah, but that won't play nicely with the verbose log output
[16:22] <cgoldberg> thomi, how so?
[16:23] <cgoldberg> thomi, it displays like this:  http://paste.ubuntu.com/6124578/     just needs some indentation and line wrapping and it would look nice
[16:25] <balloons> om26er, can you run autopilot directly on the images anymore?
[16:26] <balloons> om26er, it fails with this for me http://paste.ubuntu.com/6124593/
[16:26] <om26er> balloons, I didn't try, I guess I need to make it rw first
[16:27] <balloons> om26er, yes
[16:27] <om26er> balloons, what do i need to touch ?
[16:27] <om26er> touch as in command lol
[16:28] <balloons> om26er, https://wiki.ubuntu.com/QATeam/TouchTesting#Switch_from_RO_to_RW , /userdata/.writable_image
[16:36] <balloons> I feel like I need more than 1 phone now, lol.. it's hard to test AP stuff and manual tests at the same time
[16:44] <rvr> balloons: lol
[16:45] <rvr> balloons: Let's hope you don't receive any call during an AP test ;)
[16:45] <balloons> om26er, so I installed the ubuntu-sdk do to the qmlscene error in the trace, but it changed nothing. it still fails
[16:45] <balloons> rvr, :-) That would be funny..
[16:45] <om26er> balloons, I enabled rw on my phone, I am going to try that
[16:47] <balloons> om26er, if you get it to work I want a log from the calendar app tests
[16:49] <om26er> balloons, the problem could probably with the MTP support as well, it just disconected while my test was running
[16:49] <om26er> now running the test directly on the phone terminal
[16:50] <balloons> om26er, ohh right, that's a nice workaround
[16:50] <om26er> balloons, it ran fine on my phone now
[16:50] <balloons> om26er, can you capture the log and push it to paste?
[16:50] <om26er> balloons, I think that's a known issue with MTP atleast a_sac knows about that
[16:52] <om26er> balloons, sure
[16:53] <thomi> cgoldberg: yeah, but if you run it with a functional test....
[16:54] <om26er> balloons, that didn't work, I ran the test as autopilot run -v test_name > calendar.log and the logs only had
[16:54] <om26er> Loading tests from: /usr/lib/python2.7/dist-packages
[16:54] <om26er> Tests running...
[16:54] <om26er> __pthread_gettid -2
[16:54] <om26er> Ran 1 test in 49.076s
[16:54] <om26er> OK
[16:54] <om26er> while the screen did show logs :p
[16:56] <balloons> om26er, only 1 test? there should be 5
[16:56] <om26er> balloons, I only ran the one that was failing for you. let me run all
[16:56] <balloons> om26er, you'll need to redirect stderr too, not just stdout :-)
[16:56] <balloons> om26er, they only fail when run as a group
[16:57] <balloons> om26er, use &> calendar.log
[16:57] <balloons> or the 2>&1 stuff
[16:57] <om26er> ack
[16:58] <balloons> hurray, I merged the pending manual test requests.. ty everyone who had one waiting ;-)
[17:09] <pitti> thomi: back, can do it now
[17:10] <pitti> thomi: yay new ap in saucy!
[17:12] <thomi> \o/
[17:14] <thomi> jfunk: I'm finding and reporting a lot of touch bugs - from the wiki it looks like I just need to report it with the correct tags: is that correct? I don't need to add it to a spreadsheet somewhere?
[17:15] <pitti> thomi: ah, still pep8 fun in the forward port :( (did you see the failure?)
[17:15] <thomi> oh FFS
[17:15] <thomi> I thought I fixed that
[17:15]  * thomi fixes it now
[17:15] <jfunk> thomi, I believe that is correct
[17:16] <jfunk> balloons, and iahmad made up some new ideas this morning I haven't fully caught up with yet
[17:16] <balloons> jfunk, thomi yes, I have no plans to use a spreadsheet
[17:16] <balloons> sane or not, launchpad will be my only data source for bugs :-)
[17:17] <pitti> thomi: done
[17:17] <thomi> pitti: pEP8 issues fixed & pushed
[17:17] <thomi> ok, cool
[17:17] <pitti> thomi: don't these pep8 tests run during package builds? I had assumed they were part of the non-DISPLAY unit tests
[17:18] <thomi> pitti: no, it's a pbuilder hook that automation adds
[17:19] <thomi> pitti: top approving it now
[17:19] <pitti> thomi: ah, would probably be better to add that to setup.py test (or whatever) so that you get these locally?
[17:19] <pitti> thomi: did you run the full tests with both py2 and py3?
[17:19] <thomi> pitti: yes, with tox
[17:19] <pitti> nice
[17:29] <jfunk> balloons, can you update the note at the top of the spreadsheet with the process that you've decided on for tracking automation - http://goo.gl/dwidOm
[17:31] <balloons> jfunk, we can just point to the wiki page.. I'd prefer that I think
[17:32] <jfunk> sure
[17:32] <jfunk> balloons, would you like to join our standup in the AM or PM
[17:33] <balloons> I'm typically around for both, haha, but my EOD is closer to the pm.. when is the pm again/
[17:44] <elfy> balloons: about 1am I think :)
[17:45] <thomi> jfunk: is the camera app missing from this list for a reason? https://wiki.ubuntu.com/QATeam/TouchTesting/BugFiling
[17:46] <balloons> thomi, because you haven't added it yet.. No, probably an oversight, let's add it
[17:46] <balloons> :-)
[17:47] <thomi> I seem to be finding a bug a minute... literally
[17:47] <balloons> https://bugs.launchpad.net/camera-app/+filebug?field.tags=avengers
[17:47] <thomi> balloons: are you adding it, or shall I?
[17:47] <thomi> ta
[17:47] <balloons> I'm on it, ty
[18:32] <cgoldberg> thomi, I reviewed your forward-port-changes MP.  few suggestions in comments
[18:34] <thomi> cgoldberg: thanks, good catches there :)
[18:34] <thomi> I'll fix it upand TA
[18:37] <cgoldberg> cool
[19:01] <elopio> alecu: are you trying to run the tests on the phone?
[19:02] <alecu> elopio: I was requested to run the unity8 autopilot tests on a branch I did for unity-lens-applications
[19:03] <alecu> elopio: I suppose I need to run it on the phone, yes.
[19:03] <elopio> veebers: are you here?
[19:03] <thomi> jfunk: this one's good fun: https://bugs.launchpad.net/powerd/+bug/1227319
[19:03] <veebers> elopio: yep, what's the haps?
[19:04] <elopio> awesome. alecu wants to run the unity8 autopilot tests using his application lens branch.
[19:04] <elopio> veebers: I have a vague idea of how to do it, but it would be better if you tell us both how to do it.
[19:06] <jfunk> thomi, hah nice
[19:06] <veebers> right, well I would build the package and use phablet-test-run. i.e. something like: phablet-test-run -n -c <package I've built 1> -c <package built 2> unity8
[19:06] <thomi> jfunk: yeah, it's totally reproducible as well
[19:06] <veebers> that will run all the unity8 tests, make that more specific if you want to run only a subset
[19:07] <alecu> veebers: do I have to flash anything before that?
[19:08] <veebers> alecu: actually that's a good point, are you using cdimage-touch or ubuntu-image when you're flashing your device?
[19:08] <alecu> veebers: I've been using ubuntu-image, but I'm setting it readwrite and installing some deps to build my packages
[19:08] <alecu> (deps= the vala compiler, and misc libraries)
[19:09] <veebers> ah ok, so your building on the device?
[19:09] <alecu> (actually, I've been just running my code from binaries, not from actual .deb packages)
[19:09] <alecu> veebers: yes, I've been doing that so far.
[19:10] <veebers> right, well a couple of options. You could just run the autopilot tests from your source (i.e. ssh in and run the autopilot command)
[19:10] <veebers> or you could install the debs and, again, ssh in a run autopilot
[19:10] <veebers> or you could run that command I mentioned (that will work as you have your ubunutu-system set to r/w)
[19:11] <alecu> veebers: awesome. I need to be afk for an hour or so now (kindergarten run), and I'll get to do it after that
[19:11] <alecu> thanks!
[19:12] <veebers> alecu: no worries. I'll still be around then so ping me if you have any issues
[19:12] <alecu> great
[19:19] <elopio> veebers: thanks!
[19:20] <veebers> nw
[19:41] <thomi> veebers: ping?
[19:44] <veebers> thomi: pong
[19:48] <thomi> veebers: hey - you did some OSK tests to test the various input hints right? Like the numeric input hint?
[19:48] <veebers> thomi: yep
[19:48] <thomi> any chance you could send me an html file that has all the different input hints?
[19:48] <veebers> at the moment the autopilot tests aren't running for the ubuntu-keyboard, I'm currently working on fixing that
[19:49] <veebers> thomi: let me have a look
[19:49] <thomi> I'm pretty sure I've found a bug in the OSK, but I need to be able to bring up a numeric keyboard
[19:51] <veebers> thomi: ah I see, neat. I think this is what you're looking for: http://doc-snapshot.qt-project.org/qt5-stable/qtquickcontrols/qml-qtquick-controls1-textfield.html#inputMethodHints-prop
[19:51] <veebers> you can find an example of using it in a qml script in the ubuntu-keyboard autopilot tests
[19:52] <thomi> veebers: I was hoping for html, but that's OK
[19:52] <thomi> I can fix it
[19:52] <veebers> thomi: ah I see. Sorry, not sure about that one
[19:52] <balloons> afternoon letozaf
[19:55] <letozaf> balloons, hey
[19:56] <letozaf> balloons, I did not carry on with the sudoku app migration to emulator, because yesterday I installed ubuntu touch on a nexus 4 I bought :P
[19:56] <balloons> letozaf, oO
[19:56] <letozaf> balloons, so I was playing around with it
[19:57] <balloons> :-)
[19:57] <letozaf> balloons, well after the Ubuntu Edge thing, I couldn't wait and so ...
[19:57] <balloons> letozaf, I was just going to say. I tried the tests this afternoon as they are and got this: https://bugs.launchpad.net/sudoku-app/+bug/1227340
[19:59] <letozaf> balloons, good! I mean at least I wasn't doing something wrong
[19:59] <letozaf> balloons, :P
[19:59] <letozaf> balloons, so should I wait for migrating that test or what ?
[20:00] <balloons> letozaf, lol.. I was going to ask if I could assign you the bug as well :-) It *looks* simple enough
[20:01] <balloons> but yes, I would fix the test and convert it as part of that
[20:01] <balloons> but lest I derail things too much, what did you think of ubuntu touch
[20:01] <balloons> ?
[20:03] <letozaf> balloons, oh ok :P
[20:03] <letozaf> balloons, well I like Ubuntu touch a lot,
[20:03] <letozaf> balloons, there is still a lot to work on though
[20:04] <letozaf> balloons, I was wondering if you prefer me to test on the Nexus 4 or carry on writing autopilot tests
[20:04] <letozaf> balloons, wish I could do both
[20:04] <letozaf> balloons, but haven't got enough time :P
[20:04] <balloons> letozaf, did you see this? https://wiki.ubuntu.com/QATeam/TouchTesting
[20:05] <letozaf> balloons, I saw the page but did not finish reading it, I will read it now
[20:06] <letozaf> balloons, mmm looks like it-s a lot of fun :P
[20:07] <balloons> letozaf, yes basically we're finding and reporting bugs, and then writing tests were it makes sense.. Feel free to join in however you wish.. Since you have a device, you should definitely have fun with it, but it will also make writing tests easier ;-)
[20:08] <letozaf> balloons, yes I also though that it will be easier now, if you tell me how to run them on the device :P
[20:08] <balloons> letozaf, ohh, well that's easy!
[20:08] <balloons> there are several ways to go about it, but you can run them from your desktop to a connected device via a phablet-test-run tool
[20:08] <balloons> let me see here..
[20:09] <balloons> adb shell into your phone and make sure you have what you need installed
[20:11] <letozaf> balloons, ok let me connect it to my PC
[20:11] <alecu> veebers: ping
[20:12] <alecu> veebers: I'm running the tests, after installing unity8-autopilot
[20:12] <veebers> alecu: pong
[20:12] <cgoldberg> thomi, ping.. I can add pep8 to the tox runs for AP.  where can I see what's being run now for static tests by it's CI?  is it just pep8, or anything else?
[20:12] <thomi> cgoldberg: it's just pep8. That information is stored in the cupstream config file
[20:13] <thomi> balloons: jfunk: There's a lot of bugs filed with the avengers tag. How are we handling prioritisation and escalation of those reports?
[20:13] <alecu> veebers: weird thing is that "unity8-fake-env" was installed too, and the tests used a fake camera app, and had a text watermark
[20:13] <veebers> alecu: ah right, that's part of the mocking. It's used for instance on the desktop
[20:14] <alecu> ah, great.
[20:14] <cgoldberg> thomi, ok... any interest in pyflakes or flake8 (aka, the combo) ?  while I'm in there I can add those also
[20:14] <veebers> alecu: you are wanting to run actual apps right?
[20:14] <thomi> cgoldberg: autopilot fials pyflakes - most need to be fixed, but there are some places where we fail for good reasons
[20:15] <thomi> cgoldberg: if there was a way to silence certain pyflakes errors in certain locations... that would be nice
[20:15] <thomi> cgoldberg: there's already a hook for pyfkales, so adding that would simply be a matter of changing the cupstream config
[20:15] <alecu> veebers: yes, I'd like to add tests to install some app from the click store, and run it. But that can wait, what I need to do today is run the current unity8 tests, and those seem to be working fine :-)
[20:15] <cgoldberg> thomi.. I can run it and cleanup what I can, and silence the rest.. it's pretty configurable
[20:17] <thomi> cgoldberg: well, the thing you won't be able to silence is the unused imports
[20:17] <veebers> alecu: ah ok, because I'm in the midst of landing some autopilot tests in unity8 that provide a decorator to disable that mocking for a single test
[20:17] <thomi> We have several unused imports that are there for backwards compatibility
[20:18] <veebers> ah awesome, it looks like the autolanding issues have been worked out. alecu: https://code.launchpad.net/~veebers/unity8/adding-app-lifecycle-tests/+merge/185514
[20:18] <veebers> that has an example of the decorator that should be available very shortly (seeing as though it's merged)
[20:20] <slickymaster> good night all
[20:23] <alecu> veebers: looks good, thanks!
[20:35] <cgoldberg> thomi, why are the unused imports needed?
[20:35] <thomi> cgoldberg: to maintain backwards compatibility with autopilot v1.2
[20:36] <cgoldberg> ah
[20:39] <elopio> om26er: here you go: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1227355
[20:39] <elopio> I'm sorry for the delay.
[20:40] <cgoldberg> thomi, so i just looked at pyflakes more.  i can't selectively ignore lines... (though I can monkey-patch it with a small wrapper script to do the job :)  but flake8 supports a "#NOQA" tag you put on the offending lines so they are skipped by pyflakes
[20:40] <om26er> elopio, cool, I'll try to talk to indicators developers about this
[20:40] <thomi> cgoldberg: that sounds like *exactly* what we need then :)
[20:41] <elopio> om26er: yes, please mark the other projects as also being affected by this bug.
[20:41] <thomi> cgoldberg: maybe work with the CI guys so we get flake8 support? We either need it in the upstream packaging code, or as a hook in the CI. I think I prefer the former, TBH
[20:41] <thomi> but we don't want to run pep8 twice
[20:43] <cgoldberg> thomi, gotcha.  what's the upstream packaging code?
[20:43] <cgoldberg> or where/who? :)
[20:43] <om26er> elopio, you were working on a branch to fix that, is that ready ? can I have a sneak peak ?
[20:43] <thomi> cgoldberg: we're upstream. "upstream packaging code" == debian/ dir in lp:autopilot
[20:43] <om26er> thomi, hey! what's the progress on Mir? landing anytime soon on the touch image ?
[20:43] <balloons> om26er, I'm confirming all your bugs :-) Anything you think is critical?
[20:44] <thomi> currently pep8 is run as a pbuilder hook, which is patched in by the CI infrastructure
[20:44] <elopio> om26er: almost https://code.launchpad.net/~elopio/ubuntu-ui-toolkit/base_autopilot_class/+merge/185170
[20:44] <thomi> om26er: it's in the touch image already!
[20:44] <om26er> balloons, there are high priority bug but nothing critical for today
[20:44] <elopio> om26er: but it will just work for the sdk. All affected apps need to add the .desktop.
[20:44] <cgoldberg> thomi, ah.  ok.. so move pep8 invocation to our tree?
[20:45] <om26er> thomi, right, I meant landing as default.. I do run it with 'touch .display-mir'
[20:45] <thomi> I think so, especially if we can use flake8 and selectively ignore some lines
[20:45] <thomi> om26er: I see, I guess that's a question for asac or someone.
[20:45] <thomi> still need to land a few fixes yet I suppose
[20:46] <om26er> well that would have been a question for anyone present at the Mir sprint :p
[20:46] <om26er> I hear you on the needed fixes
[20:47] <thomi> however, there are *soooo* many other bugs, I think mir is the least of our worries
[20:47] <thomi> for example, I can deadlock the kernel pretty easily
[20:47] <om26er> I am not caring for Mir as in "my work" rather my curiosity for the new technology
[20:48] <thomi> yeah
[20:49] <balloons> om26er, ugh, I'm finding more bugs trying to confirm yours :-(
[20:49] <elopio> om26er: your review will be nice, even if it's still not passing on jenkins ^^
[20:50] <om26er> balloons, I found a lot of bugs today
[20:51] <om26er> balloons, report the new one's and give them to me to confirm :)
[20:51] <asac> om26er: MIR? wait till folks get closer to the end of the sprint
[20:51] <asac> then we see
[20:51] <asac> they currently work in submarine mode on stuff :)
[20:51] <om26er> elopio, I'll review that ;)
[20:51] <om26er> asac, two days, two days :)
[20:52] <asac> om26er: who knows. maybe they decide to extend the sprint for another month :)
[20:52] <asac> oh wait... we dont have that much time left :)
[20:52] <asac> hehe
[20:52] <om26er> haha
[20:52] <asac> well. i am sure they will come along
[20:52] <asac> lets just be ready when that happens
[20:53] <balloons> A LOT can happen in 2 days
[20:53] <cgoldberg> thomi, sounds good.  I can do that...  only 1 prob I see.  flake8 isn't in repos.  it's in a PPA, and on PyPI, or I can check it into a dependency branch?  Not sure  how to deal with that.   I don't know the current build system well.. any tips, or someone I should talk to?
[20:55] <thomi> cgoldberg: yeah, you'd need to package it and get it into the repo
[20:57] <cgoldberg> thomi, ok.. on my todo list.  for now I can add it to tox.  since that's only used for local testing.. it will just pull it from PyPI.  does that sound ok?
[20:57] <balloons> om26er, could we have your tool add the bug tag too?
[20:57] <balloons> I feel like there should be a way
[20:57] <om26er> balloons, I tried that but seems to be a bug in apport-cli, tags don't work
[20:57] <om26er> balloons, I tried apport-cli --tag=avengers but that does not work
[20:57] <balloons> boo..
[20:58] <balloons> shall we blame pitti ? :-)
[20:58] <om26er> probably him, or launchpad ;)
[20:59] <thomi> cgoldberg: I guess that's OK, but it'll cause issues if we ever want to use tox during the package builds... but I guess we won't want to do that
[20:59] <elopio> om26er, balloons: this might be important for you, too: https://bugs.launchpad.net/unity-mir/+bug/1227359
[21:00] <om26er> I tried to run calendar_app testsuite under mir and the app never showed up (a few hours ago)
[21:00] <om26er> elopio, ^ that could be related ?
[21:01] <balloons> om26er, https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1227361
[21:01] <elopio> om26er: yes. I think the calendar is missing the desktop file. It's launched by a script that doesn't pass the desktop_file_hint argument.
[21:02] <elopio> om26er: on the tests, do we need to unlock the greeter?
[21:03] <om26er> elopio, yes we need to do that
[21:03] <elopio> uitk is certainly not doing that.
[21:03] <elopio> agh, I hate this branch so much. It started being a lovely clean up.
[21:04] <om26er> elopio, that needs more thinking, you would need to restart unity8 before unlocking since you cannot talk to unity8
[21:04] <om26er> and restarting unity8 is not a good thing as of now as that causes focus problems for apps
[21:04] <elopio> om26er: how was this working before?
[21:05] <om26er> elopio, you unlock the screen by hand. and in the upstream merger I have a script to unlock
[21:05] <balloons> man, launchpad is timing out this afternoon on page loads :-(
[21:05] <elopio> om26er: ah, so it will not fail thanks to your script, that's what I wanted to know :)
[21:06] <om26er> balloons, that worked for me :/ I don't think we need to click the first button because there is a field for mobile number already
[21:06] <om26er> that plus button is supposed to give us an option to add a second number
[21:06] <om26er> elopio, yeah
[21:07] <balloons> om26er, feel free to add 'touch-needs-autopilot' as needed to these bugs.. lots of these shuld be easy tests
[21:08] <om26er> balloons, sure
[21:08] <om26er> balloons, fwiw, adding a new contact screen is too complex and something that needs fixing
[21:15] <elopio> om26er: tests are passing! So, ready for review now. Please leave your vote.
[21:16] <om26er> elopio, i'll do that after the update-meeting, if thats fine ?
[21:16] <elopio> om26er: sure, no hurries. I'll need an approval from the sdk team to merge, and they are already gone.
[21:35] <jfunk> ping cgoldberg - check ##qa
[21:42] <om26er> balloons, ping
[21:42] <om26er> balloons, re bug 1226995
[21:42] <balloons> om26er, pong
[21:42] <balloons> om26er, ohh yes
[21:42] <om26er> is that with demo active ?
[21:42] <om26er> mterry wants to know
[21:42] <balloons> om26er, no the demo is not active
[21:43] <om26er> balloons, can you hop into #ubuntu-unity
[21:43] <balloons> it's really easy to see.. something funny is going on
[22:07] <balloons> ping om26er
[22:07] <om26er> balloons, hey
[22:07] <balloons> does the browser work for you?
[22:07] <balloons> it doesn't work for me on the 9/17 or 9/18 image
[22:08] <om26er> balloons, sure, it seems to be
[22:08] <om26er> balloons, I have the latest image ("blessed")
[22:09] <balloons> well I'm doing updates via the system.. sigh, I wonder if my phone isn't right then
[22:09] <balloons> I believe the issue I was seing with jibel's bug was due to the browser having crashed
[22:09] <balloons> aka this bug, https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1226995
[22:09] <om26er> elopio, on which image did you run those tests?
[22:09] <om26er> was that from cdimage ?
[22:10] <elopio> om26er: today's make flashed with ubuntu-system, then made writable.
[22:10] <om26er> elopio, try this test ubuntuuitoolkit.tests.gallery.test_gallery.GenericTests.test_progress_and_activity
[22:10] <elopio> s/make/mako
[22:11] <elopio> om26er: sure.
[22:11] <om26er> elopio, it does not bring up the sample window rather clicks inside unity8 and opens an app
[22:11] <elopio> Ran 1 test in 12.631s
[22:11] <elopio> OK
[22:11] <om26er> elopio, hm, for me it does something different
[22:11]  * om26er reboot
[22:12] <elopio> om26er: I'm running it from source.
[22:12] <om26er> elopio, did you run the whole suite at once ?
[22:12] <om26er> elopio, I am running the installled package
[22:12] <om26er> debs
[22:12] <elopio> om26er: the installed package doesn't have my fix.
[22:12] <om26er> elopio, aah, why  not  ?
[22:13] <elopio> om26er: did you build the deb from source?
[22:13] <om26er> elopio, I got these debs from your MR http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-saucy-armhf/1141/artifact/work/output/*zip*/output.zip
[22:13] <om26er> extracted them and pushed to the phone, and installed there
[22:13] <elopio> om26er: latest jenkins run was for rev 768
[22:14] <elopio> we need it to get rev 771
[22:14] <om26er> elopio, ok, I guess jenkins is building it right now, once it does I'll pick that again
[22:14] <elopio> on 768 it failed because of bug #1227359
[22:14] <elopio> om26er: yes, thank you.
[22:14] <elopio> let me know how it goes.
[22:15] <elopio> I'm going to get some rest, but I'll be back in ~1 hour.
[22:15] <om26er> elopio, I have the debs now, downloading them
[22:18] <om26er> elopio, that test is working now. running the whole suite just to be sure. code looks fine
[22:18] <elopio> om26er: \o/
[22:25] <om26er> elopio, 1 test failed http://paste.ubuntu.com/6125902/
[22:26] <elopio> of course, I only tested that one on the desktop :)
[22:27] <om26er> elopio, how about 'from testtools import skipIf'
[22:27] <om26er> and use skipIf as a decorator to skip
[22:27] <om26er> won't fail the test that way
[22:28] <elopio> om26er: no, take a look here: http://bazaar.launchpad.net/~elopio/ubuntu-ui-toolkit/base_autopilot_class/revision/773
[22:28] <elopio> when you instantiate a test case, you need to pass the name of a method to run.
[22:30] <elopio> about using the skipIf from testtools, you are right.
[22:30] <elopio> I'll get one less import. Changing...
[22:32] <elopio> now I'm leaving for real. I hope to get good and green news from jenkins when I'm back.
[22:33] <elopio> thanks om26er.
[22:33] <om26er> elopio, bye. jenkins will never go green with one failing test I would say
[22:33] <om26er> so you need to find a way for it to not show a failure
[22:33] <elopio> om26er: I already pushed a fix.
[22:35] <om26er> cool