[08:48] <Mirv> tsdgeos: oh, is there a 'floor' problem in qmluitests too? https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/amd64/u/unity8/20160727_024846@/log.gz
[08:48] <Mirv> or is that test running some funky version of unity8, that's also possible
[08:49] <Mirv> no, that was fixed, so yes unfortunately autopkgtests do the wrong thing
[08:49] <tsdgeos> Mirv: seems very much what i fixed, no?
[08:49] <tsdgeos> is it compiling some old version or something?
[08:50] <Mirv> tsdgeos: yes, it's compiling old version
[08:50] <Mirv> tsdgeos: then elsewhere with new version, two failing tests: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/amd64/u/unity8/20160727_034401@/log.gz
[08:51] <Mirv> that could be real Qt 5.6.1 breakage
[08:52] <tsdgeos> FAIL!  : qmltestrunner::PhoneStage::test_selectAppFromSpread(App 5) Uncaught exception: Type error
[08:52] <tsdgeos> that looks bad-ish
[09:06] <tsdgeos> Mirv: if you file a bug maybe i can have a look later today/tomorrow if noone beats me to it?
[09:25] <Mirv> tsdgeos: bug #1606835
[09:25] <Mirv> oh right there were others
[09:27] <Mirv> updated
[11:48] <om26er> mzanetti, Hello
[11:48] <mzanetti> om26er, hi
[11:48] <om26er> mzanetti, mind taking a look at https://code.launchpad.net/~canonical-platform-qa/unity8/add_object_name_for_setup_wizard/+merge/300380
[11:49] <om26er> we need to land that for some testing needs in ubuntu-system-tests, it just adds object names
[11:52] <Mirv> Saviq: is dandrada around or vac?
[11:52] <Mirv> Saviq: or can you help with validating silo https://requests.ci-train.ubuntu.com/#/ticket/1715 (the relative mouse events part)
[11:52] <Saviq> Mirv, he'll be around soon (timezone)
[11:53] <Mirv> yeah I was thinking timezone but then thinking Brazil should be up already :)
[11:54] <Saviq> Mirv, http://www.timeanddate.com/worldclock/brazil/joinville almost ;)
[12:38] <Mirv> dandrader: hey! could you test the relative mouse events part of https://requests.ci-train.ubuntu.com/#/ticket/1715 on vivid and report on the ticket?
[12:39] <Mirv> dandrader: and if you have ideas for the test plan feel free to improve
[12:39] <dandrader> Mirv, ok
[12:40] <dandrader> Mirv, from qt's perspective, it's about hover events carrying timestamps
[12:41] <Mirv> dandrader: yeah, the QA would just like to know what to look for and regression potential
[13:27] <tsdgeos> Mirv: something is weird with those type error failures
[13:27] <tsdgeos> it fails when doing
[13:27] <tsdgeos> tile.mapToItem(spreadView)
[13:27] <tsdgeos> with tile being TransformedSpreadDelegate_QMLTYPE_40_QML_54(0x560f74f440a0, "spreadDelegate_32")
[13:27] <tsdgeos> and spreadView QQuickFlickable_QML_50(0x560f721a7de0, "spreadView")
[13:27] <tsdgeos> it "should work"
[13:35]  * Saviq wonders if Popescu uses yakkety proposed, he mentioned this error in a bug
[13:36] <Saviq> in bug #1606501
[13:39] <Saviq> mterry, FYI: https://code.launchpad.net/~saviq/ubuntu-system-settings/no-test-powerpc/+merge/301271 but also bug #1606501
[13:40] <Saviq> noo
[13:40] <Saviq> bug #1606835
[13:40] <Saviq> so even when we "fix" uss/powerpc, we'll be fooked
[13:41] <Saviq> and mapToItem failing isn't even funny
[13:41] <mterry> Saviq, this seems like a case where we back out 5.6 and let them fix their mess without blocking all of ubuntu
[13:41] <Saviq> mterry, tell that to Mirv...
[13:43] <Mirv> qmluitests was supposed to be fine for 5.6 :(
[13:43] <mterry> Mirv, we in unity8/ubuntu-system-settings/maliit-framework are hitting some real test problems with qt5.6, is that widespread or isolated to these three?
[13:43] <Mirv> anyway, Kubuntu are already doing their uploads to yakkety since they've been holding off their cycle work until 5.6 is in
[13:44] <Mirv> mterry: it seems isolated to those three, although likely Qt on powerpc is not perfect (and never supported by upstream in the first place)
[13:44] <Mirv> mterry: Debian doesn't have packages they'd have problems with it since they've carried Qt 5.6 since June
[13:44] <mterry> Mirv, qmluitests isn't a powerpc issue, but sure, the other two are
[13:44] <mterry> Mirv, got it
[13:45] <Mirv> right, the build phase only knows of unit tests
[13:45] <mterry> Mirv, but presumably we've also ran qt5.6  :)
[13:45] <mterry> and not come up with problems?
[13:45] <Mirv> mterry: yeah, I've run it on yakkety Unity 8 + Plasma + LxQT desktop and on xenial phone.
[13:46] <mterry> Mirv, OK.  Seems to be just a lot of problems in our immediate space.  We'll work around it
[13:46] <mterry> Saviq, I do like the amd64 re-enabling in that MP...
[13:46] <mterry> arm64 rather
[13:46] <mterry> Keep getting those confused
[13:47] <Mirv> mterry: yes, I wouldn't care about powerpc much (unliked s390x which got fixed before upload), but I would have blocked on qmluitests had I known there is trouble - albert checked it in May/June and it was fine back then but this is possibly due to changes in bug fix release 5.6.1
[13:48] <Saviq> mterry, yeah let's see how that works, I had a look at the bug and it said fixed, so...
[13:49] <mterry> Saviq, I see you added to silo, cool
[13:49] <Saviq> except that won't help with britney on yakkety :/
[13:53] <Mirv> inevitable Qt upgrades will happen in development Ubuntu versions from now on too, (Qt 5.7 in yakkety+1) unless we start to make noise about wanting to stay in the upstream's LTS (5.6). other Qt users however expect 5.7, 5.8...
[13:57] <tsdgeos> Mirv: nice that you don't see https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1582144 anymore :)
[13:58] <mterry> Mirv, yeah I expect Qt upgrades, just seemed like the problems were more widespread than they were (lots clustered in our stuff)
[13:59] <mterry> Saviq, yeah :-/
[14:00] <Mirv> mterry: yeah it'd help if we would have time (other than me) to test new releases, I've been filing bugs and offering PPA since March
[14:00] <Mirv> and not that I'd have too much time in general either
[14:06] <tsdgeos> Mirv: we will get Qt 5.6 only in yakkety right? not on vivid overlay
[14:07] <Mirv> tsdgeos: in yakkety, and xenial overlay as soon as everyone agrees. we should be switching to xenial soon anyway.
[14:07] <tsdgeos> SOON (TM)
[14:07] <tsdgeos> :d
[14:07] <tsdgeos> Half Life 3 confirmed!
[14:07] <Mirv> tsdgeos: or at least I've understood 5.6 is wanted by "everyone"
[14:07] <tsdgeos> SCNR
[14:08] <Mirv> tsdgeos: and it's upstream LTS so it makes sense to combine with our LTS
[14:08] <tsdgeos> total sense
[14:08] <Mirv> tsdgeos: I'd mostly like zsombor back and look at UITK + Qt 5.6. but that's a couple of weeks. and obviously Unity 8 will need these qmluitests fixed.
[14:09] <tsdgeos> on it
[14:16] <dandrader> Mirv, added a comment to https://requests.ci-train.ubuntu.com/#/ticket/1715 . Thanks!
[14:23] <tsdgeos> ok, first problem found
[14:23] <tsdgeos> seems mapToItem now requires the 3 arguments
[14:23] <tsdgeos> not only item
[14:23] <tsdgeos> luckily we were only [ab]using it in 1 place
[14:24] <tsdgeos> mzanetti: Saviq: ↑↑↑
[14:24] <Saviq> ah
[14:24] <tsdgeos> it's just that the guy that added the check may have added a warning
[14:25] <tsdgeos> would have been much easier to undersatnd
[14:25] <mzanetti> what issue is this?
[14:25] <Saviq> tests failing in Qt 5.6.1
[14:25] <mzanetti> ah
[14:25] <Saviq> and for good reason
[14:26] <mzanetti> weird thing is, I've fixed for sure like 5 occurances of that mapToItem argument in the last year
[14:26] <mzanetti> (after making that very same mistake quite ofter before that time)
[14:26] <Mirv> tsdgeos: great
[14:26] <mzanetti> whenever I debug thigns it seems to totally not work, but still strange that things don't break more because of wrong usage of this
[14:27] <tsdgeos> Mirv: now i'll tackle the other, but that other one may "just" be that we have unstable tests
[14:27] <Mirv> tsdgeos: the other did happen on both amd64 and i386 so at least fairly often
[14:45] <tsdgeos> mzanetti: will you review https://code.launchpad.net/~aacid/unity8/mapToItem3Args/+merge/301283 ?
[14:46] <mzanetti> tsdgeos, ack
[14:47] <mzanetti> tsdgeos, in order to test it I'd require Qt 5.6, no?
[14:47] <tsdgeos> kind of D:
[14:47] <tsdgeos> or you can just say "ok it works now"
[14:47] <tsdgeos> i mean
[14:47] <tsdgeos> "ok it still works"
[14:47] <mzanetti> yeah, I know what you mean
[14:47] <tsdgeos> and read the code of mapToItem
[14:47] <tsdgeos> where it checks for args to be 3 or 5
[14:49] <tsdgeos> mzanetti: actually give me a minute, there's a wrong mapFromItem call too that i'll add to the branch
[14:51] <tsdgeos> mzanetti: done
[14:51] <mzanetti> ack
[14:52] <mzanetti> ok. now I need to actually test it on my device
[14:53] <tsdgeos> he he
[14:53] <tsdgeos> sorry
[14:53] <tsdgeos> Mirv: so https://code.launchpad.net/~aacid/unity8/mapToItem3Args/+merge/301283 should fix the two test failures, is it easy for you to add to that auto testing or we need to land it?
[14:54] <Mirv> tsdgeos: it is easy for me to push to yakkety and update your trunk manually, if that's what you're asking
[14:54] <Mirv> tsdgeos: similar to what I did when landing the floor include fix
[14:55] <tsdgeos> yes/no i mean if you can test it without our trunk being changed
[14:55] <Mirv> tsdgeos: no, I can't test it easily. and I guess the change should be #ifdef for < 5.6 ?
[14:55] <tsdgeos> Mirv: no
[14:55] <mzanetti> mterry, hey ho. running your branch still and rebooted for the first time. seems you broke the SIM PIN entry
[14:56] <mterry> mzanetti, ah crud.  I thought I kept Lockscreen compatibility
[14:56] <mterry> mzanetti, will look into that, thanks
[14:56] <mzanetti> mterry, I looked at the diff, didn't seem you removed it
[14:56] <mzanetti> mterry, but maybe some wiring died
[15:58] <Saviq> mterry, grrrrrr https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-077/+sourcepub/6755846/+listing-archive-extra
[15:59] <Saviq> wtf, I tried it on a porter box and it does the right hting
[15:59] <mterry> Saviq, huh...
[15:59] <mterry> Saviq, and your change was small -- the support already seemed there?  (unless we've been running tests in arm64 unbeknownst to us?)
[15:59] <mterry> which wouldn't surprise me, if we've been working there for a while
[16:00] <Saviq> mterry, easy to check
[16:00] <Saviq> hah it was testing on arm64 https://launchpadlibrarian.net/274491605/buildlog_ubuntu-yakkety-arm64.ubuntu-system-settings_0.4+16.10.20160722.1-0ubuntu1_BUILDING.txt.gz
[16:01] <Saviq> *but* I tried on a porter box and it did the right thing!
[16:01] <Saviq> the previous version didn't test, though https://launchpadlibrarian.net/271833732/buildlog_ubuntu-yakkety-arm64.ubuntu-system-settings_0.4+16.10.20160708-0ubuntu1_BUILDING.txt.gz
[16:03] <Saviq> wth
[16:12] <mterry> :-/
[16:12] <mterry> Saviq, check phases of the moon
[16:21] <Saviq> mterry, I added some debug prints to debian/rules, let's see...
[16:51] <om26er> ChrisTownsend, Hi!
[16:51] <ChrisTownsend> om26er: Hey
[16:51] <om26er> ChrisTownsend, whats the recommended way to install libertine on desktop ? and which tech should be used container or chroot ?
[16:52] <ChrisTownsend> om26er: apt-get install libertine
[16:52] <ChrisTownsend> om26er: And LXC for sure
[16:52] <bregma> om26er, trust the tools to choose the right default
[16:52] <ChrisTownsend> om26er: Yes, also what bregma says.  Don't specify the container type and let it choose it for you.
[16:55] <om26er> ChrisTownsend, what would an example to create a container look like ?
[16:56] <ChrisTownsend> om26er: If using the cli, 'libertine-container-manager create -i test -n "Test"'  Of course, you can call -i and -n whatever you want.
[16:56] <ChrisTownsend> om26er: If you use the UI, well, it's just clicking the right things:)
[16:57] <ChrisTownsend> om26er: Also, the manpage and help is your friend:wink:
[16:58] <om26er> ChrisTownsend, ok, seems to have failed for me :/ http://paste.ubuntu.com/21161321/
[16:59] <ChrisTownsend> om26er: Hrmm, lxc issue.  This is the pertinent line:
[16:59] <ChrisTownsend> lxc 20160727215736.439 ERROR    lxc_utils - utils.c:safe_mount:1692 - Invalid argument - Failed to mount /sys/kernel/debug onto /usr/lib/x86_64-linux-gnu/lxc/sys/kernel/debug
[17:00] <ChrisTownsend> om26er: Are you using yakkety or xenial?
[17:00] <om26er> we need lxc guys in this channel
[17:00] <om26er> ChrisTownsend, that's yakkety
[17:01] <ChrisTownsend> om26er: They hang out in #lxcontainers
[17:01] <om26er> Need ubuntu specific channel as well :)
[17:02] <om26er> ChrisTownsend, shall I just try in a VM and see how it works out of the box in 16.04.1 ?
[17:04] <ChrisTownsend> om26er: It's working for me on my Yakkety system.
[17:05] <ChrisTownsend> om26er: I guess you can try in a VM.  I've never tried it, so I'm not sure what your experience will be like.
[20:58] <mterry> mzanetti, you said sim unlock screen didn't work for you?  it seems to be working for me using phonesim with silo 23 (which granted has more than just greeter-no-lockscreen in it...  maybe that branch broke something that another branch fixed...)