=== ValicekB_ is now known as ValicekB === chihchun_afk is now known as chihchun === tvoss is now known as tvoss|test === tvoss|test is now known as tvoss === willcooke_ is now known as willcooke [08:22] alf_: duflu: can we land https://code.launchpad.net/~afrantzis/mir/fix-1350207-unresponsive-clients/+merge/233934? [08:23] anpok_: Kind of, maybe, no. I think a few of us want a little cleanup first [08:24] ... then after 7.2.. [08:28] s/2/3 [08:30] anpok_: Does anything need fixing in 0.7.3? Or is it just another practice? [08:33] another practice, the unresponsive clients fix would be nice though.. [08:33] there were rumors that someone already achieved that somehow [08:35] anpok_: Yeah it's theoretically simple to trigger [08:40] duflu: anpok_: I've pushed an update === chihchun is now known as chihchun_afk === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader === greyback__ is now known as greyback [14:05] if Alan on holidays? [14:06] s/if/is [14:06] * dandrader needs some help google protobuf [14:07] *help with [14:09] dandrader, yes he is [14:10] :( [14:12] doesn't hurt to ask though :) === cyphermox_ is now known as cyphermox [14:34] I wonder how do I debug protobuf communication [14:35] client calls a server method, server replies, but client doesn't seem to get any content back, although the call seemed successful. later calls on the same method work though [14:49] dandrader, we have MIR_SERVER_MSG_PROCESSOR_REPORT=log [14:49] and MIR_SERVER_SESSION_MEDIATOR_REPORT=log for the server [14:50] more likely than not, the call triggered an exception within mir, which was reported back as an error string to the client [14:51] I'm using mir's "custom messages" feature though. ie, taking the protobuf channel and sending my own messages [14:51] kdub_, ^ [14:51] for the clipboard copy() and paste() more specifically [14:51] kdub_, does that make any difference? [14:57] dandrader, yeah, then I don't know that it would work === chihchun_afk is now known as chihchun === dandrader is now known as dandrader|lunch === dandrader|lunch is now known as dandrader === dandrader is now known as dandrader|lunch === dandrader|lunch is now known as dandrader [17:14] kdub_, where is mir log going to nowadays? [17:14] stdout [17:15] or some reports can go to a lttng trace [17:16] kdub_, but those MIR_*_REPORT=log you mentioned earlier should go to stdout, right? [17:16] dandrader, right, the 'log' setting will go to stdout [17:17] yeah, I see them in .cache/upstart/unity8.log now [17:19] and they're no good for debugging custom messages :( === tvoss is now known as tvoss|test === tvoss|test is now known as tvoss === dandrader is now known as dandrader|afk [19:20] AlbertA, kdub_, racarr: when you set the build type to coverage [19:20] then build, run tests and run make coverage and make coverage-xml .. [19:20] do you then get reasonable data in coverage.xml? [19:21] i can try it out [19:24] anpok: no idea... [19:24] :) [19:26] https://jenkins.qa.ubuntu.com/job/mir-utopic-amd64-ci/ [19:26] hmm [19:27] build history looks strange [19:36] kdub_: thx, figured it out.. it seems like we relied on an old gcovr version that maybe ignored the -r parameter [19:37] and the ppa in ca that provided it got updated .. hm at least after some changes it works locally again === LockeAnarchist- is now known as LockeAnarchist [19:50] kgunn__: ping my lrt test has the ui frozen. the ui is totally unusable. who can I talk to about logs to check to determine the problem? [19:51] kgunn__: I have this in logcat http://pastebin.ubuntu.com/8360154/ maybe a thermal issue on the n4. [19:53] robotfuel: can you run top ? [19:53] see who's active...almost certainly someone is pegging [19:54] ChickenCutlass: ^ do you know anything about thermal sensor? if we've tuned it etc ? [19:54] robotfuel: btw, n4 is dead to ChickenCutlass :) [19:54] kgunn__: http://pastebin.ubuntu.com/8360176/ [19:55] ChickenCutlass: ...or do you know anyone who knows about thermal sensor...e.g. should the system recover from a thermal event like this ? [19:56] robotfuel: huh, i suppose the event basically stopped all the threads === LockeAnarchist- is now known as LockeAnarchist === chihchun is now known as chihchun_afk [20:07] kgunn__, reading back log [20:32] kgunn__, robotfuel seems like system-settings is eating memory like crazy [20:33] 25.8% according to top [20:33] tvoss: that's the screen it's frozen on [20:33] robotfuel: yeah...but he's saying memory consumed.... [20:33] not cpu [20:34] that's huge [20:34] ah right I wasn't looking at that. [20:45] oh yeah apt-cache-ng...this is some good stuff [20:45] cacher* [20:45] between sbuild and [20:45] new machine with massive ram, I feel my days of compiling woes [20:45] are finally over [20:51] woah [20:51] I just got the new google docs [20:51] its so shocking I cant even remember what document I needed now. === dandrader|afk is now known as dandrader [21:55] lol