#format IRC
<Ursinha> #startmeeting
<Ursinha> 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. 
<MootBot> Meeting started at 11:00. The chair is Ursinha.
<MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
<Ursinha> [TOPIC] Roll Call
<Ursinha> Not on the Launchpad Dev team? Welcome! Come "me" with the rest of us! 
<MootBot> New Topic:  Roll Call
<gary_poster> me
<gmb> me
<Ursinha> me
* noodles775 has quit (Quit: leaving)
* matsubara (~matsubara@canonical/launchpad/matsubara) has joined #launchpad-meeting
<matsubara> me
<Ursinha> Chex, sinzui, rockstar, hello
* rockstar  
<bigjools> me
<Ursinha> Chex and sinzui are missing
<Chex> me
<Ursinha> :)
<Ursinha> only sinzui
<Ursinha> let's move on, try to break rockstar's last week record
<Ursinha> :)
<Ursinha> [TOPIC] Agenda
<Ursinha>  * Actions from last meeting
<Ursinha>  * Oops report & Critical Bugs & Broken scripts
<Ursinha>  * Operations report (mthaddon/Chex/spm/mbarnett)
<Ursinha>  * DBA report (stub)
<Ursinha>  * QA stats of the week
<Ursinha>  * Proposed items
<MootBot> New Topic:  Agenda
<Ursinha> [TOPIC] * Actions from last meeting
<Ursinha> None
<MootBot> New Topic:  * Actions from last meeting
<Ursinha> [TOPIC] * Oops report & Critical Bugs & Broken scripts
<MootBot> New Topic:  * Oops report & Critical Bugs & Broken scripts
<Ursinha> only one bug, soyuz
<Ursinha> bigjools must love me
<Ursinha> bigjools, I see the last noodles' comment in https://bugs.edge.launchpad.net/soyuz/+bug/580181, do you know if that's being tracked and fixed in another bug or one needs to be filed?
<bigjools> it's in progress
<ubot5> Launchpad bug 580181 in Soyuz "DistributionSourcePackageRelease page still oopsing with NotOneError/LocationError (affected: 1, heat: 8)" [High,Fix released]
<bigjools> Ursinha: it needs a new bug
<Ursinha> bigjools, so soyuz has two, this one and the critical
<Ursinha> bigjools, I'll file one right after this meeting
<bigjools> heh
<sinzui> me
<bigjools> cheers
<Ursinha> bigjools, bug 589073 is in progress?
<ubot5> Launchpad bug 589073 in Soyuz "Unhandled exception processing upload: permission denied for relation emailaddress (affected: 1, heat: 6)" [Critical,Triaged] https://launchpad.net/bugs/589073
<Ursinha> is it really critical?
<bigjools> Ursinha: yes, jelmer should have set that in progress ;)
<bigjools> I don't think it is actually, I'll downgrade it
<Ursinha> thanks bigjools 
<Ursinha> we have two critical bugs, one soyuz, one foundations, both being worked on then
<Ursinha> failing scripts are retry-depwait, that's being fixed by bigjools, and karma-update, allocate-revision-karma and others that, according to spm's email, are failing because nightly.sh is taking about 36 hours to run
<Ursinha> Is anyone taking care of this?
<bigjools> retrydepwait is fixed and released
<Ursinha> bigjools, right, cool
<Ursinha> last failure was yesterday
<Ursinha> gary_poster, about nightly.sh, is that foundations' domain?
<sinzui> Ursinha, I think nightly.sh is/was a victim of the master/slave issue
<Ursinha> sinzui, right
<Ursinha> sinzui, it failed yesterday again
<sinzui> nightly.sh has no owner. The losas do a lot of tinkering with it and they do not think they should
<gary_poster> nominally foundations then I suppose
<gary_poster> :-/
<sinzui> Since it takes 36 hours to run, we would expect it to fail even after the db was fixed
<rockstar> It's a good thing that days are longer than 36 hours so that it can actually run nightly...
<sinzui> Another failure to run on time would be worrisome and will warrant further investigation
<gary_poster> agreed
<Ursinha> yeah, right
<gary_poster> And I certainly have not regarded nightly.sh as a foundations responsibility.  I guess that needs to change.  Ursinha, please do help me kick myself about this :-)
<gary_poster> but for now I think we can move on
<Ursinha> gary_poster, sure 
<Ursinha> :)
<Ursinha> good
<matsubara> I don't think nightly.sh should be exclusively foundations
<sinzui> gary_poster, rockstar, other than the karma-cache update, I think everything in nightly can be parallelised.
<matsubara> I think the losas are pretty good at identifying which scripts run by nightly.sh are the worst offenders and then the responsible team should take care of that script
<sinzui> the scripts in it belong to code, bugs, translations, and registry
* EdwinGrubbs has quit (Ping timeout: 260 seconds)
<matsubara> taking the last run for example, package cache and bugtask target names are the worst offenders
<gary_poster> matsubara: no, but if no-one is in charge of something, historically that means foundations.  I'd certainly like it if losas could take that ownership though
<sinzui> and soyuz then
<matsubara> so malone and soyuz(?) should take care of those first
<sinzui> Most failures are spurious.
<Ursinha> matsubara, sinzui, gary_poster, what do you think about discussing that in the email spm sent? this way we can be sure everyone else can join the discussion
<gary_poster> cool thanks
<sinzui> The 9 times out of 10, the last proc ran late because of something else run in the sequence
<Ursinha> ok, so I'll move on
<Ursinha> [TOPIC] * Operations report (mthaddon/Chex/spm/mbarnett)
<MootBot> New Topic:  * Operations report (mthaddon/Chex/spm/mbarnett)
<Chex> hello everyone, short report this week:
<Chex>  - LP incidents of note, quiet week:
<Chex>         : Jun 08: lpnet15 died, restarted
<Chex>         : Jun 10 : poppy on germanium had died (process died) - restarted
<Chex> Us LOSAs are now searching on Canonical-losas -tagged bugs, here:
<Chex> https://pastebin.canonical.com/33309/
<Chex> I am curious about status of: 45419      Launchpad needs a way of easily flagging spam
<Chex> In the future I will try to bring up critical LP related bugs from this list, to see progress and such, and see if you need any help from us at all.
<Ursinha> bug 45419?
<ubot5> Launchpad bug 45419 in Launchpad Foundations "Launchpad needs a way of easily flagging spam (affected: 7, heat: 60)" [High,Triaged] https://launchpad.net/bugs/45419
<Ursinha> gary_poster should know that ^
<gary_poster> Foundations does not have that anywhere in our plans ATM.
<Ursinha> right..
<Chex> gary_poster: ok, fair enough, then
<Ursinha> anyone else has questions to Chex?
<gary_poster> Chex, that doesn't mean you can't/shouldn't make a stink about that fact :-)
<sinzui> If this is a foundations issue, we schema a behavioural changes made near/on IMessage so that all types of messages get the desired feature
<Chex> gary_poster: aha, ok then.  It is a time-consuming task for us, and having a automated spam-reporting/tagging feature would be highly useful to us
<Ursinha> ok, moving on
<Ursinha> thanks Chex 
<Ursinha> [TOPIC] * DBA report (stub)
<Ursinha> Already requested
<MootBot> New Topic:  * DBA report (stub)
<Ursinha> [TOPIC] * QA stats of the week
<MootBot> New Topic:  * QA stats of the week
<Ursinha> I followed up the bugs' ownership in the mailing list
<gary_poster> Chex: spam-reporting: mars and sinzui have the expertise here.  I'll try to coordinate with them.
<sinzui> I had a plan
<rockstar> sinzui, it's because you're a Cylon.
<sinzui> a comprehensive one infact
<gmb> Was it a cunning plan?
<sinzui> That would explain why I can do so long without sleep
<matsubara> heheh
<sinzui> It had a tail like a fox
* gary_poster chuckles
<gmb> Any more pop-culture references we can fit in here?
<Ursinha> hahaha
<sinzui> We seem to have missed monthy python
<sinzui> Monty Python
<sinzui> I will include that in my email to gary_poster and maris
<Ursinha> thanks sinzui hehe
<gary_poster> thanks sinzui
<Ursinha> moving on again then
<Ursinha> [TOPIC] * Proposed items
<MootBot> New Topic:  * Proposed items
<Ursinha> I have one
<Ursinha> we know that this meeting's format isn't ideal, and we couldn't find a way to change it to become really useful
<Ursinha> we also realized the qa contacts initiative isn't that effective as we thought in the beginning
<rockstar> Ursinha, for the code team, the only things that are really useful for us are the DB and LOSA reports.
<Ursinha> rockstar, yeah, I'm getting there :)
<rockstar> "Shutting up sir"
<Ursinha> haha no 
<Ursinha> so, after talking with flacoste, we decided to get rid of this meeting as we know
<sinzui> I care about the oopses actually. Since I read them every day I like to know when they will be closed or provide info about how to close them
<Ursinha> pause for cheering and etc
<rockstar> Ursinha, so we're doing away with it entirely?
<Ursinha> rockstar, yeah
<bigjools> *golfclap*
<Ursinha> sinzui, as a replacement, there will be created a section in the TLs meeting, a QA one
<Ursinha> and me and matsubara should attend
<Ursinha> we'll keep discussing that with the TLs, so sinzui, you'll still know about the oopses
<sinzui> sweet. I wonder if the meeting will go back over an hour again
<Ursinha> and bigjools, you won't get rid of us
<Ursinha> *evil laugh*
<Ursinha> :P
<gary_poster> :-)
<bigjools> :)
<Ursinha> about the LOSAs and DBA report
<Ursinha> a weekly report should be sent to the list, so we'll all keep posted about it
<Ursinha> so, that's it
<Chex> ok, sounds good, I can do that.
<rockstar> Ursinha, maybe we can have a [QA] subject addition for QA related items.
<Ursinha> thanks a lot Chex, losa's reports are really important
<rockstar> (I suspect I'll still have to deal with QA stuff within my team)
<Ursinha> rockstar, well, it should be dealt with whoever attends the TLs meeting in behalf of code
<Ursinha> is that you?
<Chex> Ursinha: yes I understand that, it helps us, too. I will try to pop my head in on the TLS meetings, too,
<rockstar> Ursinha, no.
<Ursinha> rockstar, so I guess you will only have to worry about your own QA from now on
<rockstar> Ursinha, okay.
<Ursinha> that's all then
<Ursinha> anyone else wants to add something?
<Ursinha> okay
<Ursinha> so, it was very nice to have you for these two years in this weekly meeting
<Ursinha> thanks all
<gary_poster> thank you Ursinha :-)
<Ursinha> Thank you all for attending this week's Launchpad Production Meeting. See https://dev.launchpad.net/MeetingAgenda for the logs.
<gary_poster> bye
<Ursinha> #endmeeting