<span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; "><div>MINUTES: OE-TSC meeting 30-Jun-2011</div><div><br></div><div>Attending: Mark, Koen, Tom</div><div>Guest: Richard</div>
<div>Notes: Jefro</div><div><br></div><div>Agenda & Proceedings:</div><div><br></div><div>01) choose a meeting chair</div><div><br></div><div>Jefro</div><div><br></div><div>02) new topics</div><div><br></div><div> a) libc locale split mess, why did those patches get merged, especially considering the outcome of last weeks meeting about core files. (koen)</div>
<div><br></div><div>RP: locale stuff was a bit of a disaster, review/test process had some issues</div><div>need to make warnings more visible and improve bitbake logging</div><div>should really log all console output to a logfile for example</div>
<div> </div><div>b) turning insane.bbclass back on (koen)</div><div><br></div><div>not a thursday/friday before a long us weekend change</div><div>requires some warning, as things will break - need help from community</div>
<div>--> move discussion to oe-core mailing list, tentative date July 11</div><div><br></div><div>c) Rein Memory consumption of bitbake. (khem)</div><div><br></div><div>needs someone with the time/skill to work on it - continue</div>
<div><br></div><div>03) action items from last week</div><div><br></div><div> --> patches appearing on oe-dev, khem to send email regarding "put stuff in meta-oe"</div><div>no update</div><div><br></div><div>
05) Status updates</div><div> - elections - ongoing</div><div> - oe-core</div><div> - bsp guidelines</div><div> - metadata layer splitting</div><div> - infrastructure</div><div><br></div><div>Raw Transcript:</div>
<div><br></div><div>(12:58:50 PM) Jefro: 2 minute warning. I have added agenda items from Koen and Khem, anyone else? Who's here?</div><div>(12:59:02 PM) koen: aye</div><div>(12:59:07 PM) Tartarus: pong</div><div>(12:59:19 PM) ***fray is here now</div>
<div>(12:59:30 PM) Jefro: (is 3 members a quorum now?)</div><div>(1:00:11 PM) ***RP__ is here</div><div>(1:00:14 PM) Jefro: if not, lively discussion is always an option. Khem sent an apology - he can't make it today.</div>
<div>(1:00:27 PM) ***fray notes he will not be able to make next weeks meeting</div><div>(1:00:28 PM) RP__: Jefro: We regard it with bemusement :)</div><div>(1:00:44 PM) Tartarus: Shall we begin then?</div><div>(1:00:52 PM) Jefro: sure - agenda is at <a href="http://pastebin.com/mEDd7nm4" target="_blank" style="color: rgb(0, 0, 204); ">http://pastebin.com/mEDd7nm4</a></div>
<div>(1:01:28 PM) Jefro: ALERT - I need to leave in about 45 minutes, but someone can send me the transcript of the lastbit if we are still going by then</div><div>(1:01:31 PM) RP__: koen: I think that sums it up :)</div>
<div>(1:01:49 PM) Jefro: RP__ :)</div><div>(1:02:53 PM) Jefro: quiet today... too quiet. I'll take the driver's seat if no one wants it.</div><div>(1:03:01 PM) koen: khem says he has no updated on his AR</div><div>
(1:03:07 PM) koen: (before I forget to mention that)</div><div>(1:03:14 PM) RP__: Jefro: go for it :)</div><div>(1:03:16 PM) Jefro: koen thanks</div><div>(1:03:21 PM) ***Jefro notes Jefro as meeting chair</div><div>(1:03:49 PM) Jefro: there were three new topics, two from koen - perhaps he had better just launch into it</div>
<div>(1:03:59 PM) Tartarus: no new topics here</div><div>(1:04:27 PM) fray: nothing here</div><div>(1:04:49 PM) RP__: nothing here</div><div>(1:04:59 PM) RP__: I have some comments on Koen's topics though :)</div><div>
(1:05:15 PM) Jefro: I expected nothing less</div><div>(1:05:19 PM) koen: so before we burn RP__ at the stake, let's him say his last words</div><div>(1:05:20 PM) Jefro: 2a: libc locale splitmess</div><div>(1:05:44 PM) RP__: heh :)</div>
<div>(1:06:13 PM) RP__: The locale stuff was a bit of a disaster, no question about that :(</div><div>(1:06:39 PM) RP__: I don't quite think it follows from last weeks problem though as these were two different circumstances</div>
<div>(1:07:10 PM) RP__: In this case we were on v3 of the patch and at least four people had looked at the patches including myself and Phil</div><div>(1:07:50 PM) fray: ya, there was definite review..</div><div>(1:07:56 PM) RP__: There was stuff people should have spotted and didn't</div>
<div>(1:07:59 PM) koen: but was there testing?</div><div>(1:08:10 PM) RP__: koen: I did have it in my testing trees off and on</div><div>(1:08:29 PM) koen: an incremental image build would have shown the shlib renaming problem at least</div>
<div>(1:08:45 PM) RP__: koen: I was doing builds from scratch and profiling at the same time :/</div><div>(1:08:48 PM) fray: I think the incremental image may have been a gap in the testing..</div><div>(1:08:51 PM) koen: a look at the buildlog would have shown all the -dbg misses</div>
<div>(1:09:21 PM) RP__: koen: I know, I got distracted by other build issues like performance which I'm still struggling to find a regression on</div><div>(1:09:29 PM) koen: unpackaged file are starting to become a pet peeve for me :)</div>
<div>(1:09:39 PM) RP__: Somewhere we took a 10% hit and I can't explain how</div><div>(1:09:48 PM) RP__: koen: one topic at a time ;-)</div><div>(1:09:50 PM) fray: koen (re unpackaged files) I agree.. it's getting worse</div>
<div>(1:10:36 PM) RP__: I did send some rather frank emails to the Yocto team about the locale thing asking people to learn lessons from it although the mail I sent was to an internal list</div><div>(1:11:26 PM) koen: so another set of lessons learned?</div>
<div>(1:11:31 PM) RP__: So all in all, I am resolving to do better and have asked the team to do better too</div><div>(1:11:33 PM) koen: if yes, let's move to 2b</div><div>(1:11:53 PM) RP__: koen: yes. I'd also like to see what we can do to make certain warnings more obvious</div>
<div>(1:11:56 PM) Jefro: any action items from 2a other than be more careful nexttime?</div><div>(1:11:58 PM) RP__: which leads us to 2b</div><div>(1:12:19 PM) RP__: Jefro: I think the main thing is to make warnings more visible and improve bitbake logging</div>
<div>(1:12:30 PM) RP__: we should really log all console output to a logfile for example</div><div>(1:12:50 PM) RP__: in fact someone should file that bug</div><div>(1:12:54 PM) Jefro: good point - I am very used to redirecting it to a log</div>
<div>(1:13:09 PM) koen: in .dev we log most qa errors to a file</div><div>(1:13:19 PM) RP__: koen: I want the whole console output</div><div>(1:13:36 PM) ***RP__ is sick of hearing complaints about that</div><div>(1:14:33 PM) koen: but back to 2b, can we turn them back on ASAP?</div>
<div>(1:15:02 PM) koen: basic things like the kernel ships buildarch files</div><div>(1:15:06 PM) koen: -s</div><div>(1:15:07 PM) fray: my only concern is today is Thursday and it might be better to do it Monday..</div><div>
(1:15:13 PM) fray: otherwise, yes we need to</div><div>(1:15:31 PM) Tartarus: Yes, agree with fray</div><div>(1:15:39 PM) Tartarus: it's not a thursday/friday before a long us weekend change</div><div>(1:16:05 PM) Tartarus: s/us/US/</div>
<div>(1:16:19 PM) fray: even Monday may be bad due to July 4th (and July 1st being Canada day)</div><div>(1:17:00 PM) Tartarus: yeah</div><div>(1:17:04 PM) Tartarus: Tuesday</div><div>(1:17:19 PM) Tartarus: Unless RP__ is gonna get a jump on fixing all of the QA issues too :)</div>
<div>(1:17:19 PM) RP__: koen: What I don't want to do is turn that stuff back on and have the yocto autobuilder go red across the board</div><div>(1:17:26 PM) fray: (we should likely send out a warning that things are going to break)</div>
<div>(1:17:58 PM) fray: RP__ is there anyone that will go in and fix them as part of the patch to reenable it though? with the holiday and other things, I'm not sure there is this particular moment..</div><div>(1:17:59 PM) RP__: This does need a process stepping through and ensureing oe-core at least is clean, then turning them on</div>
<div>(1:17:59 PM) koen: RP__: people aren't fixing the problems right now, seeing it go red might trigger people into action</div><div>(1:18:12 PM) RP__: koen: I'd at least like to warn people</div><div>(1:18:21 PM) Tartarus: RP__: how much warning?</div>
<div>(1:18:22 PM) fray: yes, we need to warn folks</div><div>(1:18:29 PM) Tartarus: warn today, do it Tuesday?</div><div>(1:18:39 PM) koen: but I don't want to wait till everything has been fixed</div><div>(1:18:43 PM) Tartarus: I'm with koen, this needs to cause things to go red so people fix it</div>
<div>(1:18:48 PM) ***koen doesn't agree with it being turned off to start with</div><div>(1:19:01 PM) RP__: koen: I'm not sure why that happened either</div><div>(1:19:01 PM) koen: but giving people a week time can't hurt</div>
<div>(1:19:20 PM) RP__: Its also a question of who is going to fix this stuff</div><div>(1:19:29 PM) Tartarus: RP__, everyone once it goes red</div><div>(1:19:35 PM) Tartarus: Most stuff has a fix in oe.dev already I bet</div>
<div>(1:19:42 PM) RP__: I would point out the Yocto team is actually maxed out at the moment and they do not have the bandwith this second</div><div>(1:20:04 PM) RP__: heck, I'm maxed out trying to review all the patches on the mailing list</div>
<div>(1:20:22 PM) RP__: I'm just about getting to grips with the week Saul had out :(</div><div>(1:20:23 PM) Tartarus: RP__: That "the team" is maxxed out on other stuff speaks to koen (and my) concern</div>
<div>(1:20:32 PM) Tartarus: That it will take it being broken for people to get around to fixing it</div><div>(1:20:43 PM) koen: option b) is to remove "high quality" from the website and propoganda</div><div>(1:21:02 PM) RP__: koen: just quit with that stuff please ;-)</div>
<div>(1:21:09 PM) koen: ok, ok</div><div>(1:21:16 PM) RP__: I'm trying to would out a reasonable way we can do this</div><div>(1:21:20 PM) RP__: which doesn't piss people off</div><div>(1:21:54 PM) RP__: s/would/work/</div>
<div>(1:21:55 PM) Tartarus: Well, lets see</div><div>(1:22:30 PM) RP__: I would like a little time to figure out how bad things are with those options turned on</div><div>(1:22:39 PM) RP__: We don't have an instant need to change this</div>
<div>(1:22:57 PM) koen: be glad the initial set doesn't include the LDFLAGS check :)</div><div>(1:23:26 PM) Tartarus: RP__: How about we change it on the 11th of july?</div><div>(1:23:32 PM) Tartarus: And just look at any current log for how bad it's going to be</div>
<div>(1:23:44 PM) RP__: Tartarus: That works</div><div>(1:24:04 PM) koen: if you ask nicely darren might fix kernel.bbclass before the 11th</div><div>(1:24:18 PM) ***RP__ is going to have mutiny on his hands or needs to sort this himself and take a weekend to do it :/</div>
<div>(1:24:40 PM) RP__: but I agree we need to do it</div><div>(1:24:40 PM) koen: I think it's more than a weekends work</div><div>(1:25:01 PM) RP__: koen: I don't have any more time I can physically give</div><div>
(1:25:09 PM) koen: I know</div><div>(1:25:14 PM) RP__: I'm supposed to be doing other things with my weekends too :(</div><div>(1:25:32 PM) koen: I'm just pointing out it's a big undertaking, but one that needs to get done</div>
<div>(1:25:44 PM) koen: and it's not something we want you to waste your weekends on</div><div>(1:25:47 PM) Jefro: is there anyone else in the community who can do it?</div><div>(1:26:07 PM) fray: I think the warning needs to include a plee from the community for help</div>
<div>(1:26:16 PM) fray: plea even</div><div>(1:26:19 PM) RP__: it does</div><div>(1:26:57 PM) RP__: It doesn't help I'm not doing too well from a medical PoV atm</div><div>(1:27:17 PM) koen: working weekends won't help with that</div>
<div>(1:28:00 PM) RP__: koen: It just means I don't do other things</div><div>(1:28:37 PM) RP__: Anyhow, my point is there are implications if we just make the change. I think we've agreed to give some runway and there are ways of sorting things out within that</div>
<div>(1:28:50 PM) koen: any volunteers who aren't named RP to write the danger, will robinson note?</div><div>(1:28:59 PM) Jefro: RP__ needs no excuses here, I don't think. it's just a matter of finding resources.</div>
<div>(1:29:01 PM) RP__: From a Yocto standpoint, multilib is a big worry atm btw</div><div>(1:30:42 PM) Tartarus: Well, lets see</div><div>(1:30:43 PM) koen: shall we move this discussion to the oe-core ml?</div><div>(1:30:49 PM) Tartarus: koen, just how horribly overloaded are you atm? :)</div>
<div>(1:30:54 PM) Tartarus: And that too</div><div>(1:30:56 PM) RP__: I think so</div><div>(1:31:39 PM) koen: Tartarus: spending a week at UK office next week doing only powervr stuff</div><div>(1:32:09 PM) ***koen foresees a backlog</div>
<div>(1:32:14 PM) Tartarus: Well, ok, we'll ask for folks to turn it on locally and start producing patches</div><div>(1:32:23 PM) Tartarus: See if we can't get some stuff tackled before the 11th</div><div>(1:32:26 PM) ***koen has it turned on already :)</div>
<div>(1:32:48 PM) koen: ready to move to 2c?</div><div>(1:33:18 PM) ***Jefro notes discussion to move to ml</div><div>(1:33:30 PM) Jefro: moving to 2c - was hoping khem would be here by now</div><div>(1:33:45 PM) Tartarus: Well, I think we can manage</div>
<div>(1:33:46 PM) Jefro: he wrote a letter to the tsc list about this issue. </div><div>(1:33:53 PM) Tartarus: and it sounds like RP is aware of both perf and memory issues</div><div>(1:33:53 PM) koen: he entered a 'short' meeting 20 minutes ago</div>
<div>(1:33:56 PM) fray: for 2c, I wonder if the per-file dependencies are contributing to the bloat.. this and some of the other run-time dependency info can likely be flushed out to a file and reloaded only when needed..</div>
<div>(1:33:58 PM) Tartarus: time to bust out some free time and smem</div><div>(1:34:33 PM) ***RP__ is aware of the memory issue</div><div>(1:34:37 PM) Tartarus: I know chris larson has done some what's taking so much memory profiling in the past and I think that lead to a few minor changes too</div>
<div>(1:34:41 PM) RP__: it just needs someone with the time/skill to work on it</div><div>(1:34:46 PM) koen: khem and I worry that 1k recipes need 600MB already</div><div>(1:34:49 PM) fray: would be nice to have an idea of all of the variables that are contributing to the memory usage.. then we can devise a strategy...</div>
<div>(1:34:51 PM) Tartarus: And it's a small set of folks with the skills :(</div><div>(1:34:53 PM) koen: what happens with 8k recipes?</div><div>(1:35:05 PM) RP__: koen: depends whether its the recipes causing the problem</div>
<div>(1:35:36 PM) RP__: Tartarus: at present I've seen some decidedly odd behaviour with build times which I'm trying to get to the bottom of</div><div>(1:35:48 PM) RP__: This 10% regression I mentioned.</div><div>
(1:36:17 PM) RP__: but I can only work on so much at once and the people I've asked to try and find it can't</div><div>(1:36:33 PM) koen: so it's known and scheduled to be looked at</div><div>(1:37:02 PM) RP__: well, the build time issue is. We need to officially add memory usage to the Yocto list</div>
<div>(1:37:11 PM) RP__: and find someone with time to work on it</div><div>(1:39:49 PM) Tartarus: So, I think that's that</div><div>(1:40:14 PM) Tartarus: We already had a quick update on khem's AIs and that was all there was for AIs I think</div>
<div>(1:40:28 PM) Jefro: on to status?</div><div>(1:40:32 PM) Tartarus: Yeap</div><div>(1:40:42 PM) Tartarus: Anything we haven't covered already really via 2a/b/c</div><div>(1:41:06 PM) Jefro: no word on infrastructure - I have planned a meeting with LF to discuss status on that, will report back next week</div>
<div>(1:41:52 PM) koen: elections seems to be "working"</div><div>(1:42:28 PM) Jefro: any other status not covered above on oe-core, metadata splitting...</div><div>(1:42:29 PM) koen: the usual apathy</div><div>
(1:43:02 PM) fray: I think we're good</div><div>(1:43:17 PM) Jefro: cool - meeting adjourned?</div><div>(1:43:24 PM) Tartarus: seconded</div><div>(1:43:42 PM) Jefro: awesome. see yall</div></span><br>-- <br>Jeff Osier-Mixon <a href="http://jefro.net/blog" target="_blank">http://jefro.net/blog</a><div>
Yocto Project Community Manager @Intel <a href="http://yoctoproject.org" target="_blank">http://yoctoproject.org</a></div><br>