[00:32] <racarr_> back in a few hours
[01:25] <RAOF> Bah. We have two nearly identical places where we probe the graphics platform.
[01:25] <RAOF> I always forget to update one :*
[07:13] <RAOF> Bah, cmake.
[07:15] <RAOF> Why can't you pkgconfig correctly?
[07:33] <alf_> racarr_: yes, at some point when heavy rendering is going on the whole system freezes for some time and then continues normally, I "solved" it by going back to the latest 3.15 kernel. Perhaps an early 3.16 kernel will do but I haven't had the time to bisect.
[07:46] <alf_> RAOF: duflu: Hi! Any idea about http://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-mako/2347/console ?
[07:46] <alf_> (see failure at end of log)
[07:47] <RAOF> alf_: Yup:  Package libboost-program-options-dev is not installed.
[07:48] <RAOF> Not using apt + a repository strikes again!
[07:48] <duflu> alf_: It seems build-deps are prepared based on the system installation. And those are wrong for the new tree being built. Someone needs to kick in the new package ... libmirplatform-dev:armhf depends on libboost-program-options-dev; however:
[07:48] <duflu>   Package libboost-program-options-dev is not installed.
[07:48] <duflu> So.. it's only CI that's broken :/
[07:49] <duflu> ... or our x-compile scripts. I thought Alberto made them smart and this should happen automatically
[07:49] <duflu> ... assuming CI uses our scripts
[07:52] <RAOF> duflu: Incorrect!
[07:52] <RAOF> :)
[07:52] <duflu> RAOF: OK *shrug*. I care not for new problems this week :/
[07:52] <duflu> There's plenty of old problems still
[07:54] <RAOF> alf_: Want to try with /~raof/+junk/testrunner-testing/? :)
[08:01] <duflu> alf_: I stole your bug BTW ... bug 1340510
[08:02] <alf_> duflu: Ah, good, thanks. I wanted to unassign myself since I got caught up with other things, but forgot.
[08:05] <alf_> RAOF: sure, how do I try that?
[08:05] <RAOF> alf_: I've already started - http://s-jenkins.ubuntu-ci:8080/view/mediumtests/job/mir-mediumtests-runner-mako/2348/console
[08:05] <alf_> RAOF: great, thanks
[08:06] <RAOF> Faster, silly device!
[08:09] <RAOF> Bah. Stupid thing.
[08:12] <RAOF> alf_: Died with a transient unrelated error, so I've started it again.
[08:24] <RAOF> Sweet.
[08:24] <RAOF> Looks like that's working.
[08:30] <RAOF> alf_: That looks like it's good; feel free to push that branch to the main testrunner bit.
[08:30] <RAOF> EOW for me!
[08:31] <alf_> RAOF: Thanks! Enjoy you weekend!
[08:38] <alan_g> alf_: is "libmirplatform:armhf to be configured is 0.5.1+14.10.20140728-0ubuntu1" being addressed or should I jump on it?
[08:42] <alf_> alan_g: RAOF's update to the test runner fixes this /~raof/+junk/testrunner-testing/, I will merge into our "upstream" testrunner branch
[08:44] <alan_g> Excellent
[08:45]  * alan_g goes off to play with parsing our code with libclang
[11:59] <greyback> alf_: hey, I've not dug yet, but I fear our "last frame not drawn" bug has appeared again https://bugs.launchpad.net/unity8/+bug/1354407 - it may be qtmir, and it may be mir. Just an FYI as yet
[12:00] <alf_> greyback: ack
[15:25] <racarr> Morning.
[15:26] <racarr> late psuedo standup: Still working on emulator bug...have something to test now but not 100% sure how to build an appropriate image (modified the emulator target egl impl)
[15:27] <racarr> proposed a qtmir test skeleton
[15:33] <racarr> sigh touchspot renderables failed
[15:33] <racarr> the sha1sum check again due to other stuff landing
[15:34] <kdub> groan
[15:34] <racarr> I'm considering making an mp that deletes it and adds a file like
[15:35] <racarr> README-release.txt
[15:35] <racarr> that has a checklist which includes
[15:35] <racarr> 1. Have any headers in include/ changed
[15:35] <racarr> which is just as easy to tell from the diff
[15:35] <racarr> as looking at the sha1sum file
[15:36] <kdub> yeah, I think part of the problem too is we need to firm up the interfaces
[15:37] <kdub> like look at how the downstreams are using the interfaces
[15:37] <kdub> and then bury the stuff they arent using
[15:37] <racarr> mm
[15:37] <kdub> and make sure those that are used are sensible
[15:38] <kdub> thats not quite the immediate problem, but along the same tangent and important
[15:41] <racarr> my guess is there is a bunch of stuff that could be hidden at this point but not sure
[15:42] <kdub> yeah, and even more if you take the set of stuff that is only used by the demo shell
[15:43] <alan_g> We don't want to be quite that strict - there's likely stuff we should expose that hasn't been used for the phone
[15:45] <kdub> yeah, agreed
[15:45] <kdub> I guess my main point is that an audit of the interfaces would help
[15:54] <tedg> Can I turn on the Mir LTTng tracepoints with an env var, or is it something I need to compile in?
[15:57] <racarr> env variable!
[15:58] <racarr> tedg: see doc/component_reports.md
[15:59] <racarr> http://unity.ubuntu.com/mir/component_reports.html
[15:59] <racarr> so e.g. MIR_SERVER_INPUT_REPORT=lttng
[15:59] <racarr> I doubt that list of reports is up to date
[15:59] <racarr> lol
[16:00] <tedg> Ah, cool.
[16:00] <tedg> So I guess that needs to go in the session startup script
[16:01] <tedg> I'd like to get a report on when surfaces are allocated and displayed
[16:01] <tedg> Looking at app startup
[16:01] <tedg> Which would be helpful? :-)
[16:03] <racarr> tedg: You could get that from the session mediator report which logs IPC calls I guess
[16:03] <racarr> i.e. create_surface
[16:03] <tedg> racarr, Cool, thanks!
[16:05] <racarr> :) np
[16:38] <racarr> rsalveti: Ping?
[16:39] <racarr> I am trying to test changes to the emulator libEGL...and having some difficulty understanding exactly how the emulator images are assembled
[17:19] <rsalveti> racarr: https://wiki.ubuntu.com/Touch/Emulator
[18:32] <racarr> rsalveti: So I see on one hand there is the -system parameter to the emulator binary and then also
[18:32] <racarr> the system.img is copied in to the
[18:32] <racarr>  /var/lib/lxc...etc and mounted at boot
[18:33] <racarr> what is the deal with that?
[18:33] <racarr> Having to deviate from the instructions slightly for various reasons so trying to understnad what is happening
[18:34] <racarr> rsalveti: also having terouble understanding the raw disk vs ...non raw distinction
[18:39] <racarr> also what is the ubuntu-*system.img vs just
[18:39] <racarr> system.img
[18:40] <racarr> sorry...im really unknowledgeable about the whole image business I guess :)
[18:47] <racarr> haha...ok now I tried using raw disks, so now I can mount my new ubuntu-system.img and found
[18:47] <racarr> a libEGL with a new md5sum so I guess that worked
[18:48] <racarr> well
[18:48] <racarr> nvm lets see what happens when I replace system.img with ubuntu-*system.img
[18:48] <racarr> actually lets have lunch
[18:48] <racarr> brb
[19:02] <racarr> ohhhh
[19:02] <racarr> theres a system.img
[19:02] <racarr> inside the system.img
[19:02] <racarr> ...
[19:05] <racarr> grr
[19:33] <racarr> Yay it works
[19:35] <racarr> it turns out the system.img that building the android source package produces is the system.img inside the system.img inside the sdcard.img that creating an emulator instance
[19:35] <racarr> creates
[19:35] <racarr> and the third system.img is just a decoy
[19:35] <racarr> (the one outside the sdcard.img)
[19:35] <racarr> lol
[19:35] <racarr> how does something like that happen
[20:07] <rsalveti> racarr: yeah, it's horrible
[20:07] <rsalveti> we're fixing that soon
[20:07] <rsalveti> really confusing atm
[20:14] <racarr> rsalveti: :D
[21:15] <qengho> racarr: Hi hi.  I tried to convert your Chromium ozone-mir branch into a distro patch for current stable Chromium -- really the only way I can use it -- and I had some trouble.  Do you have some time to help me debug it?
[21:17] <qengho> As I understand it, we would like to avoid code duplication with ozone-wayland, so we try to extend it, overriding where we need to.