/srv/irclogs.ubuntu.com/2010/05/20/#launchpad-dev.txt

pooliespm, there's some russian spam in https://answers.edge.launchpad.net/launchpad-code/+question/1379600:20
pooliei guess i should file a question?00:20
spmpoolie: questions, even more so than bugs; yes. that's a hand  crafted sql task.00:23
pooliehttps://answers.edge.launchpad.net/launchpad/+question/111646 fwiw00:24
=== Ursinha is now known as Ursinha-afk
=== lifeless_ is now known as lifeless
cody-somerville"This change is completely inert when not using XYZ" doesn't sound quite right at this hour. I have a feeling I'm actually looking to use a different, more appropriate word but can't think of it at the moment.06:13
lifelessA better word than is? Try etre.06:14
cody-somervillelol06:14
cody-somervillelifeless, was referring to 'inert'. :P06:14
lifelessYou have a double negative06:16
lifelessI suggest a single positive.06:16
cody-somervilleplus, etre is the verb 'to be'. I think you meant to recommend 'est'. :P06:16
lifeless"This change only takes effect when using XYZ."06:16
lifelesssame word :)06:17
lifelessyou need more practice at conjugation ;)06:17
cody-somervilleconjug...06:17
* cody-somerville was going to say conjugation is important :P06:18
lifelesshttp://www.wordreference.com/conj/FRverbs.asp?v=etre06:18
* cody-somerville doesn't dispute his French could use a lot of work in many areas.06:20
cody-somervillelifeless, anyhow, thanks. :)06:20
lifelessde nada06:20
adeuringgood morning08:15
spmnoodles775: ta. I'm often not quite sure which sub group a bug belongs to; when it doubt, let you lot figure it out. :-)08:20
noodles775spm: no probs.08:20
mrevellMorning08:58
lifelesscan Storm handle sets ? We have a comment about SQLObject failing on them in sqlbase.py10:17
lifelessand a workaround we could proably delete now10:17
deryckMorning, all.11:01
=== mrevell is now known as mrevell-lunch
=== jelmer is now known as Guest38382
=== Guest38382 is now known as jelmer
deryckBjornT, ping13:22
=== mrevell-lunch is now known as mrevell
BjornThi deryck13:40
deryckBjornT, hi.  I'm starting work on bug 418659 and you have some comments there about your previous work on this...13:41
mupBug #418659: Reporting duplicate bugs leads to receiving notifications for every duplicate of the original bug <ubuntu-qa> <Launchpad Bugs:In Progress by deryck> <https://launchpad.net/bugs/418659>13:41
deryckBjornT, and I'm looking at your work in:  https://code.edge.launchpad.net/~bjornt/launchpad/bug-46237/+merge/888613:41
deryckAnd I wonder if I'm reading your intent right....13:42
deryckBjornT, was your work to ensure that Bug A subscribers are *not* notified when Bug B is marked a dupe?  Or that Only Bug A subscribers are notified when Bug C is marked a dupe and Bug B subscribers via dupe are not notified about bug C?13:42
deryckif that makes sense :-)13:43
BjornTderyck: i think some clarification is needed :) in my example Bug B was the master bug13:44
BjornTderyck: might be easier if we take real example, e.g. bug 46237, which has a few duplicates13:46
mupBug #46237: fine-tune delivery of duplicate notification mails <email> <Launchpad Bugs:Fix Released by bjornt> <https://launchpad.net/bugs/46237>13:46
deryckyeah, good idea.13:46
deryckBjornT, So when Bug #91212 was marked a dupe of that bug, should direct subscribers to bug 46237 be notified of this?13:47
mupBug #91212: people subscribed to bugs that are duplicates shouldn't receive notifications of new duplicates to the master bug <email> <Launchpad Bugs:Triaged> <https://launchpad.net/bugs/91212>13:47
mupBug #46237: fine-tune delivery of duplicate notification mails <email> <Launchpad Bugs:Fix Released by bjornt> <https://launchpad.net/bugs/46237>13:47
BjornTderyck: no. only the ones that are subscribed to bug #91212 should be notified about it.13:48
mupBug #91212: people subscribed to bugs that are duplicates shouldn't receive notifications of new duplicates to the master bug <email> <Launchpad Bugs:Triaged> <https://launchpad.net/bugs/91212>13:48
deryckBjornT, ok.  Which should cover the second case of subscribers to 91212 being notified when the master add yet another bug marked as a dupe of it.  right?13:49
derycks/add/had/13:49
BjornTderyck: right13:50
deryckBjornT, and people were generally in agreement that direct subscribers on the master do not want to know via email about dupes being added?13:50
marssinzui, rockstar, is one of you working on the broken build?13:54
sinzuimars, I am trying to understand it13:55
marsok.  Thanks sinzui.13:55
BjornTderyck: yes. they said that even though it's somewhat useful to get notified for the developers, decreasing the number of e-mails sent was more important.13:56
deryckBjornT, right, that makes sense, given the two choices.13:56
deryckBjornT, and the only test for this is in test_bugchanges.py?13:56
BjornTderyck: i think so, yes13:57
deryckBjornT, ok, great, thanks for helping me understand.13:57
=== Ursinha-afk is now known as Ursinha
sinzuimars, is the build really broken? I think my pre-emptive fix was not really run until gary restarted it?14:09
marssinzui, I assume you can not reproduce this locally?  If you suspect is not broken, maybe you can throw a null [testfix] in there and see if it breaks again?14:11
sinzuimars, to force a build to see if the failure was spurious or real?14:11
marssinzui, that of course assumes that a null testfix will force a full suite re-run without adding changes from the queue - I don't know if that is the case.14:12
marssinzui, yes, to force a rebuild14:12
sinzuiI can always reformat a test :)14:12
marsBjornT, ^ will that work?14:12
* mars is still learning about the pqm part of the build system14:13
BjornTmars: i'm not sure what the question is :)14:15
marsBjornT, sinzui suspects the failure is suprious.  Can he submit an empty [testfix] to PQM to have it clear the flag and force a rebuild of just his and Paul's changes?14:17
BjornTsinzui: which failure?14:17
BjornTmars: ^^^14:18
sinzuifaq-views in failed devel (ran on the wrong layer). I did a preemptive fix, while it was building14:19
jelmerjml: whoops, didn't mean to make you angry!14:19
BjornTsinzui: right. and that fixed it, no?14:19
jmljelmer: only blogging-angry14:19
jelmerjml: is that a good kind of angry?14:19
jmljelmer: it's the kind of angry that hurts no-one except my keyboard and maybe some people's bandwidth14:19
sinzuiBjornT, but it was (reported) failed again  when gary forced it to restart. it is not clear if by forcing to to restart, my fix was in it so we saw a second failure?14:20
jelmerjml: ah, good14:20
=== ]reed[ is now known as [reed]
marssinzui, BjornT, fwiw, I was just looking for the "kick it again and see" answer here :)14:21
marssinzui, BjornT, I just don't know the right way to give the test system said kick14:21
BjornTsinzui: if you look at build 900, you see that it's testing up to r10892. your fix was r10895. as far as i can see, buildbot is all green.14:22
BjornTmars: why kick it? the last build succeeded14:22
sinzuiBjornT, thanks for seeing that! mars, I think db-devel has already played the test14:22
marsBjornT, ah, ok.  So I was confused because it got fixed without any mail to the list saying "Everything is good again".14:24
marsSo I said "Oh, it must be broken"14:24
BjornTmars: yeah, we should teach people to always reply to build failures, so that others don't waste time trying to fix something that has already been fixed14:30
=== deryck is now known as deryck[lunch]
=== deryck[lunch] is now known as deryck
=== Chex_ is now known as Chex
=== salgado is now known as salgado-lunch
=== beuno is now known as beuno-lunch
=== matsubara is now known as matsubara-lunch
=== salgado-lunch is now known as salgado
=== beuno-lunch is now known as beuno
=== gary_poster is now known as gary-lunch
=== matsubara-lunch is now known as matsubara
=== EdwinGrubbs is now known as Edwin-lunch
=== gary-lunch is now known as gary_poster
bachi matsubara20:27
matsubarabac, hi20:27
bacmatsubara: i'm getting the message rejection email when i submit a MP even though i am subscribed to launchpad-bugs.  does mesh with your understanding of the problem?20:27
matsubarabac, I'm looking at the subscribers list and your email is parenthesized which means: Parenthesized entries have list delivery disabled.20:32
matsubaramaybe that's the reason?20:32
bacno20:32
baci just talked to barry and he said i should be able to post still20:32
bacmatsubara: i think the problem is canonical-ubuntu-platform is subscribed to devel20:32
matsubaraI'm not even sure if the hypothesis is true anymore, since ~launchpad is configured to not receive any email from devel20:32
matsubarabac, but then email to that team would go to: mdz-ubuntuplatform@alcor.net20:33
matsubaras/email/emails/20:33
bacmatsubara: ok, so maybe that's not it20:34
bacmatsubara: but launchpad-bugs is not the culprit, i don't think20:34
bacit's really annoying20:34
matsubarabac, AFAICT, there can be only one team in LP using the launchpad-bugs@lists.ubuntu.com email address20:35
matsubaraand that's ~launchpad20:35
bacmatsubara: right but we don't really know that list is the culprit20:35
matsubarahmmm, unless we have another team with launchpad-bugs@lists.canonical.com20:35
bacmatsubara: and that list has been the contact email forever20:35
=== Edwin-lunch is now known as EdwinGrubbs
mwhudsonmorning21:11
thumpermorning21:17
jelmer_'moin mwhudson, thumper21:22
thumperhi jelmer_21:22
thumperI saw in passing last night that you had tweaked dulwich21:23
thumperjelmer_: I can't seem to reproduce the original failure locally :(21:25
jelmer_Things that involve reference loops and the garbage collector never seem to be predictable :-/21:26
* thumper does school run21:31
marsabentley, still online?21:44
abentleymars, sure.21:44
marsabentley, have a moment to look at that test suite problem you encountered?21:44
abentleymars, OTP21:45
marsabentley, ok, whenever you have a moment then21:45
=== matsubara is now known as matsubara-afk
=== jamalta_ is now known as jamalta
=== salgado is now known as salgado-afk

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!