/srv/irclogs.ubuntu.com/2011/08/03/#launchpad-dev.txt

wgrantThanks StevenK.00:16
wgrantYou are not yet imprisoned?00:17
jelmerWhat has StevenK done now?00:17
StevenKjelmer: On the call today I said I have a rental inspection, so if I'm not around for the rest of the day it's because I've been arrested for killing my landlord.00:17
* jelmer tries to imagine what a rental inspection is00:21
poolielike this: http://www.youtube.com/watch?v=aCiYmCVikjo00:21
jelmerheh00:22
StevenKjelmer: Where the landlord comes over to inspect the place you're renting to make sure you're taking care of it00:23
wgrantStevenK: It looks like the FileBugAPI XML-RPC call has been used around once in the last three months.00:23
jelmerStevenK: I don't think my landlord is legally allowed to do that00:23
StevenKHaha, around once00:23
pooliewgrant: coincidentally i was wondering this morning if there are or should be postmortems for rollbacks00:23
StevenKwgrant: Zero is around once?00:24
StevenKwgrant: It seems cronscripts/create-debwatches.py uses debsync?00:25
jelmerStevenK: while you're here.. can I add a branch to your queue?00:25
StevenKjelmer: I just reviewed one of yours00:25
StevenKjelmer: Or do you mean a different branch?00:26
jelmerStevenK: ah, race condition.. thanks for the review :)00:26
StevenKAnd create-debwatches isn't actually run00:27
StevenKOrsum00:27
wgrantNo, chromium, you may not have 7GB of RAM.00:30
StevenKBwaha00:31
wgrantStevenK: Right, I'm pretty sure that create-debwatches and update-debwatches have never been used.00:31
wgrantThey were written at the end of 2004.00:32
wgrantAnd haven't really been touched since.00:32
wgrantStevenK: Heh, look at r7675.771.200:34
wgrantOne of mine: "Port create-debwatches.py away from IDS.publishedBinaryPackages(). The script didn't work anyway, so I'm just going to pretend that I haven't broken it more."00:34
StevenKHaha00:34
wgrantSo, IMO you should delete it and update-debwatches.py, and probably trherefore debsync.00:35
StevenKsteven@liquified:~/launchpad/lp-branches/kill-cruft% bzr di | diffstat | tail -n 100:35
StevenK 7 files changed, 1890 deletions(-)00:35
wgrantWhat's removed?00:35
StevenKwgrant: http://pastebin.ubuntu.com/657575/00:36
wgrantStevenK: You've confirmed we have a bugzilla exporter?00:38
wgrantThis script was clearly written for the Ubuntu migration and probably hasn't been touched since, but best to check.00:38
StevenKwgrant: scripts/migrate-bugzilla-initialcontacts.py should probably die a firey death too00:40
wgrantProbably, yes.00:41
StevenKwgrant: You don't mean things like lp.bugs.externalbugtracker.bugzilla?00:43
wgrantNo.00:44
wgrantThat's the checkwatches backend.00:44
wgrantThe bugzilla exporter won't be in our tree.00:44
StevenKAh00:44
wgrantMeh, delete it anyway. There probably is one.00:45
StevenKHaha00:45
StevenKAs a serious question, do we actually care?00:46
wgrantNo.00:47
lifelessabout what ?00:56
wgrantThe ancient bugzilla import script.00:57
lifelessubuntu bugzilla to lp?00:57
lifelessdoes it even work now ?00:57
wgrantVery probably not.00:58
wgrantHence its imminent demise.00:58
wgrantlifeless: The XML-RPC FileBugAPI (https://help.launchpad.net/MaloneXMLRPC) has been used four times this year.01:09
wgrantCan we kill it?01:09
lifelesswe what now?01:09
wgrantHm?01:11
=== Ursinha is now known as Ursinha-afk
StevenKCan haz review?01:17
pooliewgrant: how much extra work does a rollback cost?01:32
poolie10m, an hour, a day?01:32
pooliei mean across losas and developers01:33
lifelesspoolie: you might like the mail I just sent01:34
lifelesspoolie: which puts some structure on this for the pre-deploy case.01:34
wgrantpoolie: LOSA time: should only be a few minutes, but I don't know how long they spend watching it.01:34
poolieah ok01:34
lifelesspoolie: things that have been deployed, and then rolledback incur the pre-deploy pipeline overheads *as well*01:34
pooliei was just writing up a few thoughts on this change01:34
wgrantWell, if we catch it before deployment, no LOSA time at all.01:34
lifelesspoolie: which change ?01:36
pooliemail-scope01:37
lifelesspoolie: so it never got deployed01:37
lifelesspoolie: no cost to losa01:37
poolieit got deployed to qastaging01:37
poolieno?01:37
poolieor is that not called 'deployed'?01:37
lifelessan unqualified 'deployed' means production only.01:38
wgrantThat's not "deployed"01:38
lifelesspoolie: the mail scope change falls directly under the performance tuesday mail I just sent.01:39
wgrantBlah.01:39
pooliewhat is that called then, "deployed to qastaging"?01:39
wgrantOr just "on qastaging"01:39
wgrantwallyworld: The Subscribe spinner on your Answers work is a bit odd.01:41
wallyworldi reused what was there already01:41
wallyworldwe can iterate if required01:41
wgrantIt doesn't appear until a few seconds after the click :(01:41
wallyworldi call the method to display the spinner inthe onclick01:42
wgrantHuh.01:42
wallyworldwell i thought i did01:42
wallyworldi will have to check01:42
poolielifeless: yeah it totally does01:43
wgrantIt seems to make an XHR request, show the spinner, then make another.01:43
wgrantlifeless: "20 minutes DEPLOY -> deployment -> fails or"01:44
wgrantIs that the 75 minutes or so to qastaging?01:44
lifelesswgrant: has it degraded?01:44
pooliei am trying to develop more sensitivity to risky landings by looking back at things that failed01:44
lifelesswgrant: but yeah, thats what I was refering to.01:44
poolieor, that could have been risky but worked01:44
lifelesspoolie: I think that we have a skewed environment because of two things:01:45
lifeless - long pipeline01:45
lifeless - single pipeline01:45
poolieyes, that's clearly true01:45
lifelessas we get more services with independent pipelines, and a faster pipeline01:45
lifelessthen we can iterate more in the direction responsive companies are talking about01:46
wallyworldwgrant: looks like you are right. it was supposed to be displayed before the first xhr call, but instead happens after. i'll raise a bug and fix. thanks01:46
wgrantlifeless: It only checks every half hour, and takes nearly an hour.01:46
lifelessI don't think applying their basic conclusions to us today will work at all well, though knowing their analysis methods / model for the problem is useful.01:47
wgrantwallyworld: Thanks! If possible, it mihgt be nice to also have it change the "(+) Subscribe" into "(o) Subscribing" like Bugs used to do, and hopefully will again soon.01:47
lifelesswgrant: please send an errata01:47
lifelesswgrant: I would appreciate that01:47
wallyworldwgrant: i thought about that approach but initially just wanted to reuse as much as possble what was there already01:47
wallyworldlifeless: might you have time to +1 that loggerhead mp?01:48
wallyworldhttps://code.launchpad.net/~xaav/loggerhead/export-tarball/+merge/6640801:48
lifelesswallyworld: I haven't re-read it yet01:48
wallyworldnp01:48
lifelesswallyworld: this week has been -very- bitsy. Its a high pri for me.01:48
wallyworldthat's cool. sorry for nagging :-)01:48
wgrantwallyworld: Good plan.01:49
lifelessnothing to apologise for01:49
lifelessI'm holding up someones contribution, which sucks.01:49
poolielifeless: sent; would appreciate your thoughts on it some time01:49
StevenKlifeless: You were looking over my kill-cruft MP to review it, or out of interest?01:50
* wallyworld puts on earplugs - electrician installing new solar inverter - *very noisy*01:50
lifelessStevenK: s/interest/horror/01:50
lifelessStevenK: :)01:50
lifelessStevenK: I think you should JFDI01:50
poolieoh no, the inverter's upside down!01:50
lifelesspoolie: I wanted to touch base with you anyhow; would you like a chat now ?01:50
pooliesure01:50
* wallyworld slaps forehead at poolie's bad pun01:51
pooliepots?01:51
lifelessI'm on the laptop, so can do sip or skype or whatever01:51
pooliesip01:51
poolie'currently unavailable'01:52
wgrantlifeless: So, I think we should just drop the XML-RPC method. It's been pretty much deprecated since the API was introduced, seems to be used once every couple of months, and whoever is using it can spend the 5 minutes rewriting their script, if indeed someone is actually using it.02:11
StevenKTBH, I agree with lifeless. Let's FF it first02:12
StevenKAnd soyuz-upload.txt is broken02:16
StevenKCan we delete that yet?02:16
wgrantWha?02:16
wgrantIt passed ec2..02:16
StevenKhttp://pastebin.ubuntu.com/657616/02:17
wgrantYeah.02:17
wgrantMaybe the race was real.02:17
=== jtv-afk is now known as jtv
=== jtv changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: StevenK, jtv | Critical bugs: 248 - 0:[#######=]:256
wgrantStevenK: I think I will just rip the poppy section out of soyuz-upload.txt02:37
wgrantSince test_poppy.py tests it all already.02:37
StevenKExcellent02:38
wgrantIn fact, this removes calls to poppy from outside lp.poppy.02:55
wgrantHandy.02:55
StevenK\o/02:55
StevenKDo you need a review?02:56
wgrantIt's only test changes, so I will self-review it.02:56
jtvhi wallyworld — just letting you know I'm on the mentoring request.03:00
wallyworldjtv: thanks!03:00
jtvI've been doing disappointingly little of that lately, so high time I caught up.03:01
lifelesswgrant: in your lxc's, have you been configuring up postfix ?03:20
lifelesswgrant: or something like nullmailer ?03:21
wallyworldwgrant: the subscription portlet's existing behaviour was to display progress  after the initial xhr call. i can't fix that for "subscribe someone else" or for when "subscribe me" displays an entry in the list but can fix it for answers as it is currently used03:31
lifelessI wonder if 122 /    3  Person:EntryResource:searchTasks is a regression03:37
wallyworldStevenK: want a very small review? https://code.launchpad.net/~wallyworld/launchpad/subscriber-portlet-spinner/+merge/7024703:58
StevenKwallyworld: r=me, but I'm not very comfortable with my JS-foo04:00
wallyworldStevenK: thanks. the change was just moving a few lines around, so should be ok04:00
lifelesserm04:09
lifelesshttps://launchpad.net/ubuntu/+source/apt/+index04:09
lifelessclick on the expanders04:09
lifelessthey all seem to go 'failed to fetch package details'04:09
lifelessand retry reloads the whole page04:09
lifelessis this known ?04:10
wgrantlifeless: I haven't.04:10
wgrantlifeless: Just whatever rocketfuel-setup installs, which is IIRC nothing.04:10
lifelesswgrant: recommends are on by default04:10
lifelesswgrant: so it pulls in postfix04:11
wgrantAh, no, I disable recommends.04:11
wgrantHalves the downloads or so.04:11
lifelesswgrant: right; see my mail to -dev :P04:11
wgrantI always add -o Apt::Install-Recommends=no, mostly for speed and clutter reasons.04:11
wgrantBut have never had the heart to do it in devel.04:12
* wgrant reads.04:12
wgrantHah04:12
wgrantErm.04:12
wgrantIsn't that top OOPS meant to be fixed?04:12
wgrantBut maybe the fix wasn't a rollback and the original rev wasn't marked qa-bad :(04:13
lifeless 145.73s  OOPS-2040CCW4   http://www.urbanvelo.org/04:13
lifeless   ?04:13
wgrant 943 LocationError: (<zope.browserpage.metaconfigure.SimpleViewClass from /srv/launchpad.net/production/launchpad-rev-13552/lib/lp/registry/browser/../templates/object-timeline-graph.pt object at INSTANCE-ID>, 'getCacheJSON')04:13
lifelessI suspect not a rollback, not marked bad.04:13
lifelessIn my mail about pipelines I've covered this sort of change FWIW04:13
lifelessI'd rather we never do such things.04:14
lifeless https://launchpad.net/ubuntu/+source/apt/+sourcepub/1635507/+listing-archive-extra04:14
lifelessis 404ing04:14
lifeless(from https://launchpad.net/ubuntu/+source/apt/+index)04:14
lifelesswgrant: right any bells? I think you refactored stuff in this area?04:15
wgrantPossibly the expander refactoring a couple of weeks ago.04:16
wgrantI think that should be /ubuntu/+archive/primary, not /ubuntu/+source/apt.04:16
wgrant    /**04:17
wgrant     * If a page wants to use this outside of an archive context then it04:17
wgrant     * can define LP.cache['archive_context'], which should be a04:17
wgrant     * full or relative URL to the context archive page required.04:17
wgrant     */04:17
wgrantSuspicious04:18
wgrantAnd indeed, that's set correctly on DSP:+index...04:18
wgrantSo why is it ignored.04:18
lifelessheh, you've got the bit between teeth huh.04:20
lifelessshould I file a bug for this, or do you want to ?04:20
wgrantBit between teeth?04:21
lifelesshttp://www.usingenglish.com/reference/idioms/bit+between+your+teeth.html04:22
wgrantAh04:22
StevenKBuild Source Stamp: [branch bzr+ssh://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel] 1358904:22
StevenKWGRANT!04:22
lifelessif a horse grabs onto the bit, the bridle can no longer control the angle of its head, because the teeth can take a -lot- of pressure vs the back of the jaw04:22
StevenKBlamelist: William Grant <william.grant@canonical.com>04:22
wgrantStevenK: The testfix landed hours ago!04:23
StevenKAh, it's soyuz-upload again04:23
wgrantAgain?04:23
wgrantThis is the build you complained about while it was in progress!04:23
StevenKThat was ec204:24
StevenKThat failure was from buildbot04:24
wgrantOh.04:24
wgrantI presumed you saw the failure on buildbot.04:24
StevenKJust then, from it's bleating mail04:25
StevenKwgrant: You've killed poppy ftp, can we nail https://bugs.launchpad.net/launchpad/+bug/29645 shut?04:26
_mup_Bug #29645: Weird requirement to poll the ftp.sock during the upload session <lp-soyuz> <tech-debt> <Launchpad itself:Triaged> < https://launchpad.net/bugs/29645 >04:26
wgrantStevenK: I plan to go through all poppyish bugs soon, yeah.04:27
StevenKCool04:27
wgrantlifeless: Ah!04:36
wgrantlifeless: It's a fresh regression.04:36
wgrantAaron's thing.04:36
wgrantIt now clobbers LP.cache instead of just adding new items to it.04:36
lifelesswgrant: urgh04:36
wgrantChecking to see what else is affected...04:36
lifelesswgrant: I'll let you file it04:36
lifelessI guess we need to revert prod ?04:36
wgrantMmm. QA-wise we're in an OK state.04:37
lifelesswe don't get js exceptions to count oopses04:38
wgrantWe should be able to deploy this fix in 10 hours.04:38
wgrantSo, maybe.04:38
wgrantI guess we should.04:38
lifelessso the fallout is unknown04:38
wgrantWe have to go back all the way, though.04:38
lifelessyes04:38
wgrantIt was my deployment, not the US one :(04:38
lifelessdo you happen to know the old good evno ?04:38
wgrantThe one before 13548... which was 1354304:39
wgrantThis was reported 22 hours ago, but I didn't notice it :/04:40
wgrantlifeless: This should be the only fallout of this type.04:42
wgrantThere are a couple of other templates which manipulate LP.cache, but they do it on domready and are working fine.04:42
lifelesswgrant: how was it reported ?04:43
wgrant16:58:00 < diwic> "Failed to fetch package details. Retry" <- is this a known launchpad bug?04:45
wgrantIn #launchpad.04:45
lifelessah, didn't miss a bug report.04:47
lifelessthanks04:47
wgrantBug #820174, anyway04:47
_mup_Bug #820174: Expanders on DistributionSourcePackage:+index broken by LP.cache changes <regression> <Launchpad itself:In Progress by wgrant> < https://launchpad.net/bugs/820174 >04:47
wgrantStevenK: Just failed for me in ec2 too :(04:50
wgrantYet I have an email here, "Test results: murder-poppy => devel: SUCCESS" :(04:51
StevenKEven with your change in devel?04:51
wgrantNo.04:51
wgrantI know that's not racy :)04:51
StevenKStrange04:52
wgrantOh?04:52
jtvwallyworld: I'm afraid I reverted to my usual nit-picky self on that branch.04:52
StevenKwgrant: That it failed, but you get a success message04:52
wgrantAh, no, you misunderstand.04:53
wgrantThe branch passed ec2. The test did not fail.04:53
wgrantIt landed.04:53
wgrantThen broke buildbot and every subsequent ec2 run.04:53
jtvStevenK: are you ready to exact sweet, sweet revenge for all the horrible things I've done to you?04:54
StevenKHeh04:54
wallyworldjtv: i'm looking now, thanks04:54
StevenKjtv: No, because I'm not yet in the same country as you ...04:54
jtvStevenK: you clearly have not learned to appreciate the full potential of the internet.04:54
StevenKI can't kick people in the face over the Internet.04:54
wgrantlifeless: Would you prefer a full revert, or https://code.launchpad.net/~wgrant/launchpad/fix-dsp-index/+merge/70249?04:55
wgrantSince it can skip ec2.04:55
lifelesswtf04:56
lifeless robertc@lucid-test-lp:~/source/launchpad/lp-branches/working$ ls /etc/postgresql/04:56
lifeless8.204:56
wgrantErm.04:56
StevenKFail04:56
StevenKwgrant: That MP looks good to me04:56
lifelesswgrant: is the other template thing fixed too already ?04:57
wgrantWasn't 8.2 removed just after hardy?04:57
lifelesswgrant: no freaking idea04:57
wgrantlifeless: Which?04:57
wgrantThe top OOPS from yesterday?04:57
lifeless lsb_release -a04:57
lifelessNo LSB modules are available.04:57
lifelessDistributor ID: Ubuntu04:57
lifelessDescription:    Ubuntu 10.04 LTS04:57
lifelesswgrant: yea04:57
StevenKpostgresql-8.2 |    8.2.7-1 | hardy/universe | source, amd64, i38604:57
jtvStevenK: I still say you're not appreciating (1) the full potential of the internet or (2) the awesome violent scale of my physical reaction to face-kicking attempts.  Hence my offer of safe retribution across the internet.04:57
wgrantlifeless: Was fixed in r1356004:58
wgrantlifeless: So the fix is on prod already.04:58
wallyworldjtv: you certainly are very detailed. i'll check in with curtis tomorrow. thanks again.04:58
StevenKwallyworld: s/details/pedantic/04:58
wallyworldlol04:58
StevenKjtv: How?04:58
jtvwallyworld: it's the risk of over-escaping date formatting that has me worried.04:58
lifelesswgrant: ok, I'm fine with rollforward if we're confident of no other sites.04:58
jtvStevenK: by reviewing one of my branches!  https://code.launchpad.net/~jtv/launchpad/bug-819674/+merge/7013504:59
StevenKAh, that branch.04:59
lifelesswgrant: we will want the original bug to be bad-commit flagged and this new one flagged rollback too though.04:59
lifelesswgrant: I think.04:59
wgrantlifeless: Yup.04:59
wallyworldjtv: yes, i think that's a fair question to ask04:59
StevenKI am not comfortable doing so, since I don't like the idea of the publisher being SIGINT'd04:59
wallyworldi suspect it won't be an issue but still.....05:00
wgrantStevenK/lifeless: Can I have a +1 on the MP?05:01
StevenKwgrant: r=me05:01
wgrantThankyou sir.05:01
jtvStevenK: fair enough.  It all ends up being nice & safe though.05:02
StevenKI don't trust it either05:02
StevenKHow can you be *certain* that the publisher is safe to Ctrl-C05:02
StevenKIt's a can of worms05:02
wgrantAs long as the backup switch happens only around publish-distro and not process-accepted, it's not too bad,.05:03
wgrantThe worst it can do is delay.05:03
StevenKBleh, and my kill-cruft branch has failed due to soyuz-uploads05:04
wgrant:(05:04
StevenKRETRIBUTION05:05
jtvFeels good, doesn't it?05:05
jtvAnyway, if wgrant says it's not too bad, it's probably not too bad.  :)  I mapped out and simplified the whole directory dance when I re-did publish-ftpmaster, and now nothing risky gets done in the "real" dists directory until all the hard work is done.05:07
StevenKjtv: I was talking about retribution for wgrant05:08
jtvOh.05:08
wgrantJust don't revert whatever process-accepted did, and you won't die.05:08
wgrantHmm.05:11
wgrantSo, confirmed, nothing else touches LP.cache in bad ways.05:11
wgrantThe rest of that rev may be good.05:11
StevenKThen land your fix05:12
StevenKIMO05:12
wgrantIt landed a while ago.05:12
StevenKThen speed up buildbot05:12
* wgrant points at lifeless and LXC.05:12
lifelesslooks like I'm ready to try parallel testing again, having beaten oneiric lxc into submission05:17
jtv! \o/05:18
wgrantlifeless: I see the restart problem has been diagnosed.05:18
lifelesswgrant: there are some terrible hacks under the hood, something about O makes them more visible.05:18
jtvwgrant: would you be able to review my branch perhaps, since StevenK is too chicken?05:19
wgrantMaybe.05:20
jtvMaybe thanks.05:25
=== jtv is now known as jtv-eat
wgrantjtv-eat: So this is just improving tests?05:27
wgrantThere seems to be no functional change.05:27
lifelesswheee05:32
lifelesslocalpackagediffs fail - generated two OOPSes :)05:33
lifelesshttps://launchpad.net/ubuntu/oneiric/+localpackagediffs?field.name_filter=apt&field.package_type=ignored&field.package_type-empty-marker=105:33
lifelessand hit refresh05:33
lifelessModule lp.services.propertycache, line 116, in __get__05:33
lifelessvalue = self.populate(instance)05:33
lifelessModule lp.registry.browser.distroseries, line 1081, in cached_differences05:33
lifelessstatus = package_type_dsd_status[self.specified_package_type]05:33
lifelessKeyError: u'ignored'<br />05:33
wgrantHmmm.05:35
lifeless(apt is currently generating a diff)05:35
wgrantThat page does have a thread-safety issue, but it's behind a flag and shouldn't cause this.05:35
wgrantIt seems to only affect some appservers.05:35
wgrantIt renders every so often.05:36
LPCIBotProject devel build #941: FAILURE in 6 hr 8 min: https://lpci.wedontsleep.org/job/devel/941/05:50
StevenKBah, there is an import violation that requires a storm fix05:50
wgrantExcellent.05:59
wgrantAll remaining QA is European.05:59
StevenKallenap and danilos, right?06:00
wgrantAnd rvba.06:01
=== jtv-eat is now known as jtv
jtvwgrant: yup, I just didn't realize it until I'd written the tests.06:20
wgrantThat explains my confusement.06:20
jtvAnd then the tests turned out still to be useful.06:20
jtvDamn, I thought I mentioned this in the cover letter.06:20
wgrantjtv: Do you know about assertRaisesWithContent06:21
wgrant?06:21
jtvYes06:21
wgrantSeems like you could use that in two of those tests.06:21
jtvProbably makes more sense to use that.  I'll fix it.06:21
wgrantIt cuts out about 5 lines from each.06:21
jtvYes… it doesn't really matter that it's the same exception object, I guess.06:23
wgrantNo. But if you use getUniqueString you can be pretty sure.06:24
wgrantAnyway, apart from that it looks fine.06:24
wgrantMore publisher tests are always good.06:24
jtvThanks.06:25
jtvThe change is pushing.06:25
wgrantYou did sort of mention that it was only test changes in the cover letter, but I sort of assumed that couldn't be the case so ignored it.06:25
jtvwgrant: meanwhile, I'm just about through the testing I can do for the new publish-ftpmaster, except I'm not sure it expedites security updates.  Maybe there's more you can think of.06:28
wgrantjtv: Not sure that it does, or suspicious that it might not?06:28
jtvSuspicious that it might not—except we didn't actually get around to publishing a security update, and I don't really know what to look for.06:29
jtvThen again, that may not be a blocker.  Can't drag this out forever.06:32
wgrantWell, you could just get two fresh uploads, copy one into security and one not, and check the mtime of the security pool and dists files are before the non-security pool and dists files.06:33
jtvThanks..06:35
wgrantIt's easy enough to check, and I can do it if you want.06:41
jtvwgrant: I'd be lying if I'd say I wouldn't want that — if only because you're so much more likely to spot any glaring mistakes than I am.  :)06:44
jtvIn other words, yes please!06:44
jtv(Please imagine better grammar when reading the above)06:45
* wgrant enters the molasses.06:45
wgrantStevenK: :(06:49
wgrantStevenK: It wasn't entirely file deletions.06:49
wgrantI am disappoint06:49
StevenKHaha06:49
wgrantjtv: You seem to have a diff in 10-sign-releases.06:53
wgrant #!/bin/sh -e06:53
wgrant 06:53
wgrant+exit 0 # XXX: DEBUG06:53
wgrant+06:53
jtvwgrant: that's just because the gpg won't work on dogfood.06:56
jtvWithout it, test runs will break.06:56
wgrantAh.06:56
wgrantHmm. Why is --post-rsync an option>?06:57
wgrantI am loving the sane timestamps in this log.06:58
wgrantI might set oneiric to CURRENT for a while to clear out the -updates queue.07:04
wgrantNFI how stuff got there :/07:04
jtvwgrant: it was an experimental feature… doesn't look particularly useful on dogfood, though unknown benefits in production.  This way we get to try things.07:05
wgrantAh, k.07:05
jtvWhen you say set oneiric to CURRENT, you mean on dogfood right?  :)07:05
wgrantI don't have privileges to do that on production, sadly.07:05
jtvIf you hadn't added the "sadly," you might still have stood a chance of convincing an admin.  :-)07:06
wgrantOK, release, security and partner uploads uploaded.07:07
wgrantNow to wait for them to build.07:07
wgrant:( partner hates me.07:09
wgrantAlso, mawson is slow.07:09
jtvHave you called the press or should I?07:11
wgrantMaybe we can steal gandwana and potassium for staging Soyuz or something.07:12
jtvwgrant: meanwhile, do you know the particulars of bug 659769?07:23
_mup_Bug #659769: should copy custom uploads to newly-initialised release <derivation> <lp-soyuz> <new-release-cycle-process> <soyuz-publish> <Launchpad itself:Triaged by jtv> < https://launchpad.net/bugs/659769 >07:23
wgrantjtv: Unassign.07:25
jtv?07:26
wgrantNot really fixable without completely redesigning the custom upload model.07:26
wgrantSince they are entirely untracked once the build is processed for the first time.07:26
wgrant(they're currently published when a PackageUpload is process by process-accepted, and then nothing is recorded about them)07:27
jtvThese are PackageUploadCustoms?  Do they get deleted?07:27
wgrantThey don't get deleted at the moment, no.07:27
wgrantBut we can't know what is still relevant.07:27
wgrantAll we can do is republish every PackageUploadCustom ever.07:28
wgrantExcept for the minor issue that translations tarballs are expired, so that will crash.07:28
jtvNo other heuristics?  Matching filenames or somesuch?07:28
* wgrant sobs.07:28
jtvAccess dates?07:30
jtvStatus of the attached PackageUploads?07:31
wgrantOnce they're DONE, they're DONE.07:32
wgrantThat is the end :(07:32
jtvAnd there's no way to determine that a PackageUpload supersedes an older PackageUpload?07:32
wgrantNope.07:33
jtvAccess stats on the Librarian file?07:34
wgrantThere's probably only ever one hit.07:34
jtvAnd they all have different filenames?07:34
wgrantMostly.07:35
wgrantwallyworld___: Will you be around to QA your thing in 3 hours?07:37
wallyworld___wgrant: sure07:37
wallyworld___i've been checking buildbot :-)07:37
jtvwgrant: what would that one single hit be?07:38
wgrantjtv: process-accepted putting it in dists/07:38
jtvAnd the rest of the use is from there then, I take it.07:38
wgrant2011-08-03 07:33:14 INFO    Processing upload hello_2.6-1df1~querulous1_source.changes07:38
wgrant2011-08-03 07:38:17 INFO    Committing the transaction and any mails associated with this upload.07:38
jtvWhere do these files go, anyway?07:38
* wgrant burns Soyuz to the ground.07:38
wgrantjtv: http://archive.ubuntu.com/ubuntu/dists/natty/main/07:39
wgrantEverything except binary-* and source is custom uploads.07:39
wgrantThere are also two other types of custom uploads which don't end up there: translations and static-translations.07:39
=== wallyworld___ is now known as wallyworld
wgrantBut those that you see there are basically unpacked tarballs.07:40
jtvThe translations tarballs are broken up instantly.07:40
wgrant(Until a year ago, tarballs unpacked without regard for whether the paths contain ../../ and spray files all over whichever archive the uploader wishes)07:40
jtvI remember making one of those code paths check that it's not trying to unpack devices…07:41
jtvBut anyway.07:41
wgrantAh yes, translation imports had that issue too.07:41
jtvIs there any way to delete custom uploads?07:42
wgrantrm -r07:42
wgrantThe way we currently copy custom uploads is with cp.07:42
wgrantYes, that is mutilating the one-step-from-live archive with cp and rm.07:43
jtvWhich, admittedly, sounds like fun.07:44
jtvEspecially with the dot-directory end-of-level baddie.07:44
wgrantHah07:44
wgrantlifeless: What are gandwana and potassium up to these days?07:45
jtvrm -- rf .<tab><enter><backspace><backspace><ctrl-C><ctrl-C><panic>07:45
lifelesswgrant: not sure; possibly going to be the staging scripts machine and achive machine.07:46
lifeless[qa]staging that is07:46
wgrantYay07:46
wgrantAs I was hoping.07:46
wgrantMaybe it will happen this decade :)07:46
wgrantBecause mawson is pissing me off.07:46
=== stub1 is now known as stub
=== stub1 is now known as stub
jtvwgrant: still, do the PUCs really need a redesign or just a bit of extra metadata so we can track and manage them?07:51
wgrantjtv: They need a *PublishingHistory table, probably.07:51
wgrantAs sources and binaries have had since ~the start.07:51
* jtv discovers it's his turn to sob07:51
wgrantI warned you!07:52
jtvStill, can't be as bad as BPPH07:52
wgrantI wonder if we can do away with scripts/ and cronscripts/07:58
jtvwgrant: are the Packages files I see for the installers also custom uploads?07:58
jtvThey're in binary-* directories, but not at the top level so not clear where they fall.07:58
adeuringgood morning07:59
jtvHi adeuring07:59
adeuringhi jtv!07:59
wgrantjtv: Sorry, debian-installer/binary-* are also not custom uploads.07:59
wgrantjtv: They're udeb indicies.07:59
jtvSo it's the translations stuff (which looks like it probably doesn't really need copying), dist-upgrader, and installer-<arch>08:00
wgrantRight.08:00
wgrants/translations/ddtp/, to avoid confusion.08:00
jtvWhere do the versioned directories inside the dist-upgrader and installer-<arch> come from?  Created by hand in the filesystem?  Or do the custom uploads go to a specific version?08:01
wgrantThe versions are in the custom upload filename, and current is a symlink that we keep up to date, I believe.08:01
jtvLooks like it, yes.08:02
jtvISTM we'd only want to copy custom uploads for the current versions.08:03
jtv(Which we may not trivially know, unless we have the symlink handy, but it'd make a big dent in the purging problem)08:04
wgrantPossibly.08:05
mrevellHello08:15
jtvhi mrevell08:22
jtvwgrant: looks like it's a bit simpler actually.  I see two kinds of filename: <purpose>_<version>_<arch>.tar.gz and <purpose>_<version>.tar.gz, depending on <purpose>.  I'll bet the last of these for any given (<purpose>, (<arch> or 'all')) in the previous series will take us a long way.08:25
wgrantIn an extremely distasteful manner, but possibly.08:26
allenapwgrant: Thanks for sorting out that rollback.08:26
jtvNo more distasteful than other places where the debian edifice relies on tarball naming conventions.  Make it (<format>, <purpose>, (<arch> or 'all')) for luck.08:27
jtvCheck whether the Librarian still has the file, and done.08:27
wgrantjtv: We make no assumptions like that outside the custom upload publisher.08:27
wgrantPutting that into series initialisation is awful.08:28
wgrantPossibly the easiest solution, but still thoroughly awful.08:28
jtvWell what produces the tarball names?08:28
wgrantPackages.08:29
=== almaisan-away is now known as al-maisan
jtvWhat aspect of packages produces the tarball names?08:31
wgrantjtv: It varies.08:44
jtvwgrant: taking just the dist-upgrader and the installer, what in the packages determines the tarball filenames?08:45
jelmeris canonical.launchpad.utilities.ftests.test_gpghandler.TestImportKeyRing.testHomeDirectoryJob known to be flaky?08:46
wgrantjelmer: Yes.08:47
danilosstub, about the DB patch, do I assign a patch number myself?08:47
wgrantjtv: debian-installer and update-manager08:47
stubdanilos: Didn't you already have one? Yes, assign it yourself is best.08:47
* danilos fetches ~launchpad/+junk/dbpatches08:47
danilosstub, ack08:47
=== StevenK changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: jtv | Critical bugs: 248 - 0:[#######=]:256
stubdanilos: Just don't use a -0.sql patch number, per newly added comments in the notes of that file.08:48
danilosstub, right, reading it now08:48
jelmerwgrant: thanks08:48
jtvwgrant: those have their own dedicated packageuploadcustomformats?  I think these two are the ones we _really_ care about; the rest at first glance seems more sort of optional.08:49
wgrantjtv: They do.08:49
danilosstub, do I use the existing "base" number (i.e. 79-0 is assigned, should I use 79-1)?08:49
lifelessdanilos: https://dev.launchpad.net/PolicyAndProcess/DatabaseSchemaChangesProcess#Patch ids08:50
stubdanilos: It doesn't really matter. Your patch number needs to be higher than any your patch depends on, but that rarely matters.08:50
daniloslifeless, that doesn't help answer my question, but thanks :)08:51
danilosstub, ok, thanks, I'll use 79-1 then08:51
lifelessdanilos: we don't use -0 at all now08:51
daniloslifeless, right, stub already explained that (and pointed at comments in the allocated.txt), I was wondering how do I choose the "base" (middle) number for -1, -2 etc.08:52
lifelessdanilos: could you add something to the file while you are there? I will add a note to the wiki reference I gave.08:55
daniloslifeless, sure, I will08:56
lifelessthanks!08:56
jtvcjwatson: got a moment to discuss possibilities for bug 659769?09:09
_mup_Bug #659769: should copy custom uploads to newly-initialised release <derivation> <lp-soyuz> <new-release-cycle-process> <soyuz-publish> <Launchpad itself:Triaged by jtv> < https://launchpad.net/bugs/659769 >09:09
danilosstub, can you please run http://paste.ubuntu.com/657714/ (it's the query you optimized yesterday) on qastaging? (if you are busy with the code hosting crisis as well, just ignore me)09:10
danilosstub, actually, ignore that, just got a response :)09:10
lifelessdanilos: hi09:22
lifelessdanilos: your https://code.launchpad.net/~danilo/launchpad/bug-814580-resubmit/+merge/70262 merge should be against devel - it has no db component09:22
lifelessdanilos: its only the schema changes that should land on db-devel09:23
daniloslifeless, it depends on a branch that has a DB patch09:23
lifelessdanilos: ah; well you'll need to remember to merge that to devel yourself when the DB patch is deployed.09:23
daniloslifeless, how can I know if the DB patch is deployed? devel/stable will contain it or is there something else that I need to watch out for?09:24
lifelessdanilos: the db patch will be merged to devel by stub / myself after its deployed.09:25
danilos(hopefully something more of the push-type instead of a pull type notification)09:25
daniloslifeless, ack09:25
lifelessI think we will want to mail the list when we do this too, for clarity09:25
lifelesseventually there will be a view on the appservers to check, and stub has plans for a report09:26
daniloslifeless, it would be even better if original committers are emailed directly as well, perhaps even automatically, but I am sure you guys will figure something smart out :)09:26
lifelessfirst pass is just to get the cycle time benefits09:27
lifelesssubsequent passes will add polish of various sorts09:27
=== danilos changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: jtv, danilos | Critical bugs: 248 - 0:[#######=]:256
LPCIBotYippie, build fixed!10:07
LPCIBotProject db-devel build #777: FIXED in 6 hr 10 min: https://lpci.wedontsleep.org/job/db-devel/777/10:07
jtvWould anyone mind if I removed makeDistroRelease, replacing all calls with makeDistroSeries?10:16
wgrantI've been tempted to do that for a Long Time.10:18
jtvAs a rule, I find that temptation isn't actually much cheaper than indulgence.10:20
adeuringlifeless: fancy a 200 diff review? https://code.launchpad.net/~adeuring/launchpad/bug-739052-3/+merge/7027210:20
adeuring(yeah, I know it's late for you...)10:20
lifelesstis almost early10:20
lifelessno diff yet :)10:20
lifelessadeuring: you decided not to handle desc, asc, asc, asc, desc as 3 expressions to reduce ?10:24
adeuringlifeless: well, I wanted a simple start :)10:25
lifelessok10:25
adeuringI know that we could try this too10:25
adeuringbut I'm wondering if we shouldn't first check how efficient the tuple expressions are10:25
lifelesssure10:26
=== al-maisan is now known as almaisan-away
stubwhat is the magic env variable for Storm statement logs again?10:37
bigjoolsLP_DEBUG_SQL10:38
bigjoolsLP_DEBUG_SQL_EXTRA if you want a trace with each one10:39
adeuringlifeless: you suggested in an older review to use "resultset.find(resultset.order_by)". Seems that this does not work:10:56
adeuringIn [11]: rs.find(rs._order_by)10:56
adeuringOut[11]: <storm.store.ResultSet object at 0x278a6d0>10:56
adeuringIn [12]: list(rs.find(rs._order_by))10:56
adeuringProgrammingError: argument of AND must be type boolean, not type integer10:56
adeuringLINE 1: ...de_private FROM Bug WHERE Bug.id IN (1, 2, 3) AND Bug.id ORD...10:56
adeuring                                                             ^10:56
lifelessadeuring: it was pseudo code :P10:58
adeuringlifeless: ...but i did not understand it ;)10:58
lifelessadeuring: I think I further suggested10:58
lifelessfind(<initial find clause> + (order by columns tupe) ...10:58
lifelessto get both the original data, and the precise data we need10:59
lifelessadeuring: however, your exception there is in the where clause not the select clause10:59
adeuringlifeless: resultset.find() only allows to extend the WHERE clause, but we can't extend the data returned10:59
lifelessadeuring: ah, shame11:00
lifelessadeuring: guess we need to fix that too11:00
adeuringlifeless: well, I think we can change the original query and used a DecoratedResultSet11:00
adeuringthat does not require any changes for storm11:01
lifelessadeuring: get_select_expr11:02
lifelesscan  be used too11:02
adeuringlifeless: Ah, ok. But is it worth the effort to tweak the result set?11:03
lifelessperhaps11:03
lifelessI dunno11:03
adeuringI mean, DecoratedResultSet are all we need11:03
lifelessbig picture what I was saying is11:03
lifeless- use the existing things to retrieve11:03
lifeless- add in the things the order orders on with Asc/Desc removed11:03
lifeless- interrogate only those added things11:03
lifeless-> we now support queries that return funky stuff, are grouped, etc.11:04
adeuringlifeless: ok, I see11:04
adeuringlifeless: I suspect that queries with aggregates might fail really bad with StromRangeFactory11:06
adeuringunless the aggregates are done in sub-queries11:06
adeuring...sub-selects...11:06
lifelessif its in order by11:07
lifelessit must be safe to have in the results11:07
=== almaisan-away is now known as al-maisan
adeuringwell, you could do something like select sum(col) from table order by col; but that's quite pointless...11:08
=== jtv changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: danilos | Critical bugs: 248 - 0:[#######=]:256
lifelessadeuring: I don't think you can :)11:11
adeuringmaybe ;)11:11
lifelessselect sum(col1) from demo order by col1;11:11
lifelessERROR:  column "demo.col1" must appear in the GROUP BY clause or be used in an aggregate function11:11
lifelessLINE 1: select sum(col1) from demo order by col1;11:11
wgrantwallyworld: Thanks.11:13
wallyworldnp11:13
wgrantallenap: Hi.11:13
wgrantrvba: Hi11:13
allenapwgrant: Hi :)11:15
lifelessadeuring: and if you group by it, you can select it :P11:15
adeuringlifeless: yeah11:15
wgrantallenap: Bug #809985 needs QA within the next 3 or so hours.11:15
_mup_Bug #809985: DistroSeriesDifferenceBaseView modifies shared objects <derivation> <qa-needstesting> <tech-debt> <Launchpad itself:Fix Committed by allenap> < https://launchpad.net/bugs/809985 >11:15
adeuringlifeless: back to get_select_expr(): that would work, I think, it it will require two more SQL queries to retrieve the memo values. Do we want this?11:16
allenapwgrant: I'm on it already, but thanks for the reminder nonetheless.11:16
wgrantallenap: Thanks.11:16
adeuringlifeless: argh... i wropte plain nonsense11:16
lifelessadeuring: have you had your morning coffee ?11:17
adeuringlifeless: not enough... I nearly poured the coffee directly into ash tray this morning...11:18
lifelessLOL11:18
lifelesswell, I have to crash, early start tomorrow.11:18
lifelessnight all11:18
adeuringnight lifeless11:18
wgrantNight lifeless.11:18
jtvhey danilos, I'm going EOD but if you want a bit of fun and you're out of good books: https://code.launchpad.net/~jtv/launchpad/we-prefer-distroseries-thank-you/+merge/7028211:22
jtvSomething tells me I'll be approving it myself though.  ☺11:22
danilosjtv, it looks pretty decent considering the diff has not been generated yet11:23
rvbawgrant: Hi11:23
danilosjtv, and I thought DistroRelease stuff was the *preferred* spelling for DistroSeries11:23
jtvdanilos: small linguistic note: it looks pretty decent *because* the diff has not been generated yet.  :-)11:24
jtvDistroRelease was the old spelling.11:24
jtvMark had that nice 30,000-line branch that did away with it, a few years back.11:24
wgrantrvba: You have some pending QA. and we will are hoping to deploy 55 or so revs in a few hours.11:24
danilosjtv, heh, ok, if you say so (regarding the linguistic note)11:24
rvbawgrant: ok, I'm on it.11:25
wgrantThanks.11:25
danilosbtw, I wondered about the state of the deployment report, looks pretty weird to me11:25
jtvdanilos: go on, ask yourself _why_ the diff hasn't generated yet.  :)11:25
wgrantdanilos: We reverted the last two deployments.11:25
wgrantdanilos: And found two bad revisions.11:25
wgrantSome of which were already deployed.11:25
wgrantdanilos: We should be good to deploy again in 3.5 hours, and should deploy as soon as it is possible.11:26
stubWhere is my long poll diff refresher dammit.11:26
wgrantdanilos: Only one item in the current buildbot run needs QA, and it's quick and documented in the bug, so you should be able to deploy just about as soon as it hits qastaging.11:26
stubdanilos: Short branch to review - https://code.launchpad.net/~stub/launchpad/trivial/+merge/7028411:28
* stub wanders off for a bit for kitchen detail11:28
wgrantbigjools: If jtv returns, could you inform him that expedited security processing works fine?11:33
bigjoolswgrant: he's EoD.  But thanks for letting me know.11:33
danilosstub, diff is still not showing up :(11:33
bigjoolsI think we're close to releasing this puppy11:34
wgrantbigjools: I think so.11:34
wgrantbigjools: The core stuff looks good, I believe, but I need to reexamine the hooks at some point.11:34
bigjoolswgrant: yeah11:35
LPCIBotProject devel build #942: STILL FAILING in 5 hr 49 min: https://lpci.wedontsleep.org/job/devel/942/11:39
danilosdiff generation seems dead11:49
wgrantdanilos: See #launchpad-ops11:49
wgrantAnd see the spam that should be in your inbox :)11:49
daniloswgrant: thanks (and I am only trying to review stuff, thus not getting the spam)11:51
wgrantHeh.11:51
wgrantWe'll hopefully have nagios checks on scriptactivity soon, but until then someone should watch for the emails.11:51
daniloswgrant: right, it's one thing we are particularly bad at (watching all the -errors emails)11:52
=== matsubara-afk is now known as matsubara
danilosstub, r=me, with a minor proposal which is entirely up to you (if you perhaps want to still update all of bug heat values with a single query, but you know better if that's worth it :))12:03
StevenKwgrant: Er, I think you broke devel12:18
StevenKwgrant: https://lpbuildbot.canonical.com/builders/lucid_lp/builds/1212/steps/shell_6/logs/summary12:18
wgrantStevenK: https://code.launchpad.net/~wgrant/launchpad/i-suck/+merge/7029812:32
wgrantStevenK: No diff, due to the ongoing incident, but you can get it from loggerhead.12:33
stubdanilos: ta12:35
StevenKwgrant: Right. Approved, please land12:38
wgrantI forgot that |nothing swallows exception.12:39
=== mwhudson_ is now known as mwhudson
StevenKdanilos: You are the last person who needs to do QA, r1358613:03
danilosStevenK, hasn't that been QAd already?13:05
danilosStevenK, oh, separate db-devel landing has made qa-tagger mess up my tags, we are all good13:05
StevenKdanilos: Until a bunch of new revs hit stable. Thanks!13:06
jmlthe diff generation issue wasn't announced on identi.ca :(13:11
danilosStevenK, thankfully, forthcoming testfix will put a stop to that! ;)13:12
StevenKdanilos: Which wgrant has already fixed.13:14
danilosStevenK, he should be sleeping, shouldn't he? :)13:17
StevenKdanilos: He fixed it before his bed time :-P13:21
henningeabentley: https://wiki.canonical.com/IncidentReports/2011-08-03-LP-failing-jobs13:33
=== danilos changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: - | Critical bugs: 248 - 0:[#######=]:256
=== Ursinha-afk is now known as Ursinha
=== al-maisan is now known as almaisan-away
mtaylorhey guys! did the bzr haproxy timeout get changed back down again?15:51
jelmerhi mtaylor16:02
mtaylorhi jelmer !16:02
jelmer(checking the haproxy status)16:03
mtaylorjelmer: I'm getting timeouts16:07
jelmermtaylor: this is when a connection is idle for more than X seconds?16:07
mtaylorjelmer: not full sure - still tracking down on my side16:07
jelmermtaylor: I think I saw your bug report yesterday about bzr handling that more gracefully16:08
mtaylorjelmer: https://jenkins.openstack.org/job/nova-tarmac/109707/console16:08
mtaylorjelmer: if you look at the bottom there, you'll see the "Connection to bazaar.launchpad.net closed by remote host."16:08
=== beuno is now known as beuno-lunch
=== beuno-lunch is now known as beuno
LPCIBotProject devel build #943: STILL FAILING in 5 hr 52 min: https://lpci.wedontsleep.org/job/devel/943/17:31
sinzuijcsackett, do you have time to mumble?18:30
jcsackettsinzui: i will in five minutes.18:30
lifelessmorning18:44
sinzuijcsackett, https://code.launchpad.net/~sinzui/+recipe/mmm-archive-manager-daily18:53
lifelessbac: hi18:54
bachi lifeless18:54
lifelessbac: just a very small note - it was great to see you identifying some dupes; could you please bias towards duping on the oldest one ?18:55
baclifeless: i would've but i was already working the other so i biased toward it18:55
lifelessbac: ah... so I've just messed things up for you by switching them around18:55
lifelessbac: I'll put them back.18:55
bacperhaps18:56
* bac will live18:56
lifelessbac: this isn't really documented anywhere, but I've a convention with timeouts of puting the page id in the title, it helps folk searching for the bug given a OOPS summary report.18:56
lifelessin this case I failed to update the subject on the newer one, and in not doing that I failed to notice it was a dupe :) - mea culpa18:57
lifelessthere, all back, and I've copied the subject over18:57
lifelesssorry for the interrupt!18:58
baclifeless: np!18:58
sinzuijcsackett, I am jinxed. The battery indicator just went belly up19:03
sixstringHowdy, #launchpad-dev. I'm happy to join the crew working on launchpad.19:37
SpamapSlifeless: here's a bug that consistently times out .. I suspect its a known issue: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/80489619:38
_mup_Bug #804896: gnome-settings-daemon assert failure: gnome-settings-daemon: ../../src/xcb_io.c:140: dequeue_pending_request: Assertion `req == dpy->xcb->pending_requests' failed. <apport-crash> <i386> <oneiric> <unity-2d> <gnome-settings-daemon (Ubuntu):Triaged by rodrigo-moya> <gnome-settings-daemon (Ubuntu Oneiric):Triaged by rodrigo-moya> < https://launchpad.net/bugs/804896 >19:38
lifelesssixstring: welcome19:40
lifelesswhats the OOPS id19:42
jmlsixstring: \o/20:14
jmlsixstring: welcome :)20:14
* sixstring is running rocketfuel-setup.20:15
sixstringYep. It's a long process. :)20:15
sixstringEsp. at this coffeeshop.20:16
jmlI'll bet!20:18
sixstring~300KB/s. I'd better go get another cup o' joy.20:22
sixstringIncidentally, I don't suppose rocketfuel-setup would recover if I halted the bzr checkout step, would it?20:23
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
lifelesssixstring: not well :)20:51
sixstring183MB so far, so good. Guess I'll just wait it out. :)20:52
Ursinhahello launchpadders :)21:29
Ursinhais there a way to bring someone's attention to a bug other than subscribing them to that?21:29
lifelessemail them a url ?21:30
Ursinhalifeless: I'll pretend you didn't suggest me that :P21:31
Ursinhalifeless: what I see people doing is assigning to the bugtask the one they want input from21:33
Ursinhathat's misleading21:34
Ursinha(from a defect analyst point of view)21:34
lifelessUrsinha: if the bug is blocked on that persons action, it seems accurate to me.21:34
Ursinhalifeless: right21:34
lifelessbut there is no 'ask for input from <person>' facility in LP itself.21:35
Ursinhaso assignee not just the one who's going to actually fix, but the one the bug is depending on... ok, makes sense21:35
UrsinhaI'm working on the ubuntu server bug triage process, so I saw that a couple of times21:36
Ursinhapeople don't actually follow bug reports when there are lots and lots of them21:37
Ursinhawell, you do, but that's you :P21:37
lifeless:)21:38
=== Ursinha is now known as Ursinha-afk
sinzuistevek, mumble23:03
LPCIBotProject devel build #944: STILL FAILING in 5 hr 52 min: https://lpci.wedontsleep.org/job/devel/944/23:24
sinzuiwallyworld, ,maybe the save event needs to explicitly set the NUM_SEARCHES to 023:55
wallyworldsinzui: perhaps, i'll look at that. i also want to see when it went bad23:56

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