## Template for LP Production Meeting logs. Just paste xchat log below and the format IRC line will take care of formatting correctly #format IRC #startmeeting Meeting started at 10:00. The chair is matsubara. Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] Welcome to this week's Launchpad Production Meeting. For the next 45 minutes or so, we'll be coordinating the resolution of specific Launchpad bugs and issues. [TOPIC] Roll Call New Topic: Roll Call Not on the Launchpad Dev team? Welcome! Come "me" with the rest of us! me me me me * Ursinha-afk is now known as Ursinha ni! me Ursinha: and i thought you're doing your telepathic typing trick again... intellectronica, hehe Chex, hi matsubara: hello ok, so we're missing stub and henning/danilo me hi danilos :-) matsubara: no you are not :) so, from now on, you'll be attending the prod meeting, right? matsubara: well, not necessarily, let's see :) ok, let's move on then [TOPIC] Agenda matsubara: but soon I will be replacing henninge as our QA contact New Topic: Agenda * Actions from last meeting * Oops report & Critical Bugs & Broken scripts * Operations report (mthaddon/Chex/spm/mbarnett) * DBA report (stub) * Proposed items danilos, ok [TOPIC] * Actions from last meeting New Topic: * Actions from last meeting * cprov to follow up on bug 413749 * stub to investigate garbo-hourly failure after spm adjusted script checking to 12h * sinzui to poke barry about ExpatError OOPSes (bug 403606) * danilos, Ursinha and matsubara to discuss oops summaries split per team Bug 413749 on http://launchpad.net/bugs/413749 is private Launchpad bug 403606 in launchpad-registry "ExpatError errors should be handled to not generate the OOPSes" [High,Triaged] https://launchpad.net/bugs/403606 ok, I know that stub replied to the garbo-hourly failure email, so I think that's done matsubara: we kind of did that, flacoste is involved as well, and it's all on track I'd say :) danilos, right. if you have more suggestions let me know barry, hi! sinzui is on unavailable I believe * barry has some thoughts about the expat errors matsubara: hi! barry, what's up with those expat errors? matsubara: I did reply on 413749 as well, needs discussion, though. thanks cprov * noodles775 has quit (Read error: 110 (Connection timed out)) matsubara, the one with the expaterrors I'd bring in the oops section * noodles775_ (n=miken@f053074246.adsl.alicedsl.de) has joined #launchpad-meeting matsubara: well, some more investigation might be warranted, but they are intermittent and i've always chalked them up to problems with xmlrpc. i believe they can be safely ignored though because the system will "catch up" the next time mailman talks to xmlrpc server. barry, here's the problem, they happen every day matsubara: ultimately, we should get rid of the xmlrpc stuff. it was a solution to a problem we no longer have (namely gpl pollution between mailman and launchpad) if it's safe to ignore them, can we add some code to catch the exception and not log the oops? * stub (n=stub@canonical/launchpad/stub) has joined #launchpad-meeting hi stub you said in the bug report that we have only a handful a week, but I see them everyday, and their numbers are the highest count Ursinha: i get many oops reports for mailman that are clean. am i looking at the wrong reports? barry, I think so :) look at the lpnet reports Ursinha: meaning the daily emails hmm. okay. i see them only rarely in the mailman daily email. i will double check next time i see the report, but i think ignoring the error is the right thing to do barry, ok. it floods the summary, and that's annoying Ursinha: gotcha! i hadn't realized that. i'll do something about it then When I discussed hiding the problems, given the frequency, Francis suggested that we not hide them but investigate a bit. Maybe a small timebox would be appropriate? thaaaanks muchly barry! eh, nm :-) gary_poster, :) gary_poster: yes, we can do that. it will take losa intervention and some cowboy debugging, but it's probably worth it ok cool [action] barry to continue debug on bug 403606 ACTION received: barry to continue debug on bug 403606 Launchpad bug 403606 in launchpad-registry "ExpatError errors should be handled to not generate the OOPSes" [High,Triaged] https://launchpad.net/bugs/403606 thanks barry, gary_poster, Ursinha thanks let's move on [TOPIC] * Oops report & Critical Bugs & Broken scripts New Topic: * Oops report & Critical Bugs & Broken scripts ok Ursinha, take the stage please so the ExpatErrors were already discussed here I have only one bug intellectronica, bug 408738 Launchpad bug 408738 in malone "OOPS when rendering bug activity" [Undecided,Triaged] https://launchpad.net/bugs/408738 that's another one that happens pretty often really? if so then we should at least recover gracefully from it intellectronica, I see those everyday as well i mean in addition to figuring out why we have records like those I agree intellectronica, could you take a look or poke someone to do so, please? yes yes thanks intellectronica :) matsubara, [action] intellectronica to take a look or find someone to take a look on bug 408738 Launchpad bug 408738 in malone "OOPS when rendering bug activity" [Undecided,Triaged] https://launchpad.net/bugs/408738 [action] intellectronica to take a look or find someone to take a look on bug 408738 ACTION received: intellectronica to take a look or find someone to take a look on bug 408738 thanks :) thanks Ursinha and intellectronica we have 2 critical bugs critical bugs are fix committed, and the process-pending-packagediffs script failure was already explained by cprov both fix committed so, we're done! you can move on, matsubara thanks guys! thanks everyone [TOPIC] * Operations report (mthaddon/Chex/spm/mbarnett) New Topic: * Operations report (mthaddon/Chex/spm/mbarnett) hello everyone : hi Chex :) the report for this week: Lots more cherry picks this week More and more problems with codebrowse (per the Incident Log) New losas getting up to speed (Chex and mbarnett) Testing tarmac for oops-tools project - making progress but not quite there yet https://lp-oops.canonical.com/oops.py/?oopsid=tools Will begin process of implementing recommendations from SplitIt Sprint before too long One of our top priority bugs is bug 416990 - others per https://bugs.launchpad.net/~canonical-losas That's it unless there are any questions Launchpad bug 416990 in bzr "Memory usage of codehosting processes is excessive" [High,Confirmed] https://launchpad.net/bugs/416990 Chex, re: tarmac setup for oops-tools, I'll submit a merge proposal to tarmac today with the remaining fixes needed. https://lp-oops.canonical.com/oops.py/?oopsid=tools Chex, I'll coordinate with mthaddon later on cool matsubara: ok, great rockstar, can you poke people in your team about the codehosting memory issue? matsubara: is it worth fixing ubottu not to choke on oops-tools mention? ;) https://lp-oops.canonical.com/oops.py/?oopsid=tools lol I can ask the maintainer matsubara: thanks :) [action] matsubara to chase ubottu maintainer to fix regexp used to identify oopses ACTION received: matsubara to chase ubottu maintainer to fix regexp used to identify oopses let's move on thanks Chex [TOPIC] * DBA report (stub) New Topic: * DBA report (stub) The long running transaction killer is back set to 3 hours, thanks to the Rosetta team sorting out the language pack export issue quickly. oot that was fast hehe like mrevell, it was short thanks stub and rosetta people :-) lol lol [TOPIC] * Proposed items New Topic: * Proposed items we have no proposed items haha bigjools anything else before I close? hi mrevell Thank you all for attending this week's Launchpad Production Meeting. See https://dev.launchpad.net/MeetingAgenda for the logs. matsubara: nothing from me, just responding to bigjools... :) #endmeeting Meeting finished at 10:24.