[00:18] <racarr> Derp! I was using
[00:18] <racarr> sequenced expectations to wake up a series of wait conditions
[00:18] <racarr> but didn't actually sequence the expectations
[00:19] <racarr> Got a free bonus from this derp of spending a good hour reading InputDispatcher.cpp *facepalm*
[00:27] <RAOF> Whoops!
[00:30] <racarr> Any opinions on https://code.launchpad.net/~robertcarr/mir/rebuild-input-focus-selection/+merge/158505 ?
[00:38] <RAOF> racarr: Looks OK to me.
[00:41] <racarr> RAOF: Ok. Thanks :) Once I finish my branch (needs a few fixes...but after 11 hours it is...not computer time) will switch this one to approved if no one finds anything
[08:18] <alan_g> duflu: could you re-review https://code.launchpad.net/~kdub/mir/fix-shutdown-bug/+merge/158710 - thanks
[08:20] <duflu> alan_g: Done. Sorry but I've obviously been busy with my own branches today
[08:21] <alan_g> duflu: np - was an easy one to clear
[08:22] <duflu> Wow, gcc is so bad at error messages. I just spent 10 minutes trying to decipher various errors. None of which told me the truth -- missing closing parenthesis
[08:23] <duflu> Almost switched to clang
[08:24] <alf_> duflu: I've heard that g++-4.8 has improved error messages a lot
[08:24] <alan_g> alf_: I've heard that too. (From one of the developers. ;)
[08:45] <alan_g> Actually, thinking about it - from one of the *library* developers, so that's more convincing.
[09:07] <alf_> alan_g: Regardless of how much it has improved, at least (and at last) there is some interest in it... the benefits of competition :)
[09:08] <alf_> alan_g: a.k.a. why even wayland supporters should be excited about Mir ;)
[09:11] <alan_g> alf_: I don't think the mir protocol is in the same solution space as Wayland.
[09:14] <alf_> alan_g: Perhaps not, but they are *conceived* as being competing technologies, and that's enough to drive competition.
[09:37] <duflu> alan_g: Could you please ignore my branches for the next hour or two. Otherwise my day will never end :)
[09:38] <alan_g> duflu: Sure.  Alternatively, you could also ignore my comments for the next hour or two. ;)
[09:38] <duflu> alan_g: Yeah I normally close my email for the last hour or so of the day. Just missed the cut-foff
[09:38] <duflu> cut-off
=== alan_g is now known as alan_g|tea
=== alan_g|tea is now known as alan_g
[10:09] <alan_g> kgunn: Good morning
=== alan_g is now known as alan_g|tea
=== alan_g|tea is now known as alan_g
[15:05] <kdub> good morning! status, bumped our scripts to raring, trying to think of a way to ease reviewing my display branch, and working on getting galaxy nexus to look nice again
[15:12] <alf_> status: working on vt switching communications management, currently blocked on improving our test infrastructure so I can perform needed tests
[15:14] <alf_> kdub: alan_g: racarr: It seems that all this time our display server test process (launch_server_process(...)) didn't exit() after the server finished. I am trying to make it exit(), but it seems a lot of tests depend on the broken behavior in some way or another.
[15:15] <alan_g> alf_: "this time"?
[15:16] <alan_g> alf_: "all this time"?
[15:18] <alf_> kdub: alan_g: racarr: I mean "since the beginning" :)
[15:21] <alan_g> alf_: I find that hard to believe - I occasionally saw zombi server processes near the beginning, but AFAIK that got fixed.
[15:21] <alan_g> alf_: What makes you think it isn't exiting?
[15:25] <alf_> alan_g: There is no exit() after the server finishes, so after finishing, the server process continues executing into the test code. In tests up to now this wasn't visible because we let the test infrastructure kill the server process after the test. However, in a test I am working on, the server is terminated during the test and all of this becomes apparent.
[15:26]  * alan_g looks
[15:27] <kdub> hmm
[15:28] <alan_g> alf_: why doesn't it exit in tear_down_clients()?
[15:33] <alan_g> alf_: I guess you meant: "all this time the server exited in tear_down_clients() - not in launch_server_process() where I'd now like it to".
[15:34] <alf_> alan_g: s/tear_down_clients/tear_down_server/?
[15:36] <alan_g> alf_: I'm still not following
[15:37] <alf_> alan_g: kdub: hangout?
[15:37] <alan_g> Was just about to suggest it
[15:37] <kdub> sure
[15:37] <alf_> alan_g: kdub: creating one
[15:39] <alf_> alan_g: kdub: https://plus.google.com/hangouts/_/ba672682fda0c13019ca0531e91417dc0ce83b39?authuser=0&hl=en
=== pete-woods1 is now known as pete-woods
=== francisco is now known as Guest86369
[16:16] <racarr> Morning
=== mhall119 is now known as mhall119|lunch
[16:34] <kdub> hello racarr
[16:37] <racarr> Hey :)
=== alan_g is now known as alan_g|life
=== mhall119|lunch is now known as mhall119
[17:57] <racarr> ugh
[17:57] <racarr> was finally ready to propose my new input dispatcher controller stuff and
[17:57] <racarr> realized I based it off ease-shell-configuration
[17:57] <racarr> because it required changing session manager arguments
[18:11] <racarr> only 12 conflicts to remove it!
[18:39] <kgunn> tvoss: can you sanity check my whiteboard entry on this bp ?
[18:39] <kgunn> https://blueprints.launchpad.net/ubuntu/+spec/client-1303-unity-ui-windowmanager
[18:40] <tvoss> kgunn, tomorrow fine with you?
[18:40] <kgunn> sure :)
[18:40] <tvoss> kgunn, cool, thx
[19:42] <racarr> https://code.launchpad.net/~robertcarr/mir/reflow-input-focus-selection/+merge/159225 new DispatcherController :)
[19:42] <racarr> couldn't get bzr to cooperate so had to manually back out ease-shell-configuration
[19:43]  * mlankhorst couldn't get bzr to work, at all, now using git-bzr :)
=== kdub is now known as kdub^lunch
[20:08] <thomi> morning
[20:25] <racarr> MORNING!
[20:25] <racarr> *descends in to hunger psychosis as lunch becomes later and later...*
[20:28] <racarr> ah phew its here
=== kdub^lunch is now known as kdub
[21:56] <kgunn> robert_ancell: i'd love to make the team meeting...but had another 5am start.
[21:56] <robert_ancell> kgunn, fair enough!
[21:57] <kgunn> i'll be on later during baseball practice....gonna go eat right now