[00:40]  * thomi is back
[00:46] <RAOF> thomi: Oook.
[01:21] <duflu> RAOF: No luck with libdrm_radeon/mesa?
[01:22] <duflu> Hmm, tho it hasn't tried to build since the 24th
[01:33] <RAOF> duflu: Do you want to hit the rebuild button? Should work now.
[01:35] <duflu> RAOF: I hit /a? rebuild button. Not sure if it was the right one. Thanks
[01:35] <duflu> "a"
[01:55]  * duflu thinks it's awesome that he can click 3 build buttons and all 3 builds start immediately
[01:56] <duflu> kdub: Jenkins marked this done. Is it really? https://bugs.launchpad.net/mir/+bug/1130553
[02:11] <thomi> does anyone remember the secret key you need to push to stop grub booting?
[02:11] <RAOF> thomi: Madly mash shift.
[02:12]  * thomi is still trying to un-brick his laptop :(
[02:12] <RAOF> thomi: Although we *should* be marking your boot as failed, and automatically bringing up the grub prompt.
[02:12] <duflu> Mashing escape works too
[02:12] <thomi> doesnt seem to be shift....
[02:12] <thomi> and technically speaking, the boot works
[02:12] <thomi> time to try Escape
[02:13] <duflu> But you have to be fast with escape. Start mashing at the end of POST
[02:13] <RAOF> thomi: I believe that we decided that “has logged in to a session, or does a controlled shutdown” are the two criteria for determining whether a boot is successful.
[02:14] <thomi> oh, well that's not workng
[02:14] <thomi> RAOF: seems you need to hold the shift key, not just press it 0.O
[02:22] <thomi> robert_ancell: what should I do to disable u-s-c in lightdm.conf?
[02:22] <robert_ancell> thomi, uninstall u-s-c or edit /etc/lightdm/lightdm.conf.d/10-unity-system-compositor.config and quote out type=unity
[02:23] <robert_ancell> thomi, also check you don't have an old setting in /etc/lightdm/lightdm.conf - if so just remove it
[02:24]  * thomi crosses fingers and reboots
[02:25]  * kgunn waits with anticipation
[02:35] <thomi> well, I got my laptop back
[02:35] <thomi> but xmir totally breaks it for me
[02:35] <kgunn> laptop \o/
[02:35] <thomi> also, I realise that the mir stress tests break the server again. every time we get closer to enabling them for CI, something else breaks :-/
[02:39]  * duflu thought lightdm was meant to "fall back to xlocal" if things don't work
[02:39] <kgunn> olli: i notice you say reboot your system vs restart lightdm....did you experience issues w lightdm restart ?
[02:40] <robert_ancell> duflu, it did work, then it locked up and lightdm tried to get to failsafe X, but it was locked up by that point
[02:41] <kgunn> robert_ancell: ^ restart lightdm vs reboot ?
[02:41] <robert_ancell> kgunn, same difference
[02:41] <kgunn> robert_ancell: i thot so...just noticed olli referenced it today on irc & in his blog
[02:42] <RAOF> Hey, what's our idiom on server-side event-callbacks?
[02:42] <duflu> RAOF: Server side doesn't get callbacks ... ??
[02:43] <RAOF> duflu: I mean: an event occurs, and some server code needs to react to it. Do we not currently have any of that?
[02:44] <duflu> RAOF: It will be buried in the server classes (because they do have support for turning events into messages already). But I think what you mean by "server side callback" will be a virtual method to be overridden
[02:44]  * duflu is not helpful yet; goes to get coffee
[02:46] <robert_ancell> argh, C++! I copy the demo shell input handling code into u-s-c and it gives me obscure error messages
[02:48] <duflu> ??
[02:49] <RAOF> Looks like other parts of our code use a set_foo_callback() idiom.
[02:56] <kgunn> i just updated to the latest....and verified https://bugs.launchpad.net/mir/+bug/1194039
[02:57] <thomi> mir_stress causes the mir_demo_server to crash: https://bugs.launchpad.net/mir/+bug/1195089
[03:38] <duflu> Reboot. Wish me luck
[04:06] <duflu> RAOF: Ta. Mir is functional on raring again
[04:06] <duflu> via staging
[05:13] <didrocks> hey robert_ancell! around?
[05:14] <tvoss_> good morning all :)
[05:15] <didrocks> hey tvoss_
[05:18] <robert_ancell> didrocks, yep
[05:19] <didrocks> robert_ancell: was my email I sent yesterday understandable?
[05:20] <robert_ancell> didrocks, the big ol list of things to be done?
[05:20] <didrocks> robert_ancell: yep, and particularly the pending questions :)
[05:21] <thomi> morning tvoss_
[05:21] <thomi> morning didrocks
[05:21] <didrocks> hey thomi!
[05:21] <didrocks> thomi: moving house?
[05:22] <thomi> didrocks: yeah... have moved. Well, most things are still in boxes
[05:22] <didrocks> I imagine :)
[05:22] <didrocks> so you are working from a coffee shop or anything?
[05:23] <thomi> didrocks: no, working from home, I managed to un-pack my office. But I cannot find anything, so I end up buying new things, then find the box that I was looking for in the first place
[05:23] <thomi> like, I have no cups....
[05:23] <thomi> I'm sure they'll turn up somewhere
[05:24] <robert_ancell> didrocks, can you send me details on how you do integration tests with the unity stack
[05:24] <didrocks> thomi: argh, but no cups was a priority :-) Anyway, you never have enough of them :)
[05:24] <thomi> yeah
[05:24] <didrocks> robert_ancell: doing that now
[05:25] <didrocks> robert_ancell: on lightdm and ABI, any idea? (meanwhile I'm writing you that)
[05:25] <robert_ancell> ABI for?
[05:25] <didrocks> robert_ancell: see, RAOF told that the client ABI is stable, so platform-api and xmir will use that stable ABI, right?
[05:25] <didrocks> we don't need to worry too much about ABI stability, right?
[05:25] <robert_ancell> didrocks, yes
[05:26] <didrocks> so we can put everything in the same stack finally, I guess
[05:26] <robert_ancell> didrocks, though we want the integration tests to pick up if we stuff that up :)
[05:26] <didrocks> robert_ancell: sure ;)
[05:26] <didrocks> platform-api will dep on mir at some near point in the future, right?
[05:27] <robert_ancell> didrocks, as I understand it, it will depend on libmirclient
[05:27] <robert_ancell> racarr, correct?
[05:27] <didrocks> yeah, so, the stacks will be dependant as a whole :)
[05:27] <robert_ancell> though he's probably asleep :)
[05:27] <didrocks> robert_ancell: for lightdm/unity-greeter, in that case, do you want them in the mir stack or in another stack?
[05:27] <didrocks> I guess so :)
[05:28] <tvoss_> RAOF, good morning :)
[05:28] <robert_ancell> didrocks, I don't have a strong preference on the stacks. From my perspective you could lump them all into one stack and I'd be happy with that. As long as we don't slow down important bug fixes for one component
[05:28] <RAOF> tvoss_: Good morning.
[05:28] <robert_ancell> I have to go, but I'll be back in 2.5-3 hours
[05:28] <didrocks> robert_ancell: it doesn't slow down anything as long as any of them FTBFS or fail tests :)
[05:29] <didrocks> robert_ancell: ok, I'll send you about the integration tests then
[05:29] <robert_ancell> ta
[06:13] <tvoss> robert_ancell, duflu what are the remaining open vt bugs?
[06:14] <duflu> tvoss: Might be inaccurate, but https://bugs.launchpad.net/mir/+bugs?field.tag=vt
[06:15] <duflu> I think the medium one is actually the most annoying right now
[06:17] <tvoss> duflu, hmmm, I think that's the one making it difficult to fallback easily
[06:18] <duflu> tvoss: Well not having a terminal to log in to is a risk too
[06:18] <tvoss> duflu, that's what I mean
[06:19] <duflu> Right. So "expert fallback" = terminal. As opposed to fallback mode, which is X (when it works?)
[06:19] <tvoss> duflu, right
[06:19] <tvoss> duflu, that's what I mean
[06:28] <duflu> alf: Good morning. Bad news... https://bugs.launchpad.net/bugs/1195105
[06:29] <alf> duflu: Yeah, I saw that late yesterday, but thankfully it's a simple fix
[06:29] <duflu> alf: Cool. You saw it before the bug was logged?
[06:34] <alf> duflu: assigned it to myself
[06:35] <alf> duflu: (disconnected, may have lost some messages)
[06:35] <duflu> alf: No nothing missed. Thanks. What's the cause?
[06:37] <alf> duflu: Surface::flag_for_render() internals changed, so now one call to it is not enough to mark the surface as valid for rendering.
[06:38] <alf> duflu: if you need a temporary workaround just call it twice in render_surfaces
[06:39] <duflu> Oh. Server internals...
[06:59] <tvoss> RAOF, https://github.com/whot/libevdev
[07:00] <RAOF> Yah.
[07:00] <RAOF> Also in my G+ stream :)
[07:00]  * RAOF still needs to check about the libsynaptics situation.
[07:00] <RAOF> I don't think we're _particularly_ interested in libevdev, right? The Android stack already handles that.
[07:00] <RAOF> But we *are* interested in having touchpad support ☺
[07:05] <RAOF> Man, I wish C++ had a builtin string class.
[07:06] <RAOF> Strike that; I wish it had a builtin string *type*.
[07:06] <duflu> RAOF: You're asking for the C++ spec to grow further? :)
[07:07] <RAOF> Actually I'm basically asking for typeof("foo") == std::string.
[07:07] <RAOF> :)
[07:11] <duflu> RAOF: You can go: char foo[] = "foo"; int len = sizeof(foo) - 1;  :)
[07:12] <duflu> What more can you want from a string? ;)
[07:12] <mlankhorst> utf-8
[07:12] <duflu> mlankhorst: Yeah fair point
[07:13] <duflu> Though unicode is easier to deal with most of the time... wchat_t foo[] = L"foo";
[07:14] <duflu> *wchar_t
[07:14] <RAOF> wcat_t whiskers[]!
[07:15] <duflu> int longcat = (sizeof(whiskers) / sizeof(whiskers[0])) - 1
[07:17] <RAOF> Peppa pig!
[07:18] <didrocks> robert_ancell: once you are back: https://code.launchpad.net/~didrocks/lightdm/packaging-cleanup/+merge/171722
[07:22] <duflu> Ah, wchar_t can still be multibyte. But C++11 also has char32_t to rule them all
[07:23] <duflu> (except longcat who cannot be ruled)
[07:35] <tvoss> robert_ancell, hey there :) searching for the command line that invokes usc from lightdm
[07:35] <RAOF> src/seat-unity.c is what you want to be looking in.
[07:39] <tvoss> RAOF, that's lightdm, right?
[07:39] <RAOF> Right.
[07:40] <seb128> RAOF, hey
[07:40] <RAOF> seb128: Ho!
[07:40] <seb128> RAOF, how are you?
[07:41] <RAOF> I'm well. Hows about you?
[07:41] <seb128> I'm good thanks
[07:41] <seb128> RAOF, quick question for your ... did you guy test the new xorg which is getting ready for upload in saucy? does it has an possible impact on XMir or on work you are doing?
[07:41] <seb128> it seems like that stack is mostly ready for landing in saucy
[07:42] <seb128> but I want to make sure it's not going to create issues for you guys first
[07:43] <RAOF> It shouldn't, although I should check whether the input ABI changed.
[07:44] <seb128> RAOF, can you check tomorrow and give us a ack/nack?
[07:44] <mlankhorst> RAOF: just some repacking
[07:44] <RAOF> mlankhorst: Urgh, again?
[07:44] <mlankhorst> yeah someone loves their bitfields
[07:45] <RAOF> Ok. So I'll need to throw xf86-input-* into the Mir PPA until that's moved to 1.14.
[07:45] <mlankhorst> but a rebuild is enough for that
[07:45] <RAOF> Right
[07:46] <RAOF> Or, I guess, move xserver in the Mir PPA to 1.14; that should be fast.
[07:46] <mlankhorst> indeed :p
[07:46] <mlankhorst> and then just bump the video drivers to rebuild them
[07:47] <RAOF> Exactly.
[07:47] <RAOF> mlankhorst: I guess xf86-input-* built against 1.14 are in a PPA somewhere, right?
[07:48]  * duflu wonders how the Apple Magic Trackpad would go with Mir
[07:49] <mlankhorst> RAOF: canonical-x/x-staging is whats going to land
[07:50] <RAOF> duflu: Reasonably, but no tap-to-click etc.
[07:50] <RAOF> mlankhorst: Ta.
[07:50] <duflu> RAOF: I mean Mir android input, not X
[07:50] <RAOF> duflu: So did I.
[07:51] <duflu> Oh
[07:51] <duflu> I recall trying it on a Honeycomb tablet a while ago. Kind of worked...
[07:51] <RAOF> seb128: I'll move our PPA on to 1.14 tomorrow and give you the goahead.
[07:51] <seb128> RAOF, thanks
[08:13] <robert_ancell> RAOF, I put a work item for the 1.14 update in https://blueprints.launchpad.net/ubuntu/+spec/client-1303-mir-system-compositor
[08:17] <tvoss> robert_ancell, hey, looking at src/seat-unity.c. I would like to add options to enable reporting of the different mir components
[08:17] <tvoss> robert_ancell, question is: how do I access the settings as read from the per-seat config file?
[08:18] <robert_ancell> tvoss, not 100% sure what you mean, but you just need to call seat_get_*_property to get a property of a seat as set in the config
[08:20] <tvoss> robert_ancell, ah cool, so the usc executable has command line options to enable logging of internal operations, either to a log file or to lttng
[08:20] <tvoss> robert_ancell, for debugging purposes, it would be great if we could enable that functionality via the unity-seat config file, passing over the cl options to usc
[08:20] <robert_ancell> tvoss, I added "unity-compositor-command" which you can set to "unity-system-compositor --do-blah-blah-blah" to do stuff like that temporarily
[08:21] <tvoss> robert_ancell, ah cool, even better then :)
[08:21] <robert_ancell> tvoss, Ideally we should just set u-s-c to log stuff to stderr by default so we have baseline debugging
[08:22] <tvoss> robert_ancell, and stderr ends up in the usc.log, right?
[08:22] <robert_ancell> tvoss, ack
[08:28] <tvoss> robert_ancell, so something like unity-compositor-command="unity-system-compositor --glog --glog-stderrthreshold=0 --display_report_opt=log"
[08:28] <tvoss> in 10-unity-... .conf should work ...
[08:31] <robert_ancell> tvoss, yes
[08:31] <tvoss> robert_ancell, cool, trying now :)
[08:42] <didrocks> robert_ancell: so, I guess before daily releasing mir and unity-greeter to a PPA (so not blocking on integration tests nor the duplicated libraries in Mir), I just need your lightdm review, did I miss anything?
[08:43] <didrocks> robert_ancell: then, we can continue discussing with jibel if needed to clear up how to do the integration tests
[08:44] <robert_ancell> alf, I think the link is too flaky :(
[08:45] <robert_ancell> didrocks, otp, I'll get back to you.. which is the review? I thought I just did them all
[08:46] <didrocks> robert_ancell: https://code.launchpad.net/~didrocks/lightdm/packaging-cleanup/+merge/171722
[08:46] <didrocks> robert_ancell: fresh new one! :)
[08:51] <tvoss> RAOF, ping
[08:53] <RAOF> tvoss: pongity pong.
[09:02] <tvoss> robert_ancell, adding the command line makes the server not start, executable not found
[09:03] <robert_ancell> tvoss, can you paste me your config?
[09:04] <robert_ancell> tvoss, there is a nice regression test that tests this case, so it *should* work...
[09:04] <robert_ancell> didrocks, approved
[09:05] <didrocks> robert_ancell: thanks! I'm prepping the daily release machinery through the next ppa then!
[09:05] <robert_ancell> didrocks, I take it the man page change was intentional?
[09:05] <robert_ancell> You probably know groff better than me :)
[09:05] <didrocks> robert_ancell: yeah, it was an empty stenza (I saw it through lintian TBH :p)
[09:05] <tvoss> robert_ancell, unity-compositor-command="unity-system-compositor --glog --glog-stderrthreshold=0 --display_report_opt=log"
[09:06] <robert_ancell> hah! Your secret is out!
[09:06] <tvoss> I tried without ", too
[09:06] <didrocks> it is :)
[09:06] <robert_ancell> tvoss, no quotes
[09:06] <tvoss> robert_ancell, tried that, without luck :/
[09:06] <robert_ancell> tvoss, can I see the lightdm.log?
[09:07] <didrocks> robert_ancell: tell jibel and I when you want to discuss integration testing, we can do that at a time not too late for you :)
[09:07] <robert_ancell> didrocks, will do
[09:07] <tvoss> robert_ancell, don't have it handy, but it said that it tries to invoke the command line and then command not found
[09:08] <robert_ancell> didrocks, I still can't see where the tests are for unity - can you point me at what files actually do the tests?
[09:09] <didrocks> robert_ancell: lp:unity tests/autopilot/unity/*
[09:09] <robert_ancell> didrocks, ta
[09:09] <didrocks> yw :)
[09:10] <robert_ancell> tvoss, hmf. I'll try here
[09:11] <tvoss> that was fast
[09:18] <robert_ancell> tvoss, works for me - config http://paste.ubuntu.com/5804162/, lightdm log http://paste.ubuntu.com/5804163/
[09:20] <tvoss> robert_ancell, cool, sorry for the noise then :) mind pasting the usc.log, too?
[09:20] <robert_ancell> tvoss, there's nothing new in it, but I didn't set --display_report_opt=log - does it need that?
[09:21] <tvoss> robert_ancell, yup, that allows us to log anything going on with vt's inside the gbm module
[09:21] <tvoss> iirc
[09:21] <robert_ancell> tvoss, brb
[09:31] <tvoss> robert_ancell, win?
[09:32] <robert_ancell> tvoss, you gave me an invalid command line :)
[09:32] <robert_ancell> unity-compositor-command=unity-system-compositor --glog --glog-stderrthreshold=0 --display-report=log
[09:32] <robert_ancell> works
[09:32] <tvoss> ups :)
[09:32] <robert_ancell> log output - http://paste.ubuntu.com/5804187/
[09:32] <robert_ancell> then my VTs went crazy so I was sshing from my phone - real pain to try and type on those keyboards :)
[09:32] <tvoss> yeah
[09:33] <robert_ancell> tvoss, that what you expected to see?
[09:35] <tvoss> looks good, trying to tune the output to get information back to us in case of issues
[09:40] <tvoss> robert_ancell,
[09:40] <tvoss> robert_ancell, ^
[09:41] <robert_ancell> yep, we should have this stuff on by default
[09:43] <tvoss> robert_ancell, do you think we should enable it in the ppa by default?
[09:44] <robert_ancell> tvoss, yes, change the defaults in u-s-c to log things that wont affect performance by default
[09:44] <tvoss> robert_ancell, yup, I think we want display reporting enabled, including info. We can lower that over time
[09:46] <robert_ancell> yep
[09:47] <robert_ancell> tvoss, bug 1195227
[09:48] <tvoss> robert_ancell, thx
[09:59] <didrocks>  ah, mir trunk FTBFS on the ppa
[09:59] <didrocks> https://launchpadlibrarian.net/143539491/buildlog_ubuntu-saucy-i386.mir_0.0.6%2B13.10.20130627ubuntu.unity.next-0ubuntu1_FAILEDTOBUILD.txt.gz
[10:00] <didrocks> hum, hard to read with -j8
[10:01] <didrocks> (can be the parallel build making it failing as well)
[10:01] <tvoss> didrocks, yup
[10:01] <didrocks> tvoss: did you see anything else than parallel build which can be the cause here? I don't see any hint in the trace :/
[10:02] <seb128> didrocks, the error seems to be "cp: cannot create regular file '/build/buildd/mir-0.0.6+13.10.20130627ubuntu.unity.next/obj-i686-linux-gnu/doc/html/cppguide/styleguide.css': No such file or directory"
[10:02] <didrocks> seb128: waow, you have good eyes, couldn't see that one :p
[10:02] <tvoss> seb128, o/
[10:02] <seb128> ;-)
[10:02] <seb128> tvoss, hey ;-)
[10:03] <seb128> /usr/bin/cmake -E cmake_progress_report /build/buildd/mir-0.0.6+13.10.20130627ubuntu.unity.next/obj-i686-linux-gnu/CMakeFiles
[10:03] <seb128> Generating ../doc/html/cppguide/styleguide.css
[10:03] <seb128> cp /build/buildd/mir-0.0.6+13.10.20130627ubuntu.unity.next/guides/styleguide.css
[10:03] <seb128>  
[10:03] <seb128> seems to have a path mismatch there
[10:04] <didrocks> indeed
[10:04]  * seb128 let you guys debug the build system ;-)
[10:08] <didrocks> passing on other archs, I think it's a --parallel mismatch, I'll disable it for now unless some cmake gurus wants to ensure that it works, tvoss, do you know if Satoris would be interested?
[10:10] <tvoss> didrocks, might be :)
[10:12] <katie> tvoss, mpt do we have anything to discuss today?
[10:13] <katie> tvoss, everything on my list was covered yesterday
[10:17] <didrocks> tvoss: seb128: it passed with this rebuild FYI
[10:17] <seb128> didrocks, ok, so some sort of race in the build system
[10:17] <didrocks> yep, let's see once Satoris is around
[10:41] <tvoss> katie, likewise :)
[10:48]  * duflu -> dinner
[10:50] <tvoss> katie, ping
[11:01] <tvoss> hah!
[11:02] <katie> tvoss, pong
[11:12] <didrocks> tvoss: ah, more annoying tests failed on powerpc: https://launchpadlibrarian.net/143542002/buildlog_ubuntu-saucy-powerpc.mir_0.0.6%2B13.10.20130627ubuntu.unity.next-0ubuntu1_FAILEDTOBUILD.txt.gz
[11:12] <didrocks> tvoss: do you mind having a look?
[11:16] <tvoss> didrocks, C++ exception with description "GLPixelBuffer doesn't support big endian architectures" thrown in the test body.
[11:16] <didrocks> tvoss: so this test should be disable on powerpc I guess
[11:17] <didrocks> or we can declare no Mir on powerpc, but that will make the inclusion by default difficult…
[11:18] <tvoss> didrocks, can you file a bug please?
[11:19] <didrocks> tvoss: sure
[11:21] <didrocks> tvoss: https://bugs.launchpad.net/mir/+bug/1195260
[11:30] <didrocks> tvoss: other tests failure on armhf: https://launchpadlibrarian.net/143544949/buildlog_ubuntu-saucy-armhf.mir_0.0.6%2B13.10.20130627ubuntu.unity.next-0ubuntu1_FAILEDTOBUILD.txt.gz
[11:30]  * didrocks opens a bug
[11:31] <didrocks> it seems no valgrind?
[11:32] <tvoss> didrocks, why is this passing in the ppa?
[11:32] <didrocks> tvoss: passing?
[11:33] <tvoss> didrocks, building
[11:33] <didrocks> tvoss: daily release?
[11:33] <didrocks> as it's our goal
[11:34] <didrocks> and as we don't have integration tests for everything yet, we are using the next ppa first
[11:34] <didrocks> (and rightly as we need to settle down those issues first)
[11:34] <didrocks> tvoss: https://bugs.launchpad.net/mir/+bug/1195265 FYI
[11:43] <tvoss> didrocks, quick check: isn't valgrind in the build-deps?
[11:44] <didrocks> tvoss: no, I just added it and dput to the ppa
[11:44] <tvoss> didrocks, thx
[11:44] <didrocks> for a test build
[11:44] <didrocks> tvoss: I wonder what is pulling it for the other archs TBH
[11:44] <didrocks> but anyway, it's needed to be in the build-dep :p
[11:44] <didrocks> will see this build result
[12:35]  * 6JTAAX1W6 is incognite
[12:35] <tvoss> not anymore :)
[13:16] <cprofitt> hello all
[13:47] <didrocks> tvoss: do you have a minute? I think we need to check with the launchpad guys. It seems to me that the armhf build is blocked: https://launchpad.net/~ubuntu-unity/+archive/daily-build-next/+build/4751091
[13:47] <didrocks> (it's like that for 15 minutes)
[13:48] <didrocks> seems it's taking 0.04 sec on amd64 to pass :p
[14:05] <tvoss> alf, ping
[14:05] <alf> tvoss: pong
[14:06] <tvoss> alf, pm
[15:04] <kdub> good morning
[15:08] <hikiko> ssh: Could not resolve hostname bazaar.launchpad.net: No such file or directory
[15:08] <hikiko> i am getting this error :s
[15:08] <hikiko> does anyone has problems to push?
[15:12] <hikiko> fixed
[15:15] <kdub> reviews piling up!
[17:25] <racarr> Howdy
[17:30] <tvoss_> racarr, hey there :)
[17:30] <tvoss_> how goes?
[17:30] <tvoss_> kdub, you should have edit rights btw
[17:31] <kdub> ah, thanks
[17:37] <racarr> tvoss_: Root canalled about 20 minutes ago
[17:37] <racarr> so it goes pretty...ow
[17:37] <racarr> im assuming as some point thoughts will resume
[17:38] <tvoss_> man, root canal is ouch
[17:40] <racarr> tvoss_: S'ok. I'll distract myself XD
[17:40] <racarr> How goes on your end?
[17:48] <tvoss_> racarr, pretty good, got some stuff to finish for end of month
[17:48] <tvoss_> racarr, but all good
[17:51] <tvoss_> racarr, preparing some vegetarian chili :)
[17:51] <racarr> I should try making that...
[18:01] <greyback> racarr: owww, root canal, nasty
[18:06] <racarr> it really is pretty nasty business. I considered just waiting it out until little nano robots could clean my teeth with lasers
[18:06] <racarr> :p
[18:07] <racarr> greyback: How goes?
[18:07] <greyback> racarr: fine. No real time for Mir stuff today. But tomorrow will
[18:07] <greyback> be on it fully
[18:08] <greyback> racarr: any update for me?
[18:08] <racarr> greyback: Not really. will finish the session stuff today
[18:08] <racarr>  land my other branches
[18:08] <racarr> err, session authorier stuff
[18:08] <racarr> I realized today
[18:08] <greyback> racarr: ok cool. Yep I'd like to see that
[18:09] <racarr> missed the sync up with Katie.
[18:09] <racarr> but you should start talking to Katie
[18:09] <racarr> she did the surface management design
[18:09] <racarr> and there is lots there, including functional tests (some of which are in mir now)
[18:09] <greyback> racarr: yep, I've been reading her documents recently
[18:09] <racarr> which hypothetically one day should run on
[18:09] <racarr> unity/mir and that would be
[18:09] <racarr> awesome
[18:09] <greyback> +1
[18:09] <greyback> where are the functional tests?
[18:09] <racarr> letsseee
[18:10] <racarr> on a page that crashes firefox
[18:10] <racarr> *waits*
[18:11] <racarr> greyback: https://docs.google.com/a/canonical.com/document/d/1GtXBxUo1M2ya5-6Um-pJ2bhLM-tXYMXDaZvEgr6edMg/edit
[18:11] <racarr> I guess they might be out of date to some of the recent
[18:11] <racarr> design refactoring
[18:11] <racarr> XD
[18:13] <greyback> racarr: then we'd best get them updated. These look very useful, and I'll automate them asap
[18:13] <racarr> there is
[18:14] <racarr> some cucumber code hanging around in mir...weeeeeeeeeeeeeeeeeeeeee
[18:14] <racarr> yeah
[18:14] <racarr> we should both talk to katie next week
[18:14] <racarr> and then figure out how to get some of them running on unity/mir combined
[18:15] <greyback> racarr: cucumber? When did ppl start using that?
[18:16] <greyback> +1
[18:16] <racarr> greyback: Me and Katie did! in december
[18:16] <racarr> :p
[18:16] <racarr> Katie and I *italics*
[18:16] <racarr> uh
[18:16] <greyback> stop taking all the credit :)
[18:17] <greyback> I'm not a big fan of the abstraction of cucumber in general, but for specific use-cases it will do I guess
[18:17] <greyback> it does make it easier for non-coders to write tests for us
[18:17] <racarr> I have
[18:17] <racarr> mixed opinions
[18:18] <racarr> Cucumber definitely isn't ideal
[18:18] <racarr> lots of sort of things are difficult to express
[18:18] <racarr> I havent thought about cucumber in probably 2 months so it's a little difficult to recall exactly which ones :p
[18:19] <greyback> :)
[18:19] <greyback> no worries, I was just curious
[18:19] <greyback> racarr: It's well past my EOD, gotta go
[18:19] <greyback> hope you have plenty of pain-killers and have a nice easy day :)
[18:20] <racarr> cya
[20:01] <thomi> morning all
[20:04] <racarr> Morning
[20:16] <bregma> racarr, regarding #1194075 (the, uh, embedded cucumber problem), would be be possible to just rewrite the session_manager_steps.cpp tests to use GTest directly instead, so we could simply drop the cucumber?
[20:20] <bschaefer> while running xmir, is anyone noticing ~20-30 seconds where everything hangs? Usually brought on by compiling...but sometimes not
[20:32] <racarr> bregma: There are grand plans for cucumber I guess, the single tet could be rewritten but there is not much point
[20:32] <racarr> if it is actually blocking anyone I think just remove it from the tree
[20:33] <bregma> racarr, it's blocking landing in Ubuntu
[20:34] <racarr> Really?
[20:34] <racarr> Why can't we land in ubuntu with cucumber-cpp embedded
[20:34] <racarr> as long as we are following the licensing
[20:42] <racarr> kdub: Ok I see it is failing, will look around for a bit
[20:42] <kdub> thanks
[20:43] <racarr> kdub: Why all this file synchronization stuff
[20:43] <racarr> isn't it satisfied by
[20:43] <racarr> InputTestingServerConfiguration::wait_until_client_appearas
[20:43] <racarr> ?
[20:44] <kdub> well, that will look on the server side for the client creation
[20:44] <kdub> but we need to wait until after the client has registered its handler
[20:44] <racarr> no
[20:44] <racarr> you can register the handler in the connected callback
[20:45] <racarr> and the client input thread wont be started until after this finishes
[20:45] <racarr> the server will send the first event over the pipe, and wait for this to happen before sending any more
[20:45] <racarr> the thing is the way the handler is being registered now
[20:45] <racarr> the thread can be started and read an event
[20:45] <racarr> before the handler is registered, so it just discards it
[20:45] <racarr> the problem in this test though is on the server side (
[20:45] <racarr> :(
[20:46] <racarr> you can see with MIR_SERVER_LEGACY_INPUT_REPORT=log
[20:46] <kdub> ah... all these secret switches :)
[20:46] <racarr> well they are in --help to be fair :p
[20:47] <kdub> haha, yeah
[20:47] <kdub> well, its somewhere to start then
[20:47] <racarr> kdub: Is it possible
[20:47] <racarr> I am still trying to sort out what has happened all in all
[20:47] <racarr> perhaps because of the way size comes from the buffer stream
[20:48] <racarr> something has changed there?
[20:48] <racarr> I dunno...it says it is dropping the vent because there is no touched window (you can see this in InputDispatcher.cpp)
[20:48] <racarr> but it looks like ms::SurfaceStack::for_each basically works the same way
[20:48] <racarr> so that it m ust have to do with the handles
[20:48] <racarr> when I say must I mean maybe
[20:52] <kdub> hmm, ok
[20:52] <kdub> new places to look at least :)
[20:55] <racarr> kdub: ill research some more too
[21:01]  * robert_ancell -> breakfast
[21:03] <racarr> robert_ancell: ok. 1-1 later?
[21:12] <kgunn> racarr: how you feelin' ?
[21:21] <robert_ancell> racarr, sorry, can do now
[21:29] <racarr> kgunn: Not so bad :)
[21:30] <kgunn> racarr: glad to hear it....ironically...my daughter is on the couch, post wisdom teeth removal (she had 6...and yes...the more you have the more you pay)
[21:31] <robert_ancell> racarr, lp:~robert-ancell/unity-system-compositor/keyboard
[21:38] <kdub> racarr, any insights on that branch?  i've gotten lost in the input stack
[21:40] <racarr> kgunn: Oww
[21:41] <racarr> kdub: Not yet -.-
[21:54] <kdub> racarr, thanks for looking.. . happily I did this in git, so I'll just bisect until I see what happened
[22:36] <xnox> Are you interested in dual-screen bugs where output is not mirrored across dvi and hdmi and there are significant differences?
[22:37] <xnox> also it seems like software rendering + xmir + unity, is faster than hw accel + xmir + unity.
[23:48] <RAOF> xnox: I'm interested in hearing how you can get into a situation where output is not mirrored!
[23:49] <thomi> RAOF: got a second?
[23:49] <thomi> RAOF: I have some more information regarding my xmir i915 issue
[23:49] <RAOF> Oooh.
[23:50] <RAOF> I therefore have a second.
[23:50] <thomi> RAOF: http://paste.ubuntu.com/5806320/
[23:50] <thomi> that's dmesg
[23:50] <thomi> look at thge last 3 lines
[23:51] <thomi> the contents of that file in /sys coming up....
[23:52] <thomi> RAOF: http://paste.ubuntu.com/5806322/
[23:52] <RAOF> Right. We've hung the GPU, possibly because of the plymouth segv, possibly *causing* the plymouth segv
[23:53] <thomi> Talk to me like I'm stupid - what's plymouth?
[23:53] <RAOF> The boot splash, input multiplexer thing.
[23:53] <thomi> ahh ok
[23:53] <thomi> anything else I can grab for you while i'm logged in?
[23:55] <RAOF> thomi: /var/log/lightdm/* would be nice.
[23:56] <thomi> lightdm.log: http://paste.ubuntu.com/5806327/
[23:57] <thomi> u-s-c log: http://paste.ubuntu.com/5806328/
[23:58] <thomi> RAOF: are the x-* logs of any use?
[23:58] <RAOF> Not really, no.
[23:59] <thomi> ok
[23:59] <thomi> I scanned them and didn't see anything that stood out
[23:59] <RAOF> Failed to set the current VT mode?
[23:59] <RAOF> robert_ancell: Hey, how would you feel about using CLOCK_MONOTONIC timestamps in the lightdm logs?