[07:15] <Mirv> tsdgeos: Saviq: Qt 5.6.1 is now in yakkety-proposed and lp:unity8 was updated with the changelog entry -> you'll need a rebuild.
[07:16] <Saviq> Mirv, ack
[07:18] <Saviq> bzoltan, ↑
[07:18] <Mirv> he knows too
[13:08] <mterry> mzanetti, so I've been living with 0103.  I did mispress once or twice, but it was seemingly due to me pressing in between OSK keys.  Otherwise I've been OK
[13:09] <mzanetti> mterry, I think this is related to the screen size
[13:09] <mterry> mzanetti, fair!  I've been using a krillin
[13:09] <mzanetti> mterry, I also never had that problem with krillin that I dragged the OSK down a bit while typing
[13:09] <mzanetti> but on turbo I do have it when writing text
[13:57] <Saviq> mzanetti, isn't it because of GU? i.e. keyboard has the "drag down" threshold in px, not taking GU into account?
[13:58] <mzanetti> good question
[13:58] <mzanetti> could be, depends how the OSK is implemented
[13:58] <mzanetti> and then it's still a question whether/how the actual size matters
[17:21] <mterry> Saviq, so I haven't been paying full attention to silo 23 today.  Looks like there's some rebuilds and a persistent failure on ubuntu-system-settings/yakkety/powerpc?
[17:57] <om26er> Hi! How can I run a single unity8 qml test ? I am trying to fix one but its a little painful to wait for jenkins to finish with each commit
[18:03] <Saviq> mterry, persistent? I only saw it once an hour or two ago
[18:03] <Saviq> could you try and rebuild https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-077/+build/10521585
[18:04] <mterry> Saviq, I rebuilt it and it happened again.  And I saw it in another silo
[18:04] <mterry> ok, rebuilding again
[18:04] <Saviq> om26er, run `make testComponentName` or `make testComponentName FUNCTION=ComponentName::testName`
[18:04] <Saviq> that latter might not work, but if it does - it will let you run a single test
[18:04] <Saviq> mterry, wonder if qt 5.6
[18:04] <mterry> It should work, I use it regularly
[18:05] <mterry> (FUNCTION= that is)
[18:06]  * Saviq doesn't, ninja doesn't support that
[18:08] <om26er> mterry, which directory should I run that from ?
[18:09] <mterry> om26er, if you use ./build.sh, you can run it from builddir.  make -C builddir xvfbtestShell FUNCTION=Shell::test_XXX
[18:11]  * mterry reboots
[18:29] <Saviq> mterry, looks like persistent fail after all
[18:30] <mterry> boo
[18:34] <om26er> mterry, I did what you suggested, seems the test is never run: http://paste.ubuntu.com/21037499/
[18:34] <om26er> Totals: 0 passed, 0 failed, 0 skipped, 0 blacklisted
[18:35] <mterry> om26er, xvfbtestMenuItemFactory then
[18:35] <mterry> om26er, the test name and function prefix need to match
[18:37] <om26er> mterry, thanks, seems to work
[18:37] <om26er> :)
[18:43] <mterry> josharenson, did you update the gui branch?  Should I review it again?
[18:44] <josharenson> mterry: not yet, eating lunch real quick
[18:44] <mterry> no worries, just checking in
[18:53] <om26er> Can anyone please take a quick look at my branch[1], it adds object names for some UI components for the Wizard. We need this for Ubuntu System Tests project.
[18:53] <om26er> [1] https://code.launchpad.net/~canonical-platform-qa/unity8/add_object_name_for_setup_wizard/+merge/300380
[19:11] <josharenson> mterry: pushed it for now w/ a small hack
[19:12] <josharenson> but 99.9% there
[19:14] <mterry> josharenson, OK.  I'll give it a look over after