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