[01:21] Project devel build #1,027: STILL FAILING in 4 hr 6 min: https://lpci.wedontsleep.org/job/devel/1027/ [01:32] wgrant: lpci has a new cert [01:38] StevenK: Indeed, thanks! [04:14] Morning! [04:15] *yawn* [04:15] are we still in testfix? [04:19] hmm. QA. [05:38] Project devel build #1,028: STILL FAILING in 4 hr 8 min: https://lpci.wedontsleep.org/job/devel/1028/ [05:54] nigelb: kia ora [06:03] G: O hai. You haz qa [06:03] G: I can give you run-down if you need it. [06:04] StevenK: huh? [06:05] G: Launchpad has a deployment report for which revisions are deployable to production. Before they can deployed they need to be QA'd and marked as such in the bug. [06:05] StevenK: oh so this is something that I have to / can do? [06:05] Sadly, the deployment report is private, but I've started the process to open it up. [06:06] G: We prefer people do their own QA if they can. [06:06] sure I can do it myself [06:07] G: r13839 / bug 837290 and r13856 / bug 61428 [06:07] <_mup_> Bug #837290: When there is no "Other bug subscribers" incorrect descriptive text is displayed < https://launchpad.net/bugs/837290 > [06:07] <_mup_> Bug #61428: Want a "subscribed to teams" portlet... < https://launchpad.net/bugs/61428 > [06:07] StevenK: yep I was just loading up the bugs myself :) [06:07] G: You can use qastaging.launchpad.net to see if your code fixes the problem [06:07] okay [06:07] G: If it looks good, then remove the tag of 'qa-needstesting' and add one of 'qa-ok' [06:08] is qastaging clean data or what? [06:08] oh nevermind, I clicked login and openid logged me in [06:08] qastaging is using the production database, which is probably a few months out of date [06:09] qastaging and staging use their own databases, so it's fine to play with [06:12] StevenK: okay, 837290 is qa-ok now [06:12] G: Excellent! [06:14] We have 29 revisions in the queue, so I doubt we're fully deployable until AU Tuesday morning, with probably some deployable UK Monday morning [06:14] ditto for 61428 [06:14] StevenK: done [06:15] * G hits the big read "That was Easy!" button [06:15] *red [06:19] StevenK: btw, if there are any other bugs that need a look over for verification just let me know [06:25] G: Your 3 revisions are all qa-ok :-) [06:26] StevenK: yep :) === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away [09:47] Project devel build #1,029: STILL FAILING in 4 hr 8 min: https://lpci.wedontsleep.org/job/devel/1029/ [09:54] StevenK: are we still in testfix? [09:54] One of my branches is unmerged I think. [10:22] Sigh. Yes. [10:23] I can force, but there is little point, since it will fail that test. [10:27] Ah [10:27] this is the bzr-related test which was talked about yesterday? [10:40] Yeah, one of the lpserve tests [10:41] *whee* [10:42] I think I was on the blamelist of buildbot when it failed. [10:42] * nigelb remembers getting a failure email. [11:38] hmmm interesting [11:40] I was looking at the code behind https://bugs.launchpad.net/launchpad/+bug/697157 (which I'm going to fix) and noticed something interesting that I hadn't really realized [11:40] <_mup_> Bug #697157: Streamline "You have assigned this bug to yourself" message < https://launchpad.net/bugs/697157 > [11:41] sometimes an action can generate two e-mails (i.e. comment on bug, and assign to $self) first been the generate comment bug, and then another e-mail implying that the bug is NEW sent 2 seconds later