| === chihchun_afk is now known as chihchun | ||
| RAOF | duflu_: I only use the mu:: shorthand in the implementation file of mir::udev::, everywhere else I use the full mir::udev:: namespace specifier. You'd prefer it if I used the full mir::udev:: specifier in the implementation file, too? | 04:03 |
|---|---|---|
| duflu_ | RAOF: No, there are two possible ways to avoid mentioning the namespace in the implementation. I'd prefer either of them :) | 04:05 |
| === duflu_ is now known as duflu | ||
| duflu | *to avoid repeating the namespace | 04:07 |
| didrocks | duflu: hey! tell me when you have some time for a chat on the new process (hangout I guess) | 07:29 |
| duflu | didrocks: Sorry, it seems I'm possibly tied up for the rest of the day (sabdfl) in other meetings | 07:30 |
| didrocks | duflu: ok, do you think you will have time tomorrow or let's wait for Monday? | 07:31 |
| duflu | didrocks: Tomorrow is OK AFAIK | 07:31 |
| didrocks | duflu: sounds ok. there are consequences btw, we need to have a lander for unity-mir (I think you won't land every release for it) and another one for qtubuntu/platform-api | 07:31 |
| didrocks | as they are linked to those landing, we need to clear that out | 07:31 |
| didrocks | kgunn: I was thinking about greyback for unity-mir, thoughts? | 07:32 |
| greyback | didrocks: count me in | 07:33 |
| didrocks | sweet! | 07:36 |
| didrocks | so, we need to find a victim for qtubuntu/platform-api ;) | 07:36 |
| kgunn | didrocks: thats ricmm_ | 07:45 |
| kgunn | who is in a mtng w me right now | 07:45 |
| didrocks | kgunn: ok, I'll send an email to sum that up | 07:46 |
| didrocks | thanks! | 07:46 |
| === chihchun is now known as chihchun_afk | ||
| === pete-woods is now known as pete-woods|posti | ||
| anpok_ | are there any rules of thumb in using lttng - should one avoid string outputs.. keep them short .. just do not core, and make the trace points as descriptive as possible.. | 11:49 |
| tvoss | anpok_, I think there are no strong rules, but the longer the name, the more data to store | 11:51 |
| tvoss | anpok_, I would think that limiting the scope with something mir::comp::event might make sense | 11:51 |
| === mlankhor1t is now known as mlankhorst | ||
| === pete-woods|posti is now known as pete-woods | ||
| tvoss | anpok_, thoughts? | 12:10 |
| === alan_g is now known as alan_g|afk | ||
| anpok_ | re | 12:35 |
| anpok_ | tvoss: thought about parameters .. i.e there is now a report that is meant to produce the selected egl configuration.. and does so by dumping each configuration attribute line by line | 12:36 |
| anpok_ | " [ name_of_the_attribute ] : <EGLInt value>" | 12:36 |
| tvoss | anpok_, okay, can you produce a single line out of that? we can selectively _not_ record that | 12:37 |
| anpok_ | sure | 12:37 |
| === ricmm_ is now known as ricmm | ||
| === alan_g|afk is now known as alan_g | ||
| alan_g | anpok_: there's no reason that every reporting interface should be implemented for lttng (or glog, or log, or...) | 13:40 |
| anpok_ | hm why not? | 13:45 |
| alan_g | lack of need | 13:47 |
| anpok_ | so you mean no further lttng report implementations are needed? | 13:52 |
| alan_g | When we need them we write them - or even a (hypothetical) http status monitor | 13:54 |
| tvoss | alan_g, I disagree. duflu's reporters are evaluated manually by parsing text output | 13:54 |
| tvoss | alan_g, I think those are perfect candidates for lttng report implementations | 13:54 |
| alan_g | tvoss: I don't know what "duflu's reporters" means, so I can't disagree that some more lttng reports are needed | 13:56 |
| tvoss | alan_g, duflu did quite some work on reporters recently for input latency and such | 13:56 |
| alan_g | But there's no reason to say "here's a reporting interface, therefore do an lttng implementation" | 13:57 |
| alan_g | But what you're saying is we have a timing report requirement on *some* report interfaces - therefore do an lttng implementation. Which is fine. | 13:58 |
| tvoss | alan_g, fair | 13:58 |
| alan_g | But there are too many sentences starting "But" | 13:58 |
| anpok_ | But you can continue like that | 13:59 |
| alan_g | But "a report that is meant to produce the selected egl configuration" doesn't beg for an lttng version | 14:00 |
| anpok_ | so you would be fine with leaving out certain report method calls? | 14:05 |
| alan_g | Sure, just implement the simplest thing that satisfies a need we have now. | 14:10 |
| === alan_g is now known as alan_g|afk | ||
| === alan_g|afk is now known as alan_g | ||
| === dandrader is now known as dandrader|afk | ||
| kdub | alan_g, i like the second suggestion in ~kdub/mir/db-optimize | 16:48 |
| alan_g | kdub: yw | 16:48 |
| fginther | tsdgeos, going back to 1269485. You don't want a VM do you, you want to run this on a touch device, right? | 17:08 |
| fginther | https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1269485 | 17:08 |
| ubot5 | Ubuntu bug 1269485 in Ubuntu CI Services "Create CI step for unity-mir tests" [Undecided,New] | 17:08 |
| tsdgeos | fginther: yes, device is cool | 17:15 |
| === dandrader|afk is now known as dandrader | ||
| === alan_g is now known as alan_g|EOD | ||
| === dandrader is now known as dandrader|afk | ||
| === dandrader|afk is now known as dandrader | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!