[00:08] do we still use Pygpgme ? [00:09] wgrant: https://bugs.launchpad.net/launchpad/+bug/184835 [00:09] <_mup_> Bug #184835: Add status '9' (which equates to WONTFIX) to the Roundup external bug tracker < https://launchpad.net/bugs/184835 > [00:09] wgrant: is that fixed incidentally? [00:09] lifeless: No, but it's no longer an OOPS, so it's Low. [00:13] wgrant: what about https://bugs.launchpad.net/launchpad/+bug/125068 ? [00:13] <_mup_> Bug #125068: Bugzilla bug watch updater crashes on POSTs that return a HTTP error < https://launchpad.net/bugs/125068 > [00:13] lifeless: Some of those are fixed, others are not. [00:13] I wonder if leonardr's work has fixed https://bugs.launchpad.net/launchpad/+bug/106338 ? [00:13] <_mup_> Bug #106338: Editing a bug targeted to a release crashes if you directly edit the untargeted task < https://launchpad.net/bugs/106338 > [00:13] I need to check waht still shows up. [00:14] he says it hasn't fixed it [00:14] but I wonder if we're lucky [00:14] Indeed. [00:14] He tested it. [00:14] And said it wasn't fixed. [00:25] wgrant: hey - https://bugs.launchpad.net/launchpad-buildd/+bug/497772 - would love to get bm crashes oopsing [00:25] <_mup_> Bug #497772: exceptions.AttributeError: 'DebianBuildManager' object has no attribute '_subprocess' < https://launchpad.net/bugs/497772 > [00:35] lifeless: So, roughly, "fuck no" [00:36] Generating OOPSes from user-controlled code == bad [00:37] It's also really hard, since there is no access to the slaves except through lp-buildd, and that's what's broken here. [00:39] wgrant: uhm, thats not what I was saying [00:39] wgrant: if the build manager blows up, it should write an oops. [00:39] ditto lp-buildd [00:39] Where should lp-buildd write an OOPS to? [00:39] if the *build* fails, thats not lp-buildd or the build manager blowing up [00:40] wgrant: hand it off to the bm [00:40] And how do we know a user isn't going to run their own lp-buildd and generate millions of OOPSes? [00:40] wgrant: can they talk to the build master? [00:40] lifeless: I can easily hijack a buildd and get my own lp-buildd to run there. [00:40] wgrant: on the host os? [00:41] lifeless: Outside the chroot, but inside the VM. [00:41] wgrant: isn't that on a different IP ? [00:41] lifeless: lp-buildd runs inside the VM. [00:41] We don't talk to the host at all. [00:41] *blink* [00:41] We don't know that the host exists. [00:41] ok [00:41] uhm [00:41] We just know that there is a command that we can run to reset the VM. [00:41] (because we will need to use alternative virt solutions in the future *cough* ARM *cough*, where there is no Linux on the host) [00:42] you have a good scary story there [00:42] but [00:43] if we get an oops from lp-buildd, its time to kill the build [00:43] that prevents millions of oopses from one instance [00:43] What does killing the build mean? [00:43] Killing the build does not kill lp-buildd. [00:44] wgrant: AIUI we restart the buildd per build because of precisely the trust issues you allude to [00:44] wgrant: so I mean that [00:44] lifeless: At the moment we only restart it when the next build starts. But that is itself a security issue, so we should probably fix that. [01:02] There seem to be three different ways an externalbugtracker can indicate that the importance is unable to be converted :( [01:03] \o/ [01:04] lifeless: Bug #422960 is cheating. [01:04] <_mup_> Bug #422960: appear to be failing to record oops for all +translate HTTP 503 errors < https://launchpad.net/bugs/422960 > [01:04] wgrant: I disagree :) [01:06] wgrant: it falls into the bucket of a bunch of operational improvements that we should do, IMO [01:07] Maybe. [01:08] Almost OOPS report time. [01:08] yeah [01:08] almost 11 second timeout time [01:08] Exactly. [01:09] What did we start at? [01:09] 16? [01:09] 20 [01:09] 17 on edge [01:09] step 1 was making both 17 [01:10] I was going to say 17, but I thought that seemed a bit odd. [01:10] since then we've ratched as we fixed things [01:10] edge was lower 'to catch slow pages' - but has a different user population, so not very effective at that [01:11] And edge still isn't dead. :-( [01:11] its in the queue [01:12] But at least it no longer has a shorter queue. [01:15] lifeless: Your gardening has nearly been successful. [01:15] But not quite :( [01:15] I'd like to rewrite my Firefox URL suggestions, since most of those tend to be edge URLs [01:17] wgrant: thats just the first 75 [01:17] StevenK: sqlite3 [01:17] StevenK: update ... [01:17] where ... [01:20] lifeless: Er, which of the 4,000,000 sqlite databases? :-) [01:22] places [01:23] thumper: got a sec on mumble? [01:23] sure [01:27] sqlite> select count(*) from moz_places where url like '%edge%'; [01:27] 163 [01:27] :-( [01:34] gnarrrrgh [01:35] If I "accidentally" break bug searching and manage to globally corrupt the history so the old code is irretrievable, does writing an implementation does not UTTERLY SUCK become critical? [01:35] s/implementation/implementation that/ [01:37] How do you plan to globally corrupt the history? :-) [01:37] That's one part of the plan that is not yet entirely defined. [01:38] wgrant: To quote Penny Arcade: Stay Good! [01:40] lifeless: Is bug #558585 valid? [01:40] <_mup_> Bug #558585: librarian outages cause OOPSes on pages showing BranchMergeProposal diffs < https://launchpad.net/bugs/558585 > [01:40] That's like complaining that Launchpad doesn't work when the DB is down. [01:40] Except that mizuho is shit and a SPOF. [01:42] Next p-s-c run will hit SPR 98000 [01:43] wgrant: its arguable [01:43] I'm not sure if we should say 'yes, yes it does' [01:44] or 'we should degrade gracefully' [01:48] StevenK: Isn't the much faster than we thought? [01:48] Or are lots of early SPRs missing? [01:49] Lots of early SPRs are missing changelogs [01:49] I mean missing in general. [01:49] I don't know what evil was done before the first import. [01:49] Ah. The first SPR id run across was 59510 [01:49] Right. [01:49] wgrant: are you still hacking on https://bugs.launchpad.net/launchpad/+bug/575450? [01:49] <_mup_> Bug #575450: Archive:+copy-packages nearly unusable due to timeouts < https://launchpad.net/bugs/575450 > [01:50] lifeless: The next piece of work in that is bug #733071. [01:50] <_mup_> Bug #733071: Archive:+copy-packages slow when potential conflicts detected < https://launchpad.net/bugs/733071 > [01:50] But there is also work needed to speed up the UI, but I haven't analysed that yet. [01:50] wgrant: there is a stall condition here [01:50] Yes. [01:51] wgrant: if you split out a bug like this, please assign yourself to all components, or only leaf components [01:51] wgrant: you see why ? [01:51] Yeah, sorry. [01:51] no worries [01:51] bigjools pinged me about this morning when discussing the drop to 11 seconds [01:53] hes concerned about usability during release [01:53] That's +queue. [01:53] Not +copy-packages [01:54] wgrant: If my one-liner of evilness is right, we've processed 38k SPRs since the 15th. [01:54] StevenK: Sounds reasonably plausible. [01:54] Pity there is another 500+ k [01:55] wgrant: bah, emybrain [01:55] Speaking of 11 seconds. [01:56] 424 Time Outs [01:56] :( [01:57] You didn't want 424? [01:57] We had 252 yesterday. [01:57] So, no. [01:57] wgrant: The BUILDMASTER oops concerns me [01:57] Since the same thing happened yesterday too [01:57] StevenK: That normally just means the source has been superseded. [01:57] It often happens. [01:58] I thought jelmer had fixed that, but maybe not complete. [02:02] I guess EB and ED are also appservers? [02:02] EB and ED are edge appservers. [02:02] Ahh [02:02] They need more fire. [02:03] We need to get rid of potassium and gandwana. [02:03] Now. [02:03] The +copy-packages GET timeouts are all high non-SQL on gandwana and potassium. [02:04] lifeless: When are the new appservers happening? [02:05] wgrant: probably not till mthaddon is back [02:05] :( [02:05] elmo was checking with charlies/nafallo about the memory [02:06] Is the session queue normally sitting at 0? [02:06] ie. would it help to deprioritise gandwana/potassium instances? [02:06] cve:+index spiked [02:06] jcsackett: has a fix for that [02:06] He does. [02:06] is it landed? [02:06] No. [02:06] >< [02:06] Kanban says it's in review. [02:06] Checking it. [02:06] dropping the timeout [02:07] Excellent. [02:33] Wow, apparently windmill is fixed [02:34] rm? [02:39] have we done anyting to improve https://launchpad.net/ubuntu/+source/kde4libs/+publishinghistory ? [02:47] StevenK: did they use the great "rm -rf" debugger? [03:06] StevenK: Windmill is not fixed, but wallyworld fixed the broken test. [03:07] lifeless: My SPR.copyright fix will have improved that. [03:07] It still times out occasionally, though. [03:13] https://code.launchpad.net/~thumper/launchpad/blueprint-linked-bug-tasks/+merge/53734 anyone? [03:14] I have three other reviews which are the start of the pipeline [03:14] but they are trivial [03:14] and I'm tempted to self review [03:14] but if someone wants to look at them [03:14] here they are: [03:14] https://code.launchpad.net/~thumper/launchpad/bugtask-repr/+merge/53731 [03:14] https://code.launchpad.net/~thumper/launchpad/bugtask-tales-addition/+merge/53732 [03:14] https://code.launchpad.net/~thumper/launchpad/add-publishing-for-factory-distro-sourcepackage-bug-tasks/+merge/53733 [03:15] In bugtask-tales-addition you seem to be trying to reimplement structuredstring. [03:16] wgrant: what do you mean? [03:16] _make_title escapes stuff. [03:17] wgrant: I implemented it in the same way that the main link is generated [03:17] wgrant: I didn't think too hard about the implementation [03:17] Yes, and most of our code is buggy :( [03:17] is that bit buggy? [03:18] It's not buggy, but it's not a pattern that we want to perpetuate. [03:18] If you are calling cgi.escape, you are probably doing it wrong. [03:18] where is structuredstring? [03:19] canonical.launchpad.webapp.menu, or somewhere stupid like that. [03:19] Yeah, canonical.launchpad.webapp.menu.structured is the constructor. [03:22] hmm... [03:22] wgrant: Hm, do you know the diff? [03:22] StevenK: Which diff? [03:23] wgrant: wallyworld's that fixed the failing windmill test [03:24] StevenK: r12593 [03:25] wgrant: can you think of a better place than lp.services.utils for structured? [03:26] lp.app.utils [03:27] StevenK: it isn't really LP specific [03:27] I think lp.app is probably more appropriate. [03:27] But I'm not really sure. [03:27] SpamapS: ping [03:27] https://bugs.launchpad.net/launchpad/+bug/627974 - the url I got from you, did you get that from launchpadlib, or were you url hacking ? [03:27] <_mup_> Bug #627974: MaloneApplication:CollectionResource is slow/times out < https://launchpad.net/bugs/627974 > [03:29] wgrant: lp.app.browser.string ? [03:30] or lp.app.browser.structured [03:30] thumper: string, I think. [03:30] Mm. [03:30] I don't know. [03:31] it needs an interface module too [03:31] I'd not be happy putting it in lp.app.interfaces.launchapd [03:31] or launchpad even [03:31] I'd be happy to have the interface and implementation in a single file in lp.services.string [03:31] Indeed not. [03:32] and include escape and structured [03:32] But lp.services is not webapp-specific, so lp.services.string is wrong. [03:32] lp.services.escaping, maybe. [03:32] l.c.l.w.string then [03:32] But I'd prefer lp.app somewhere. [03:33] lifeless: we are trying to remove things from c.l.w [03:33] wgrant: lp.app with two files? [03:34] thumper: I know, but that seems pointless to me, the angst about it is dwarfed by the number production and deployment issues spent fixing moves [03:34] I can't bring myself to care about labels [03:35] the arguments for moving are that the old structure impeded splitting the tree, but the analysis for splitting the tree was wrong [03:35] * lifeless shrugs [03:36] perhaps we should just move canonical.launchpad.webapp to lp.app.webapp [03:36] :) [03:36] thumper: I am not sure if bugtask-repr is safe. [03:36] wgrant: why? [03:37] thumper: It potentially exposes the bug ID and target, if you manage to get hold of a BugTask through the webservice. [03:38] wgrant: the webservice handles launchpad.View [03:38] wgrant: and a bugtask view permissions filter to the bugs [03:38] wgrant: so not a valid concern I believe [03:38] thumper: The webservice handles launchpad.View for collections, sometimes. [03:38] having that repr certainly helped my debugging [03:43] 8 of todays top 10 OOPSes are fixed. Yay. [03:43] The next few are codehosting. [03:43] Blue squad sounds like a good one to take those :P [03:47] wgrant: I'm having a such a brain fade -- can you remind how to get the latest version of an SPR in a distroseries. [03:48] StevenK: That doesn't really make sense. But getCurrentSourceReleases might do what you want. [03:48] Depending on what you actually mean. [03:48] It is ambiguous in a couple of ways. [03:49] wgrant: So, Julian would like to delete the DSD is the derived series and parent series have the same version published. This makes sense to me, but I'm having a brain fade looking for the method to help me. [03:50] That's deleting the comment history. [03:50] Bad idea to do that so early. [03:50] You can possibly justify doing that once a series is done. [03:50] But not before. [03:51] Why? If something has been synced, the comments are now irrelevant/ [03:51] s/\//./ [03:52] StevenK: I want to know why it was synced. [03:52] Then you can look up the bug. [03:52] There wasn't a bug, because we are no longer in the dark ages. [03:52] The sync button has been implemented. [03:53] Good point. [03:58] how do we avoid the ValidPersonCache queries? [03:58] can we precache it? [04:01] thumper: list(getUtility(IPersonSet).getPrecachedPersonsFromIds(ids, need_validity=True)) [04:02] wgrant: I have the people already from a different join [04:04] although looking at this method, I may change it [04:06] thumper: are you filtering on person ? [04:07] lifeless: I'm looking at two timeouts [04:07] for spritns [04:07] Sprint:+huge-vocabulary? [04:07] one on +index seems to be getting valid persons [04:07] and +attendees-csv is just shite [04:07] ok [04:07] bug #'s ? [04:07] the attendees-csv could be trivially fixed [04:07] except for the ircnicknames [04:08] bug 735996 [04:08] <_mup_> Bug #735996: Sprint:+index timeouts < https://launchpad.net/bugs/735996 > [04:08] there isn't a bug for +attendees-cvs db counts [04:09] ircnicknames is a SQLMultipleJoin [04:09] so not sure how to precache the names for all the people :-( [04:09] You'll have to make it a cachedproperty returning a list. [04:10] wgrant: but that doesn't mean we can get them all at once [04:10] thumper: It does... [04:10] how [04:10] store.find(IRCNick, IRCNick.personID.is_in(personIDs) [04:10] grep around for pre_iter_hook [04:11] hmm... [04:11] I'll look around [04:28] jtv: perhaps you could comment on https://bugs.launchpad.net/launchpad/+bug/708875 [04:28] <_mup_> Bug #708875: AssertionError: More than 6 plural forms were submitted < https://launchpad.net/bugs/708875 > [04:28] lifeless: should be an unexpectedformdata if it happens from the web UI. [04:29] Seems a far-out guess that this is coming from the web UI, but I'm pretty sure I made the importer check for this condition way back when. [04:30] I think the check is wrong. [04:30] I looked at it yesterday and ran away. [04:30] There are only forms 0-5 [04:30] Which is 6. [04:30] Not more than 6. [04:36] The check doesn't even make sense to me. It's an "else" attached to a "for" loop AFAICS [04:36] Right. [04:36] That does make sense. [04:36] But it's not right here. [04:37] (the else block is executed if the loop runs to completion, without a break) [04:37] Gawd [04:37] Pretty much. [04:37] So yes, that explains the off-by-one [04:37] which is the absolute opposite of what *everyone* reads it as [04:37] The loop breaks when it hits the first plural form that is supported but is not in the form. [04:37] And when you submit exactly the maximum number of forms, it never does. [04:37] FFS. [04:38] Exactly. [04:38] But I thought this must have come up often. [04:38] Does it not? [04:39] wgrant: still working on bug 714414 ? [04:39] <_mup_> Bug #714414: unstack debian sid branches < https://launchpad.net/bugs/714414 > [04:39] Probably, yes, but plural forms are relatively rare, and only Arabic uses 6. [04:39] jtv: Right, but wouldn't it occur on every plural arabic translation, then? [04:40] Or is the last one uncommon? [04:40] Every complete plural arabic translation made in the UI, yes. [04:40] Given the debate around ubuntu-l10n-ar, I guess we don't have many arabic translators. [04:40] lifeless: Not really. [04:41] An upstream translation. or one uploaded by a translation team member, wouldn't have this problem. [04:41] I'm expounding on the bug. [04:44] wgrant: unassign? [04:46] is https://bugs.launchpad.net/launchpad-buildd/+bug/719162 deployed? [04:46] <_mup_> Bug #719162: [Natty] check-implicit-pointer-functions fails on natty, resulting possibly broken packages < https://launchpad.net/bugs/719162 > [04:48] lamont was looking at that earlier this week. We need an amd64 builder on staging before we can QA it. [04:48] So no, it's not yet deployed. [04:52] stub: hey [04:53] can you see how long the very big query in bug 722787 takes now on prod? [04:53] <_mup_> Bug #722787: Product:+filebug timeouts < https://launchpad.net/bugs/722787 > [04:53] I suspect the index repack fixed it [04:59] * stub tries to find a real query [05:01] wgrant: and are you doing 729064 ? [05:08] lifeless: Yes. [05:08] I can't even cut and paste the query without making terminal explode :-P [05:08] https://lp-oops.canonical.com/oops.py/?oopsid=1875O1575 has bigger problems than just timing out [05:08] stub: :P [05:09] love our ui [05:09] There are currently no open bugs. [05:09] https://bugs.launchpad.net/launchpad-project/+bugs?field.importance=Critical&start=225 [05:11] lifeless: So the insane query in that oops runs in 3 seconds atm. on one of the slaves. [05:12] stub: great,thanks [05:13] * lifeless closes [05:13] 224 critical bugs [05:13] tada [05:13] including 6 5-digit ones [05:14] stub: going to cook dinner; catchup after that? [05:14] sure [05:23] hi [05:24] re bug 719271, are there multiple threads per scanner process? [05:24] <_mup_> Bug #719271: Branch scanner jobs failing in bzrlib < https://launchpad.net/bugs/719271 > [06:20] stub: ping [06:24] lifeless: pong [06:24] skype? [06:28] https://staging.launchpad.net/successful-updates.txt is odd. [06:30] stub: https://dev.launchpad.net/LEP/ReliableDBDeploys [06:37] Can we move to Python 3 please? [06:37] How do you suggest we move Zope and Storm to Python 3? [06:37] Shh [06:38] Oh, you don't want problems, you want solutions? [06:39] I want non-awful Unicode. [06:39] I also want lucid_db_lp to fail sensibly. [06:39] Because its current failure is not sensible. [07:16] lifeless: tasque [07:30] wgrant: happier with the bug count now ? [07:35] lifeless: Mostly. [07:47] wgrant: there's a question about getting increased space for a ppa. who do i assign that to? [07:51] wallyworld: A LOSA, or poke a commercial admin [07:52] that doesn't sound right. we haven't been doing space increases for ages. can you guys already do that? [07:52] yourselves as in. ? [07:53] spm: if we can do it, i don't know how :-) [07:53] it's an admin option off the ppa itself. or was. [07:53] It needs a commercial admin or a LOSA, and there is approximately one active commercial admin. [07:54] i also have a question about a confirmation code being rejected when someone tried to create an account. assignee? [07:54] wallyworld: Ask them to file a ticket at the SSO support site. [07:54] that needs a level of sanity filtering first [07:54] Or reassign the question to canonical-identity-provider [07:55] wgrant: thanks. will reassign to cip. what's the sso support site? [07:56] https://forms.canonical.com/lp-login-support/ [07:56] thanks [08:01] spm: if it is an admin option on the ppa i can't see it. can i ask you to increase the space for the user? [08:01] wgrant: You were correct about Bug #736613 [08:02] (The ℃ bug since mup seems to have run out of blow) [08:03] Aha [08:03] * wallyworld has soccer training. back later [08:48] morning hackers [08:56] good morning [09:02] hi adeuring [09:03] hi jtv1! [09:04] StevenK: I realize it's late for you, so you may want to ignore this. I have minimal tests running for cron.publish-ftpmaster, but basically without any packages. Next on my wishlist is to make it produce meaningful data so I can test that I don't break it. [09:05] You managed to get it to run locally? [09:05] Yes === jtv1 is now known as jtv [09:05] In /tmp, not /srv/launchpad.net [09:06] The test should be able to reproduce it without any system changes. [09:07] Also, I changed it so it'll run against ubuntutest. Not sure yet if that's particularly useful. [09:07] Knowing the state of the sampledata, it's probably best to run against a completely new distro. [09:07] Or you are going to have fun when you start trying to publish stuff. [09:07] Yes, that's what I was hoping to do. [09:08] Problem is, I'm lost in the dark. [09:08] in a completely temp dir [09:09] all alone [09:09] and it's freezing [09:09] Don't pollute my terminal with your wide characters again. [09:10] my… what? [09:10] Oh wait, that was stub. [09:10] ah—nasty stub [09:10] Is ญ a wide character? [09:11] Anyway, wgrant, what would I have to set up? I'm guessing distro, distroseries, sourcepackagename, sourcepackagerelease, sourcepackagepublishinghistory… anything else? [09:11] Yes, but not as wide as the ℃ I was terrorised with earlier. [09:12] Wait, there's a single character for °C? [09:12] I can whine in ℉ if you would rather [09:12] How do I type those? [09:13] And if you think I'm bitching about the cold, you should hear my maid. [09:13] jtv: Distribution, DistroSeries, DistroArchSeries to start. Then you can create some stuff to publish... SPPHs (you may have to add files manually) to test publish-distro, and PackageUploads with PackageUploadCustoms to run through process-accepted to test dist-upgrader signing. [09:13] Holy cow, it's 18°! Insane! [09:13] You mean 18℃ [09:13] wgrant: quite a shopping list already… thanks [09:14] stub: At least there was no exclamation mark that time. [09:14] stub: yes, but I only know how to type that as °C [09:14] Is there a problem with an exclamation mark after ℃? [09:14] Aaaaaaaa [09:15] Or as the Danes would say, Åååå. [09:16] * jtv is beginning to wonder whether wgrant's terminal is perhaps not entirely prepared for some non-ASCII characters somehow. [09:16] Bug #736613 is the "℃" problem [09:16] http://people.canonical.com/~wgrant/bad-kerning.png [09:17] wgrant: thanks, that gives me something to aim for [09:17] if you use an irc client developed this century, it would probably work [09:17] it works in irssi [09:17] This irssi. [09:18] It depends on your terminal emulator and font. [09:18] +is [09:18] ok, irssi with real terminal and font :P [09:19] :( [09:19] ꒴ [09:20] wgrant: the files I may have to add manually are changelogs for the SPRs? Or something else? [09:20] jtv: SPRFs [09:20] Isn't that a view? [09:20] The view is SPFP [09:20] Oh [09:20] How could I have been so stupid? [09:20] I know, right. [09:22] I knew that would provoke a reaction :) [09:23] hi bigjools :) [09:25] helleau jtv [10:28] anyone around for a review? [10:30] o/ [10:31] (just waving, not volunteering :) [10:34] Project devel build #547: FAILURE in 4 hr 38 min: https://hudson.wedontsleep.org/job/devel/547/ [10:37] lp.services.job.tests.test_runner.TestTwistedJobRunner.test_timeout as usual. [10:37] oh, hi poolie :) [10:38] The Kanban board should pop a message when I move a card into the review lane that says "Are you sure, little man?" [10:41] gmb, with a picture of clippy? [10:41] Yeah :) [11:25] jml: ping [11:26] lifeless: pong [11:26] jml: https://dev.launchpad.net/LEP/ReliableDBDeploys [11:26] lifeless: yeah, I saw your earlier IRC comment about it. It's on the list. [11:26] jml: thanks [11:27] jml: also, I just replied to bug 655385 - with some ideas about solving a few of our bug challenges all at once [11:27] <_mup_> Bug #655385: Allow bug status change from Triaged only for bug supervisor < https://launchpad.net/bugs/655385 > [11:27] jml: I'd be interested in your thoughts on my comment (which was mailed in so possibly not visible yet [11:28] lifeless: ok [11:28] its a little adlib, but I felt the pieces going 'click' as I wrote === henninge is now known as henninge-lunch [11:32] man, its *really* hard to enter a tag that is a prefix of an official bug tag [11:40] jml: its there - https://bugs.launchpad.net/launchpad/+bug/655385/comments/14 [11:40] <_mup_> Bug #655385: Allow bug status change from Triaged only for bug supervisor < https://launchpad.net/bugs/655385 > [11:51] hmm, night all [11:51] bigjools: if you think some of the things I changed should still be critical, please just change them back: I was doing a big sweep as I said, and 100% accuracy is hard to achieve [11:52] lifeless: ok, I didn't want to be too presumptuous :) [11:52] bigjools: long as you include a reason (so that in 3 months I don't toggle again, blindly :)) it will be fine [11:53] jtv: there's a translation question i have no clue about. can i assign it to you? === matsubara-afk is now known as matsubara [11:54] lifeless: !!! [11:55] jml: ? [11:56] jml: you caught me just as I was about to walk away from the keyboard... whats up? [11:56] lifeless: oh, just that at least one of the bugs that were marked down had been previously marked Critical without comment. [11:56] lifeless: it's no big deal [11:57] jml: presumably by me? I do try to comment consistently, though I will admit I rarely bother when the bug is tagged oops or timeout from the start [11:59] lifeless: yeah. it was one or two out of about thirty, and not bugs I care about personally. [12:00] jml: if it was the getBranches on sourcepackage one, there was a comment already on the bug saying it no longer oopsed; I was lazy there ;) [12:01] http://webnumbr.com/.join(launchpad-oops-bugs.all,launchpad-timeout-bugs.all,launchpad-critical-bugs.all) === jtv1 is now known as jtv [12:57] hmm. [12:58] I've got some PPA stats [12:58] questions [12:59] - how many PPAs are there? [12:59] - how many packages are being uploaded to PPAs? [12:59] https://launchpad.net/ubuntu/+ppas [13:00] bigjools: awesome :) [13:00] There are also a few graphs on lpstats. [13:00] yeah w3as just searching for some good ones for jml [13:00] like https://lpstats.canonical.com/graphs/NewPPAsWithUploads/ [13:00] There aren't really any good ones. [13:01] That's the only interesting one. [13:01] https://lpstats.canonical.com/graphs/PPASourcePackages/ [13:01] do those "published sources" and "published binaries" numbers collapse versions? [13:01] published implies collapsed [13:02] PPAs don't let you publish more than one version [13:02] of the same package, I mean [13:02] If you mean distinct source versions? No. [13:02] If I have the same package in multiple series or PPAs, it will show up a few times in that number. [13:02] I guess what I mean is COUNT(DISTINCT (archive, sourcepackagename)) [13:02] ah, no idea [13:02] anyway I am desperately hungry [13:02] ok, thanks. [13:26] I'm getting a failure in stable running ./bin/test -cvv lp.services.job.tests.test_runner test_timeout [13:26] jml: Yes, that test fails on its own. [13:26] And sometimes in the full test suite. [13:26] it's consistent, and it's not like either of the failures mentioned on bug #505913 [13:26] <_mup_> Bug #505913: TestTwistedJobRunner.test_timeout fails intermittently < https://launchpad.net/bugs/505913 > [13:26] jml: Is it a failure to import _pythonpath? [13:26] wgrant: yeah. [13:27] wgrant: you also get this failure when running the test standalone? [13:27] It needs someone who knows that code to look at it. [13:27] I spent a couple of hours on it and made very little progress. [13:28] wgrant: I'm keen to have a try today, if I can deal with prior obligations. [13:29] wgrant: just to be crystal clear, you get the _pythonpath import failure when you run the test by itself locally? [13:29] jml: Yes. [13:30] jml: Working around that in ways that I no longer recall (possibly hacking site.py in the custom PYTHONPATH it uses) gets the same message as the spurious failure, but I was unable to work out how to get the output of the subprocess. [13:30] So I made the failure spurious again and ran away. === jcsackett changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | firefighting: - | On call reviewer: jcsackett | https://code.launchpad.net/launchpad-project/+activereviews/ [13:57] jml: I initially suggested doing what you considered, but could not think of a reasonable name for the method. [13:57] Er. [13:57] Swap suggested and considered. [13:58] wgrant: ahh, yeah. I can see how that would be a problem. [14:04] * bigjools waves at jcsackett [14:05] bigjools: publisher config schema review? :-) [14:05] jcsackett: yarp :) [14:05] looking now. === henninge-lunch is now known as henninge [14:17] jcsackett: will you have time to review https://code.launchpad.net/~sinzui/launchpad/person-merge-job-0/+merge/53706 [14:17] deryck: I've tried running it 30 times. It doesn't hang :/ [14:17] wgrant: *sigh* [14:18] deryck: Yes. [14:18] sinzui: i'll do it next. already had it marked for looking at today. [14:18] wgrant: I was afraid of that. [14:18] deryck: It's also only died a couple of times on Jenkins. [14:18] wgrant: can you point me at those builds? [14:18] And it doesn't die often on ec2 when only running WindmillLayer. [14:19] wgrant: also, I'm going to try it in a vm with lower resources and see if that helps cause it. [14:19] * deryck is grasping at straws [14:19] That's a good plan. [14:19] I ran out of straws a week or two ago. [14:21] I'm spending today on it and if I get no hangs, then will look at other options -- decoupling from Zope test runner or moving to Selenium. [14:22] abentley: I'm good for a js chat now. [14:22] deryck: cool. [14:22] https://hudson.wedontsleep.org/job/windmill/2/ https://hudson.wedontsleep.org/job/windmill/5/ https://hudson.wedontsleep.org/job/windmill/35/ https://hudson.wedontsleep.org/job/windmill/41/ https://hudson.wedontsleep.org/job/windmill/43/ are isolated spurious test failures. The build I thought was Windmill breakage was in fact the UEC slave going away. [14:23] leonardr: Is it possible to pass versioned annotations to export_write_operation (for example, if I want to export a write operation in devel but nothing else)? [14:23] deryck: So we have had 62 builds without a failure. [14:23] Yay. [14:23] Is it something about being in a full test run? Low resources? A race? Who knows... [14:24] gmb: yes, but you can't do it in export_write_operation, because the definition of a named operation takes place over multiple annotations [14:24] you need to use @operation_for_version() [14:24] Ah. [14:25] leonardr: So, do I do something like: [14:25] to publish an operation in devel and nothing else, at the bottom of the annotation stack you would have @operation_for_version('devel') [14:25] ... right. [14:25] :) [14:25] Cool. [14:25] THanks. [14:25] np [14:29] bigjools: so, this branch is just adding these fields, not refactoring anything to make use of them yet? [14:29] i only see addition, and setting/changing of the fields, not anything using them. [14:29] jcsackett: yep, just doing a small focused branch [14:29] bigjools: cool. [14:30] because I know that the code change to use this stuff will be pain ridden :) [14:30] bigjools: in the factory, since those are optional fields, is it entirely appropriate that they're always set? [14:31] jcsackett: interesting point [14:31] i don't know that it's actually a problem...just raising a possible different take on how it should work. [14:31] it would be impossible to set them to None [14:31] with that code [14:32] I'll change that, thanks for spotting [14:32] bigjools: r=me, with that. :-) [14:32] cheers! [14:34] sinzui: looking at your MP now. [14:34] Our reviews rock lately [14:37] i think moving to the "just use the review page as the queue" is a big win. [14:39] you weren't around in the old days when we used a wiki page ... [14:39] * bigjools shudders [14:40] that sounds like it would be problematic, yes. :-P [14:42] problematic was an understatement [14:43] and a review team of about 5 people [14:43] We had to locate a reviewer and prod each over several days to get approval [14:43] r=trivial was great for that :) [14:44] except when something broken and kiko looked at the branch and ask how anyone could claim the changes were trivial [14:50] Yippie, build fixed! [14:50] Project devel build #548: FIXED in 4 hr 15 min: https://hudson.wedontsleep.org/job/devel/548/ [14:52] wgrant: sorry, was on call. thanks for the build links. And I'm not sure honestly what it is about the entire run that causes it. [14:52] if the Jenkins build is just WindmillLayer, then perhaps it could be changed to run the entire suite + windmill. [14:55] sinzui: is there a need for a test on mergeAsync in the failure case? [14:55] i.e. when it returns None instead of a job? [14:55] ah, nevermind. that test exists, just in a different test file. [14:55] jcsackett: That is handled by the base runner and tests. the base defines an empty set of addresses. [14:56] sinzui: yes; i saw test_mergeAsync_success on test_person and so nothing corresponding, but it's handled elsewhere. :-) [14:58] hi sinzui -- can you look at this paste as a mid-imp sanity check for the menu problem we discussed yesterday? https://dev.launchpad.net/JavascriptUnitTesting [15:01] sinzui: r=me. [15:02] bac: thank you for updated the docs [15:03] jcsackett: I have an MP for you to review, if you'd be so kind: https://code.launchpad.net/~gmb/launchpad/make-+subscribe-play-nice-bug-735397/+merge/53839 [15:03] sinzui: oops, that was the wrong paste. :) [15:04] sinzui: i meant for you to look at http://pastebin.ubuntu.com/581613/ [15:04] but, yes, i was happy to update those testing docs [15:06] gmb: looking now. [15:07] Thankee kindly [15:09] bac: ugh. I do not think we should be injecting line-height into styles. The anchor is making a bad guess. Only

s have a line-height of 20px. Maybe this is why firefox still shows the icons misaligned in pages [15:09] sinzui: perhaps, but that isn't part of my change. [15:09] you cargo-culted it [15:09] sinzui: i'm happy to fix it at the same time, though [15:10] sinzui: i replicated the existing code, assuming it was correct, for the case i was adding [15:10] thanks TAL === matsubara is now known as matsubara-lunch [15:10] sinzui: the gist of my change to the page template is the conditional addition of "display:none" [15:11] bac: why do you use style instead of the invisible-link class. I think I would toggle between two classes [15:11] sinzui: good idea [15:11] we have supported invisible link since 2006 to make link testing easy. I think we can really use it for something else now [15:12] sinzui: otherwise a reasonable way to go? [15:12] yes. your implementation is what I would have done [15:12] I am worried about spurious line-heights now [15:12] damn [15:14] sweet. bac. there is only one occurrence. bac. try removing it and look at the page in firefox and safari. I think they will look the same now [15:14] lifeless: pong (no packet loss, but latency is close to interplanetary ;) [15:14] sinzui: thanks. i'll switch to use invisble-link. and i'll make the line-height fix [15:15] bac: firefox is still showing the sprites offset from where we intended them. I did not check that there was something overriding the line-height in the markup :( [15:16] sinzui: these would be for links such as in the global-actions portlet? [15:17] henninge: we're all sorted out for feature flag now? [15:18] deryck: the request is on LPS [15:18] henninge: ok, thanks. [15:19] bac: this template is used by "fmt:link", which is most links [15:21] henninge: the number in the feature flag has to be incremented above whatever the current highest number is. [15:21] jcsackett: I need to go and run some errands; I'll respond to your review comments and questions when I get back. [15:21] henninge: so the 1 is probably something like 20 now? [15:21] gmb: righto. [15:25] jml: ping [15:25] deryck: hi [15:25] deryck: hm? [15:25] henninge: I forgot what that attribute is called, but it has to be current value + 1. [15:26] deryck: oh, I did not know that. I think it's the priority. [15:26] yeah, that's it. priority. [15:27] henninge: rather, it has to be some value that isn't taken yet. ;) So everyone does current + 1. [15:27] deryck: I thought that was only relevant when you have multiple rules for the same flag. [15:28] it's to solve those ambiguities, I thought [15:29] henninge: yes, but there's a db constraint it has to be unique across all flags. the update will fail if not. it did in the past anyway. [15:29] deryck: hm, there are multiple rules with "1" and also with "0" in the current rule set. [15:29] https://launchpad.net/+feature-rules [15:30] henninge: ah, ok. So guess I'm wrong then. sorry for the noise. [15:31] sinzui: that line-height styling doesn't seem to have any effect. i've removed it and bumped it up to very high and see no difference in rendering [15:31] bac: in firefox? [15:32] Well regardless, we need to remove it. I was hoping that firefox would be fixed [15:33] sinzui: actually, i was only looking at the global-actions portlet, which uses the same styling [15:33] sinzui: it *does* have an effect on those in the involvement portlet [15:36] sinzui: on firefox, in the involvment portlet removing the 'line-height' styling does change the spacing between the lines (yay) but it does not appear to affect the vertical spacing of the sprite relative to the text. [15:38] bac: I do not see a style attribute in the involvement portlet links on https://launchpad.net/gdp [15:40] oh, no icon [15:41] bac: set this aside. I will look into it later [15:41] sorry for the diversion [15:42] sinzui: np. i'm easily diverted === salgado is now known as salgado-lunch [15:59] jcsackett: I really like your TestTeamParticipationMesh test. I was able to add two new tests, one using setMembershipData on each member, and the other using deactivateAllMembers. The second test fails as I expect. I will know my refactoring is done when both agree [16:00] sinzui: fantastic. === deryck is now known as deryck[lunch] [16:12] gmb: r=me. left a few questions in a comment, but those are strictly for my education, not issues with the branch. [16:13] jcsackett: Thanks. I'll respond to your questions in the MP now. === matsubara-lunch is now known as matsubara === salgado-lunch is now known as salgado === Ursinha is now known as Ursinha-lunch === deryck[lunch] is now known as deryck === beuno is now known as beuno-lunch [17:19] I may have a Windmill hang now! [17:32] deryck: Is that really something to get excited over ? ;-) [17:32] jelmer: it's the little things that make me happy :-) [17:37] jcsackett: ping [17:37] sinzui: pong. [17:37] jcsackett: I have a fix for team participation. Do you have a few minutes to mumble about it? [17:38] give me just a few moments to grab a drink, and i will be on mumble. [17:42] ah. stuck in a sleep. [17:43] I told you all sleep was evil. [17:47] just ask lifeless [17:48] oh wow [17:48] windmill imports time.sleep and uses it inside a while statement === fjlacoste is now known as flacoste [17:59] deryck: that sucks [18:00] jml: yes, that's a terrible, scary thing to do, IMHO. But turns out it's unrelated. Just frightening, but not causing the hang. [18:00] deryck: huh [18:00] deryck: very glad you're working on this, btw. [18:01] jml: looks like were stuck in client.open. still digging to know for sure. lot of backtrace to get through [18:01] and thanks! glad to be working on it myself [18:02] night folks [18:03] crap. lost my hung process. [18:03] night bigjools === beuno-lunch is now known as beuno [18:35] moin [18:38] g'night [18:39] Morning, lifeless [18:44] hi deryck [19:00] wgrant: jelmer: can either of you loook at https://rt.admin.canonical.com/Ticket/Display.html?id=42954 and answer toms debugging question? [19:02] abentley: hey, do you know - do the LP code import slaves need access to the librarian ? [19:02] lifeless: I don't know. [19:04] lifeless: looking... [19:04] jelmer: thanks [19:05] jml: if you haven't actually gone - did I make any sense in that bug post I pointed you at? [19:29] jcsackett: Can you review https://code.launchpad.net/~sinzui/launchpad/deactivate-all-members-fix-0/+merge/53885 today? [19:29] sinzui: sure. i'll take a look in just a bit. [19:30] sinzui: 458 lines? that's much smaller than i was expecting from your earlier concerns. :-) [19:34] jcsackett: Deleting lots of code is often small then editing it [19:34] jcsackett: hey, how is your cve:+index fix going [19:35] lifeless: made the changes you pointed out and it's out to land. [19:35] ec2 instance died without output on first try, second try seems to be going alright. [19:35] jcsackett: cool - third highest oops yesterday [19:36] lifeless: well, let's hope i got everything then. :-) [19:37] jcsackett: if you didn't, we can iterate === Ursinha-lunch is now known as Ursinha [20:07] sinzui: r=me, and thanks for that branch. i feel that it's a pretty big win. [20:07] jcsackett: thank you. [20:10] thumper: you around yet? [20:26] morning [20:26] jcsackett: am now, with coffee even [20:26] thumper: cool. i am looking at https://code.launchpad.net/~thumper/launchpad/bugtask-tales-addition/+merge/53732 [20:26] ok [20:27] i think it looks pretty good, but i wonder if now all Formatters will need to define _title_values? it looks like calling it is baked into the base class, but the base class has it as NotImplemented. [20:29] thumper: it might be better for the base form to just return None on _title_values instead, since that's handled gracefully. [20:29] jcsackett: that seems reasonable [20:29] can easily fix [20:30] thumper: with that change, r=me. [20:30] wgrant yesterday also suggested replacing the cgi.escape rubbish with "structured" [20:30] thumper: yeah, that might be better too. [20:30] jcsackett: that branch is one of a pipeline :) [20:30] thumper: dig. :-) [20:30] jcsackett: I only want to land the top [20:30] I just broke it up for review [20:30] it was getting kinda big [20:31] thumper: dig. [20:31] so, r=me on that little bit. :-) [20:31] thanks [20:43] ugh, checkwatches passwords are in lp-prod-configs :( [20:55] abentley: are translation sharing jobs actually running yet ? [20:55] lifeless: no. [20:56] abentley: I'm thinking of marking https://bugs.launchpad.net/launchpad/+bug/735954 qa-untestable then [20:56] <_mup_> Bug #735954: Translation merge job display < https://launchpad.net/bugs/735954 > === jcsackett changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | firefighting: - | On call reviewer: - | https://code.launchpad.net/launchpad-project/+activereviews/ [20:57] lifeless: I don't think "untestable" is strictly accurate. [20:58] lifeless: too-painful-to-test, perhaps :-) [20:58] abentley: indeed, and too little risk; I think we should check the page renders on qastaging [21:03] abentley: what url should I look at to see the sharing stuff ? [21:03] lifeless: translations.*/$SOURCEPACKAGE/+sharing-details. [21:05] abentley: I get a 404 on https://translations.qastaging.launchpad.net/ubuntu/+source/bzr/+sharing-details [21:06] ah, distro series source package [21:06] lifeless: yes, sorry. [21:07] https://translations.qastaging.launchpad.net/ubuntu/natty/+source/bzr/+sharing-details [21:07] seems to render ok [21:07] and i've clicked around and turned everything I could find on [21:08] abentley: that seems sufficient to suggest production won't be broken by the change [21:10] lifeless: does it show that a job's pending? [21:11] abentley: it says No upstream templates have been found yet [21:11] I guess that that is impeding it [21:12] lifeless: doesn't sound right. [21:12] abentley: darn, I'll undo my tag change then [21:13] abentley: what should we do to be confident this is deployable [21:13] [that is, that it won't regress or break anything] [21:15] sinzui: would you have the time and interest to review the branch for the menu links that we discussed this morning? [21:15] lifeless: it should say something like this: http://pastebin.ubuntu.com/581807/ [21:15] lifeless: the fact that it doesn't suggests that we may not have the correct revno on qastaging. [21:16] abentley: 12617 [21:17] I'll have a poke at unity instead [21:17] it should have strings [21:19] lifeless: I don't know what's going on. Perhaps the job has not been created. Perhaps the browser message is being suppressed somewhere. [21:19] abentley: I think its because there are no templates for upstream [21:19] lifeless: Oh, did you actually create a packaging link? [21:20] yes, but the upstream hasn't been imported [21:20] I don't recall making job creation conditional on that. [21:20] It requires the package to be an Ubuntu package, but I think that's all. [21:21] sinzui: you still there? [21:21] abentley: have a look here - https://translations.qastaging.launchpad.net/ubuntu/natty/+source/gtk+2.0/+sharing-details [21:22] abentley: tell me what you think [21:22] I am [21:23] lifeless: it looks as though this was an already-existing packaging link. If you just linked it now, then it should have the message. [21:23] sinzui: i have lost an email you may have sent about dealing with spam. there's a few open questions about removing spam links or accounts sending spam etc. if there a wiki page or email you can flick me which describes sop for that? [21:23] s/an email/any email [21:23] abentley: oh, ok. [21:23] Not yet. I may write it tomorrow [21:23] uhm, will look on needs-packaging [21:24] lifeless: look now. [21:24] abentley: what did you do? [21:25] sinzui: ok. so with accounts sending spam, i assume i should try and see if it's a one off (in case they have been hacked) or if it's an ongoing issue and hence disable that account? [21:25] lifeless: I deleted the packaging link and then re-created it. [21:25] wallyworld: I can find the email I sent. I believe we can see suspended users now so the process is simpler. suspend the user, then send an email to the user's preferred email address asking the him to confirm he has control of his computer, browser, and isp [21:25] abentley: ok, cool [21:25] so it looks ok to you? [21:25] lifeless: yes. [21:25] sinzui: will do. thanks. [21:26] abentley: thanks for the help [21:26] lifeless: you're welcome. [21:27] wallyworld: I just sent the email I think you remember. It has the text of the messages I send [21:28] sinzui: thanks. much appreciated. i need a better email filing system. there's sooooo much of it :-) [21:28] wallyworld: no you do not. I need to document what I have been doing for the last 15 months [21:29] sinzui: wow 15 months of dealing with spam! you poor soul. get it document so we all can help out better :-) [21:31] sinzui: did you see my request ^^? [21:31] bac: sorry I did not. I can review it now [21:32] thanks, sinzui! https://code.launchpad.net/~bac/launchpad/hidden_links/+merge/53911 [21:32] rockstar: whats jsoops? [21:35] lifeless: it's what Brendan Eich says when he reviews his life's accomplishments. [21:44] lifeless, it's our way of logging js errors. [21:45] rockstar: they get passed back to the server? [21:45] It's not really defined right now, but we're in the process of doing that. [21:45] lifeless, *kinda* It's still being defined. [21:45] rockstar: you might like to add anything constraints wise you come up with to dev.launchpad.net/LEP/OopsDisplay [21:45] The very basics of it is "have javascript write a img with the src="/jsoops?" [21:46] rockstar: I'm putting together a redo of the entire oops stack to be more agile and reusable across teams === matsubara is now known as matsubara-afk [21:50] rockstar: does this work of Y.on('error') or something? [21:51] mwhudson, well, we had a global event called one:error that has some extra handling (like providing feedback to the user). [21:52] ah ok [21:52] lifeless: Did you get the code import worker sorted out? [21:52] We don't yet have error handling inside YUI just yet, simply because it steps on our current jsoops infrastructure. [21:52] wgrant: the librarian usage question? its for the librarian uploader ha rt ticket [21:54] mwhudson, the idea is that if *anything* fails, even YUI, it's silently reported to our servers [21:54] I picked that up after talking to one of the gmail devs [21:54] beuno, unfortunately, YUI kills our existing jsoops stuff. [21:54] said that's how they managed to roll out so much crack to so many browsers [21:54] rockstar, yeah, need to give it some love again [21:54] beuno, already on it. [21:54] (well, kinda) [21:55] * beuno pretends to not have read that [21:55] beuno: lp will want that real badly [21:55] lifeless: can you mentor wgrant's review https://code.launchpad.net/~thumper/launchpad/add-publishing-for-factory-distro-sourcepackage-bug-tasks/+merge/53733 ? [21:55] beuno: I suspect my oops stuff will be highly relevant [21:55] * thumper waves at beuno and rockstar [21:55] splitters! [21:55] * rockstar waves at thumper [21:56] heh [21:56] hi thumper! [21:56] lifeless, yeah, I only spent a few days on it like 5 months ago, it needs some love and documentation to be able to be used company-wide [21:57] beuno: json format ? [21:57] lifeless, well, it sends it back as a url, so we don't need js to do any mangling (it did fail, so it can't be depended on) [21:58] once we finish making it play nice with yui, we need something in the backend to parse it [21:58] beuno: ok [22:01] thumper: https://code.launchpad.net/~leonardr/lazr.restful/forbid-reference-to-entry-not-published-in-this-version/+merge/53918 [22:01] not 100% happy with the implementation, but see what you think [22:02] leonardr: ok... [22:03] leonardr: with the VersionedObject addition, will this mean any locations in LP will need to be fixed? [22:03] leonardr: or is that wrapped in the entry code? [22:15] huwshimi: http://people.canonical.com/~curtis/out-4.ogv demonstrate call-to-action links create by an :after pseudo class [22:16] sinzui: Very nice! [22:16] sinzui: How do you make the arrows? [22:16] sinzui: Are they an ascii character? [22:19] huwshimi: http://pastebin.ubuntu.com/581829/ [22:20] sinzui: Nice work [22:22] huwshimi: I wanted to use something more semantic and implicit test..., but the pseudo class has to be on the parent element to hover correctly. So I used an explicit class [22:28] is LP on python 2.6 or python 2.7 ? [22:29] 2.6 [22:29] Lucid doesn't have 2.7. [22:29] :( [22:29] sinzui: I can hear you [22:36] https://code.launchpad.net/~thumper/launchpad/blueprint-linked-bug-tasks/+merge/53734 needs a mentor review :) [22:41] Project db-devel build #463: FAILURE in 4 hr 56 min: https://hudson.wedontsleep.org/job/db-devel/463/ [22:46] wgrant: did you look at the rt I mentioned? - the buildmaster xmlrpc thing [22:47] lifeless: The code import worker thing? [22:47] lifeless: That I asked you about an hour ago? [22:47] wgrant: I referenced two things [22:47] 08:00 < lifeless> wgrant: jelmer: can either of you loook at https://rt.admin.canonical.com/Ticket/Display.html?id=42954 and answer toms debugging question? [22:48] and [22:48] do the LP code import slaves need access to the librarian ? [22:48] yes, I think sop [22:48] lifeless: 42954 is code imports, not buildmaster. [22:48] we store the logs there [22:48] But yes, I think the import slaves need librarian access. [22:48] oh bah, it is [23:01] and no, not sorted [23:13] * thumper has to get out of the house [23:36] lifeless: What is blocking the HA librarian? Complete identification of all the required firewall holes? [23:42] yes [23:43] there is an rt for it, don't have the number offhand but you should be able to see it