1 <Ursinha> #startmeeting
   2 <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. 
   3 <MootBot> Meeting started at 11:00. The chair is Ursinha.
   4 <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
   5 <Ursinha> [TOPIC] Roll Call
   6 <Ursinha> Not on the Launchpad Dev team? Welcome! Come "me" with the rest of us! 
   7 <MootBot> New Topic:  Roll Call
   8 <gary_poster> me
   9 <gmb> me
  10 <Ursinha> me
  11 * noodles775 has quit (Quit: leaving)
  12 * matsubara (~matsubara@canonical/launchpad/matsubara) has joined #launchpad-meeting
  13 <matsubara> me
  14 <Ursinha> Chex, sinzui, rockstar, hello
  15 * rockstar  
  16 <bigjools> me
  17 <Ursinha> Chex and sinzui are missing
  18 <Chex> me
  19 <Ursinha> :)
  20 <Ursinha> only sinzui
  21 <Ursinha> let's move on, try to break rockstar's last week record
  22 <Ursinha> :)
  23 <Ursinha> [TOPIC] Agenda
  24 <Ursinha>  * Actions from last meeting
  25 <Ursinha>  * Oops report & Critical Bugs & Broken scripts
  26 <Ursinha>  * Operations report (mthaddon/Chex/spm/mbarnett)
  27 <Ursinha>  * DBA report (stub)
  28 <Ursinha>  * QA stats of the week
  29 <Ursinha>  * Proposed items
  30 <MootBot> New Topic:  Agenda
  31 <Ursinha> [TOPIC] * Actions from last meeting
  32 <Ursinha> None
  33 <MootBot> New Topic:  * Actions from last meeting
  34 <Ursinha> [TOPIC] * Oops report & Critical Bugs & Broken scripts
  35 <MootBot> New Topic:  * Oops report & Critical Bugs & Broken scripts
  36 <Ursinha> only one bug, soyuz
  37 <Ursinha> bigjools must love me
  38 <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?
  39 <bigjools> it's in progress
  40 <ubot5> Launchpad bug 580181 in Soyuz "DistributionSourcePackageRelease page still oopsing with NotOneError/LocationError (affected: 1, heat: 8)" [High,Fix released]
  41 <bigjools> Ursinha: it needs a new bug
  42 <Ursinha> bigjools, so soyuz has two, this one and the critical
  43 <Ursinha> bigjools, I'll file one right after this meeting
  44 <bigjools> heh
  45 <sinzui> me
  46 <bigjools> cheers
  47 <Ursinha> bigjools, bug 589073 is in progress?
  48 <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
  49 <Ursinha> is it really critical?
  50 <bigjools> Ursinha: yes, jelmer should have set that in progress ;)
  51 <bigjools> I don't think it is actually, I'll downgrade it
  52 <Ursinha> thanks bigjools 
  53 <Ursinha> we have two critical bugs, one soyuz, one foundations, both being worked on then
  54 <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
  55 <Ursinha> Is anyone taking care of this?
  56 <bigjools> retrydepwait is fixed and released
  57 <Ursinha> bigjools, right, cool
  58 <Ursinha> last failure was yesterday
  59 <Ursinha> gary_poster, about nightly.sh, is that foundations' domain?
  60 <sinzui> Ursinha, I think nightly.sh is/was a victim of the master/slave issue
  61 <Ursinha> sinzui, right
  62 <Ursinha> sinzui, it failed yesterday again
  63 <sinzui> nightly.sh has no owner. The losas do a lot of tinkering with it and they do not think they should
  64 <gary_poster> nominally foundations then I suppose
  65 <gary_poster> :-/
  66 <sinzui> Since it takes 36 hours to run, we would expect it to fail even after the db was fixed
  67 <rockstar> It's a good thing that days are longer than 36 hours so that it can actually run nightly...
  68 <sinzui> Another failure to run on time would be worrisome and will warrant further investigation
  69 <gary_poster> agreed
  70 <Ursinha> yeah, right
  71 <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 :-)
  72 <gary_poster> but for now I think we can move on
  73 <Ursinha> gary_poster, sure 
  74 <Ursinha> :)
  75 <Ursinha> good
  76 <matsubara> I don't think nightly.sh should be exclusively foundations
  77 <sinzui> gary_poster, rockstar, other than the karma-cache update, I think everything in nightly can be parallelised.
  78 <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
  79 <sinzui> the scripts in it belong to code, bugs, translations, and registry
  80 * EdwinGrubbs has quit (Ping timeout: 260 seconds)
  81 <matsubara> taking the last run for example, package cache and bugtask target names are the worst offenders
  82 <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
  83 <sinzui> and soyuz then
  84 <matsubara> so malone and soyuz(?) should take care of those first
  85 <sinzui> Most failures are spurious.
  86 <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
  87 <gary_poster> cool thanks
  88 <sinzui> The 9 times out of 10, the last proc ran late because of something else run in the sequence
  89 <Ursinha> ok, so I'll move on
  90 <Ursinha> [TOPIC] * Operations report (mthaddon/Chex/spm/mbarnett)
  91 <MootBot> New Topic:  * Operations report (mthaddon/Chex/spm/mbarnett)
  92 <Chex> hello everyone, short report this week:
  93 <Chex>  - LP incidents of note, quiet week:
  94 <Chex>         : Jun 08: lpnet15 died, restarted
  95 <Chex>         : Jun 10 : poppy on germanium had died (process died) - restarted
  96 <Chex> Us LOSAs are now searching on Canonical-losas -tagged bugs, here:
  97 <Chex> https://pastebin.canonical.com/33309/
  98 <Chex> I am curious about status of: 45419      Launchpad needs a way of easily flagging spam
  99 <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.
 100 <Ursinha> bug 45419?
 101 <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
 102 <Ursinha> gary_poster should know that ^
 103 <gary_poster> Foundations does not have that anywhere in our plans ATM.
 104 <Ursinha> right..
 105 <Chex> gary_poster: ok, fair enough, then
 106 <Ursinha> anyone else has questions to Chex?
 107 <gary_poster> Chex, that doesn't mean you can't/shouldn't make a stink about that fact :-)
 108 <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
 109 <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
 110 <Ursinha> ok, moving on
 111 <Ursinha> thanks Chex 
 112 <Ursinha> [TOPIC] * DBA report (stub)
 113 <Ursinha> Already requested
 114 <MootBot> New Topic:  * DBA report (stub)
 115 <Ursinha> [TOPIC] * QA stats of the week
 116 <MootBot> New Topic:  * QA stats of the week
 117 <Ursinha> I followed up the bugs' ownership in the mailing list
 118 <gary_poster> Chex: spam-reporting: mars and sinzui have the expertise here.  I'll try to coordinate with them.
 119 <sinzui> I had a plan
 120 <rockstar> sinzui, it's because you're a Cylon.
 121 <sinzui> a comprehensive one infact
 122 <gmb> Was it a cunning plan?
 123 <sinzui> That would explain why I can do so long without sleep
 124 <matsubara> heheh
 125 <sinzui> It had a tail like a fox
 126 * gary_poster chuckles
 127 <gmb> Any more pop-culture references we can fit in here?
 128 <Ursinha> hahaha
 129 <sinzui> We seem to have missed monthy python
 130 <sinzui> Monty Python
 131 <sinzui> I will include that in my email to gary_poster and maris
 132 <Ursinha> thanks sinzui hehe
 133 <gary_poster> thanks sinzui
 134 <Ursinha> moving on again then
 135 <Ursinha> [TOPIC] * Proposed items
 136 <MootBot> New Topic:  * Proposed items
 137 <Ursinha> I have one
 138 <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
 139 <Ursinha> we also realized the qa contacts initiative isn't that effective as we thought in the beginning
 140 <rockstar> Ursinha, for the code team, the only things that are really useful for us are the DB and LOSA reports.
 141 <Ursinha> rockstar, yeah, I'm getting there :)
 142 <rockstar> "Shutting up sir"
 143 <Ursinha> haha no 
 144 <Ursinha> so, after talking with flacoste, we decided to get rid of this meeting as we know
 145 <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
 146 <Ursinha> pause for cheering and etc
 147 <rockstar> Ursinha, so we're doing away with it entirely?
 148 <Ursinha> rockstar, yeah
 149 <bigjools> *golfclap*
 150 <Ursinha> sinzui, as a replacement, there will be created a section in the TLs meeting, a QA one
 151 <Ursinha> and me and matsubara should attend
 152 <Ursinha> we'll keep discussing that with the TLs, so sinzui, you'll still know about the oopses
 153 <sinzui> sweet. I wonder if the meeting will go back over an hour again
 154 <Ursinha> and bigjools, you won't get rid of us
 155 <Ursinha> *evil laugh*
 156 <Ursinha> :P
 157 <gary_poster> :-)
 158 <bigjools> :)
 159 <Ursinha> about the LOSAs and DBA report
 160 <Ursinha> a weekly report should be sent to the list, so we'll all keep posted about it
 161 <Ursinha> so, that's it
 162 <Chex> ok, sounds good, I can do that.
 163 <rockstar> Ursinha, maybe we can have a [QA] subject addition for QA related items.
 164 <Ursinha> thanks a lot Chex, losa's reports are really important
 165 <rockstar> (I suspect I'll still have to deal with QA stuff within my team)
 166 <Ursinha> rockstar, well, it should be dealt with whoever attends the TLs meeting in behalf of code
 167 <Ursinha> is that you?
 168 <Chex> Ursinha: yes I understand that, it helps us, too. I will try to pop my head in on the TLS meetings, too,
 169 <rockstar> Ursinha, no.
 170 <Ursinha> rockstar, so I guess you will only have to worry about your own QA from now on
 171 <rockstar> Ursinha, okay.
 172 <Ursinha> that's all then
 173 <Ursinha> anyone else wants to add something?
 174 <Ursinha> okay
 175 <Ursinha> so, it was very nice to have you for these two years in this weekly meeting
 176 <Ursinha> thanks all
 177 <gary_poster> thank you Ursinha :-)
 178 <Ursinha> Thank you all for attending this week's Launchpad Production Meeting. See https://dev.launchpad.net/MeetingAgenda for the logs.
 179 <gary_poster> bye
 180 <Ursinha> #endmeeting