/srv/irclogs.ubuntu.com/2012/07/30/#launchpad-dev.txt

wgrantStevenK: Morning00:31
StevenKwgrant: O hai00:36
wgrantStevenK: Your maintainer mail thingy needs QA00:37
wgrantAnd then we can deploy.00:37
StevenKwgrant: Yeah, I was been pondering how best to QA that while I was breakfasting.00:38
wgrantIt should be pretty simple00:39
wgrantAs you've basically just deleted code00:39
StevenKwgrant: If you file a bug under https://qastaging.launchpad.net/auditor, I shouldn't get a notification about it00:44
wgrantStevenK: ~auditor-team still has a structsub00:48
StevenKwgrant: Removed00:51
wgrantStevenK: https://bugs.qastaging.launchpad.net/auditor/+bug/939498 <- the creation notification should have gone to auditor-team, wallyworld and me; the comment to wallyworld and me.00:53
_mup_Bug #939498: rhythmbox-metadata crashed with SIGSEGV in _start() <apport-crash> <i386> <precise> <rhythmbox (Ubuntu):New> < https://launchpad.net/bugs/939498 >00:53
StevenKwgrant: Noted. Still waiting for Thunderbird to choke down the staging inbox00:56
wgrantStevenK: You've not used wallyworld's script to empty it?00:57
StevenKI have, there's still 6800 mails in it00:57
wallyworld_did you use the param to set the time period to clear messages? perhaps they are recent ones not cleared by default00:59
StevenKDefault is 2 days00:59
wallyworld_yes, so maybe those messages are < 2 days od00:59
StevenKEarliest message is 28/07 10:0001:00
wallyworld_which is the 2 day window01:01
wallyworld_so you need to specify to clear messages starting at 0 days ago01:02
StevenKwgrant: So it took qas long enough for the messages to hit the staging inbox. Three mails for the new bug -- and then one for the comment01:54
StevenKI guess wallyworld_'s structsub is close only01:55
wgrantAh, yeah01:56
wgrantMakes sense.01:56
wgrantSounds good to me.01:56
StevenKwgrant: I can put together a deployment for up to r15702 if you wish.02:03
wgrantStevenK: Indeed02:04
wallyworld_spm: i made a cake on the weekend - the one you sent me a picture of a couple of weeks ago. it turned out ok https://www.dropbox.com/s/irvxydgjw6eolcp/M1410015.JPG02:56
wallyworld_spm: i even saved you a piece https://www.dropbox.com/s/yxdksp1uhz450qf/M1410020.JPG02:56
wallyworld_so that should get me a few NDTs without begging02:56
spmwallyworld_: 1 spm: 0, so throughly outtrolled....02:57
wallyworld_well, this time anyway02:58
spmwallyworld_: and was it as good as it looks?02:58
spmit's looks terribly rich.02:58
wallyworld_spm: i think so. ask bigjools02:58
wallyworld_spm:  it is very rich, about 1kg of sugar all up02:58
spmbigjools: ^^ your considered opinion?02:58
spm!!!!!!!!!!!!!!!!!!!!!!!!02:58
wallyworld_900g maybe02:58
bigjoolsspm: it was so good that I didn't need dinner last night02:58
spmwallyworld_: was this bribery from your wife to get a cuddle with some new twins?02:58
wallyworld_spm: it was her birthday. it was bribery to get me a "cuddle"02:59
spmoic02:59
lifelessin other news03:33
lifelesspybars appears to have users.03:33
lifelessWho would have thought.03:33
lifelesscheck the download count on http://pypi.python.org/pypi/pybars03:33
wgrantUsers or Google?03:34
lifelessI'm fairly sure not google.03:35
lifelessI've seen much lower counts for other projects.03:35
lifelesse.g. http://pypi.python.org/pypi/oops_datedir_repo - 37003:35
lifelessand thats still got users (folk @ Canonical to be sure, but virtualenv users...)03:36
* StevenK stabs django05:28
StevenKTrying to use it with making use of django.test.TestCase is just an exercise in futility05:29
StevenKImportError: Settings cannot be imported, because environment variable DJANGO_SETTINGS_MODULE is undefined.05:38
StevenKSIGH05:38
nigelbStevenK: Wait, why are you using django?06:37
StevenKnigelb: https://launchpad.net/auditor06:37
nigelbooh. Nice.06:38
nigelbalso, yay django06:38
nigelb:P06:38
* nigelb runs06:38
=== jam1 is now known as jam
adeuringgood morning08:00
=== adeuring changed the topic of #launchpad-dev to: http://dev.launchpad.net/ | On call reviewer: - | Firefighting: - | Critical bugs: 4.0*10^2
lifelesswgrant: how much faster would you say the new bug search queries are?08:56
wgrantlifeless: 4208:57
lifelesswgrant: haha08:57
lifelesswgrant: really, you have no idea?08:58
wgrantPretty much.08:58
wgrantI know they're not slower.08:58
lifelessdarn08:58
wgrantWhy?08:58
lifelessI like being able to say what we've done to make things faster.08:58
wgrantYeah, certainly08:58
lifelessbut if its 'no slower', its pretty hard to point at and say 'booyah'08:59
wgrantIt's hard to measure 'cause of all the different cases, and the fact that the access control mechanism changed at the same time.08:59
lifelessI know :(08:59
wgrantI was also planning to do StormRangeFactory afterwards, but that didn't happen.08:59
wgrantThat would make the biggest difference.08:59
lifelessdoing less work :)08:59
lifelessdo you know off hand how long say, 'firefox' in Ubuntu takes ?09:00
lifelessit used to be 3s or so hot to count IIRC09:00
wgrantYeah, Ubuntu packages are where the biggest win is.09:01
wgrantSome of them will be more than 100x faster09:01
* lifeless tries09:01
lifelessso close09:01
lifeless1 → 75 of 111109 results09:01
lifelessjust two more09:01
lifelessand it will be epic09:01
wgrantHeh09:01
wgrant55ms for a count of firefox's open bugs09:02
lifelessoh, late eval faillll09:02
wgrant(could be much faster if we added another set of indices, to restrict to just open bugs. that was another plan alongside SRF)09:02
lifeless762.013ms to count forall bugs, 116 to get the batch09:03
lifeless1327.692ms for the batch for firefox itself, 592.421ms to count.09:04
wgrantEr09:04
lifelessthat looks like ~50% of the times we were seeing this time last year.09:04
wgrantWhat?09:04
lifelesswgrant: cold cache.09:04
wgrantOn which instance?09:04
lifelesswgrant: 'firefox' FTI in 'ubuntu' context.09:04
wgrantOh09:04
wgrantFTI09:05
wgrantYou didn't say FTI :)09:05
lifelessyeah, I did, I said "'firefox' in Ubuntu"09:05
wgrantI thought you meant firefox in Ubuntu09:05
wgrantie. https://bugs.launchpad.net/ubuntu/+source/firefox09:05
lifelessyeah, I saw that09:06
lifelessI would have quoted consistently for that09:06
lifelesse.g. not at all, or both.09:06
wgrantSo yeah09:06
wgrantFTI and count are going to be roughly the same length09:06
wgrantBecause they're pretty similar09:07
wgrantie. both terrible09:07
lifelesswe've switched index type already right ?09:07
wgrantBut it's not as problematic as, say, the default Ubuntu listing09:07
wgrantYes09:07
wgrantWhere the batch of 75 takes a few ms.09:07
wgrantBut the count takes a second09:07
wgrantAnyway, I need to eat.09:07
wgrantbbs09:07
cjwatsonlifeless: Any opinions on ending the beta period of https://blog.launchpad.net/general/beta-test-asynchronous-ppa-package-copies and rolling that out to everyone?  There was one bug, namely bug 1026976, which I fixed a week ago; and I've had a number of positive reports.09:43
_mup_Bug #1026976: Archive:+copy-packages creates job which oopses when async-copying from private to public archive <oops> <qa-ok> <Launchpad itself:Fix Released by cjwatson> < https://launchpad.net/bugs/1026976 >09:43
lifelesscjwatson: what failure modes do you think it could have ?09:43
bigjoolsdid you keep the synchronous exception for small numbers of packages?09:44
maxbThe async stuff is pretty poor at giving you feedback when a copy fails09:44
maxbI guess I should have bugged, I just assumed it was unfinished for now09:45
cjwatsonmaxb: When did you last check?09:45
cjwatsonbigjools: I haven't removed it yet, but I'd like to; that check is fairly bogus IMO09:45
bigjoolsit's stabbing in the dark, yeah09:45
cjwatsonThe code would be a lot more maintainable if it only had a single well-maintained path09:45
lifelesscjwatson: I'm hugely +1 on that.09:46
cjwatsonlifeless: Failure to copy at all, I guess; the actual backend code is fairly well-tested09:46
cjwatsonOr UI problems with presenting failures, but I thought that was fixed09:46
bigjoolsgiven that the backend forms part of ubuntu series opening :)09:46
lifelesscjwatson: sounds reasonable to expand it to me, long as you aren't going on leave tomorrow ;)09:47
maxbI seem to have lost the email concerned; but anyway; just displaying a message which says a copy failed, with no additional explanation, and emailing an oops code, isn't very nice09:47
cjwatsonmaxb: It's supposed to give an explanation of why - there's a screenshot example in the blog post above09:48
cjwatsonE-mailing an OOPS code indeed isn't nice.  I thought I'd made it e-mail an actual error.09:48
maxbI didn't get an explanation string in the web ui09:49
cjwatsonDid you click the expander arrow?09:49
maxbyes09:49
cjwatsonIf you know what package you were copying, and when, there's some faint possibility I might be able to investigate09:49
lifelesshow long ago ?09:49
maxbok, this was 6 days ago, and I've found the email now09:50
maxbLaunchpad encountered an internal error during the following operation: copying a package.  It was logged with id OOPS-952a0272d05f462844490a94901414e9.  Sorry for the inconvenience.09:50
maxbwas the full body text09:50
cjwatsonOne moment09:50
cjwatsonDamn, it's expired09:51
maxb24/07/12 23:5209:51
cjwatsonIs it possible that this was bug 1023372?09:51
_mup_Bug #1023372: Direct-copying an already-published package OOPSes <lp-soyuz> <oops> <Launchpad itself:Triaged> < https://launchpad.net/bugs/1023372 >09:51
maxbSounds quite likely actually09:51
cjwatsonBecause that's the one case I know of where the UI error would be entirely uninformative09:52
cjwatsonThe job log has expired from carob too09:52
wgrantYeah09:53
maxbAlthough, I believe I was trying to copy to un-delete a deleted package, i.e. previously published, not already-published09:53
wgrantNFI why we have only 5 days of retention there09:53
bigjoolscjwatson: one of my concerns is that all the PCJs go through a single job runner09:54
lifelesspossibly noone has removed the cowboy after we gobbled all of neems disk ?09:54
bigjoolscjwatson: and ubuntu series opening will dos ppa copies09:54
wgrantbigjools: No.09:54
wgrantbigjools: Initiali[sz]eDistroSeries doesn't use PCJs09:54
wgrantIt doesn't use the copier at all, in the Ubuntu case.09:55
cjwatsonIndeed, it uses PCRs instead09:55
bigjoolsI clearly need more sleep09:55
maxbOK, I've reconstructed the thing I was copying, it was bzr-upload 1.1.0-2~bazaar1~precise1 to bzr/proposed (and then I just uploaded a new version when the copy failed)09:55
bigjoolscjwatson: I still have the concern though09:55
cjwatsonStuff like Archive.copyPackage (e.g. SRUs, syncs from Debian) is our mass-testing of PCJs09:55
bigjoolssyncs will fuck it, yes09:55
bigjoolswhich is what I was thinking of and yet somehow typed wrong09:56
cjwatsonSyncs from Debian are the worst case I'm aware of; I think I've seen that go up to maybe half an hour of backlog, perhaps an hour09:56
cjwatsonmaxb: If you can set up a new example of it and get me an OOPS code, I'm interested09:56
wgrant(IDS doesn't actually use PCRs either -- it uses the cloner directly)09:56
maxbI'll see if I can retrace the process09:56
maxbBut in a few hours, at this point - I need to go to work now09:57
cjwatsonSo production jobs run on, what, ackee and loganberry?09:57
wgrantcjwatson: Right.09:57
wgrantcjwatson: lp:lp-production-crontabs is the usual reference.09:57
wgrantYou should be able to see that.09:58
cjwatsonAnd process-job-source locks for any given job source so you can't run >1 on the same machine easily.09:58
wgrantYeah, but that's easily fixable, as you've found09:58
wgrantIIRC we use a separate runner for the PCJs09:58
cjwatsonThat was more process-job-source-groups09:58
wgrantSo IDS won't be a problem there.09:58
cjwatsonIf you mean bug 83965909:58
_mup_Bug #839659: process-job-source-groups.py will starve itself if run with multiple overlapping schedules <Launchpad itself:Triaged> < https://launchpad.net/bugs/839659 >09:58
wgrantIf that's the one we filed after opening some series recently, indeed.09:59
wgrantIt's not.09:59
wgrantBut it may be the same thing.09:59
cjwatsonI filed bug 991876 separately.  I'm not sure that it's the same.09:59
_mup_Bug #991876: initializedistroseriesjob starved by other jobs <derivation> <new-release-cycle-process> <Launchpad itself:Triaged> < https://launchpad.net/bugs/991876 >09:59
wgrantRight10:00
cjwatsonNo, not as such.10:00
wgrantThey're pretty similar.10:00
wgrantBut different scripts.10:00
wgrantProbably the same fix.10:00
cjwatsonAnyway, the locking in process-job-source itself: what resource is it actually protecting?10:00
wgrantLaunchpad maintenance engineers' jobs, mostly.10:01
wgrantIt's just the normal script boilerplate.10:01
cjwatsonWell, it does seem at least somewhat real.  JobRunner.runFromSource fetches a list of jobs first and then tries to run them all; if it's racing with another runner it's not clear to me that it will behave sensibly.10:03
cjwatsonI suppose we could have a separate job source depending on whether you were copying to a distribution or a PPA, a bit like publishing.10:04
wgrantcjwatson: It should be fine.10:04
wgrantcjwatson: Doesn't it try to acquire the lease and skip if it can't, committing between jobs?10:04
cjwatsonOh, true.10:05
wgrantAnyway, the solution to non-concurrent code is to make it concurrent and fix stuff that breaks.10:05
cjwatsonStill, multiple runners won't magically avoid starvation, they'll just make queues clear more quickly.10:05
wgrantYeah10:05
wgrantThere's also celery10:06
wgrantI'm not sure what the queueing options are there10:06
cjwatsonIf the goal is for PPA copies never to be starved by distro copies, the answer is for those not to be in the same queue10:06
lifelessis the distro copy done as 20K separate jobs?10:09
lifelessOr one 20K long job ?10:09
lifelessor something in between ?10:09
cjwatsonYou mean syncs from Debian?10:09
cjwatsonSomething in between.  It uses Archive.copyPackages, which in principle could copy the whole lot at once, but in practice it does a little bit of advance checking for each package so it times out if asked to do too many in a single job; so our client for that bisects the list until it finds a set it can do in one go.  It tends to wind up being 100 or so per job.10:11
cjwatsonCopying precise to quantal (say), as wgrant observes, is a different system not in the same queue as PPA copies.10:11
lifelesswell, I mean this specific thing you 're worried about starvation thereof10:13
lifelesscelery lets us have multiple execution units for a single queue10:13
cjwatsonThen the answer is that the worst case I'm aware of for that tends to be around 20x100.10:13
lifelessso, - meh.10:13
lifelessI wouldn't spend any time on starvation for such a small set10:14
cjwatsonDuration-wise, I can't remember exactly but I think it took an hour or so to clear that.10:15
lifelessthats entirely tolerable (not desirable)10:15
cjwatsonMm.  There's no publicly-visible indication of queue length anywhere, which doesn't help.10:16
lifelessif you have time, enabling concurrent runners (w/celery) would be good, that would allow us to have e.g. 8 of them and have them mostly idle10:16
cjwatsonAs far as I'm aware the celery plumbing is in place, but are there any jobs using celery for real yet?10:17
lifelessnot on prod AFAIK, keeps failing qa10:17
cjwatsonI wonder if it would be interesting for the in-progress notification of PPA copies to say how long the queue is, or something.10:17
wgrantlifeless, cjwatson: Branch scan jobs have been celery'd on prod for a few weeks10:18
wgrantIt's some related followup work that I am chain-reverting.10:18
bigjoolsdoes any of this ever get announced?10:18
bigjoolsI try and keep up, but ...10:19
wgrantI only found out by finding that the logs were missing :)10:19
bigjools:/10:19
cjwatson<cjwatson@sarantium ~/src/canonical/lp-production-crontabs>$ grep -i celery *10:19
cjwatson<cjwatson@sarantium ~/src/canonical/lp-production-crontabs>$10:19
* cjwatson wonders how to tell10:19
wgrantcjwatson: celery isn't a cronjob10:19
wgrantThat's why it's better than cronjobs10:19
cjwatsonOh, right10:19
wgrantYou can see celeryd-job.log on ackee10:19
wgranthttps://launchpad.net/+feature-rules10:20
wgrantjobs.celery.enabled_classesdefault0BranchScanJob10:20
wgrantWell that wentw ell.10:20
cjwatsonWhere do the runners log?10:20
cjwatsonOh, sorry, read up10:20
bigjoolsnight all10:29
cjwatsonIs it likely to be deliberate that PlainPackageCopyJob.createMultiple doesn't call celeryRunOnCommit for each of the new jobs?11:14
wgrantadeuring: ^^11:15
adeuringcjwatson, wgrant: I don't know -- abentley workod on that part11:16
=== matsubara is now known as matsubara-lunch
=== benji changed the topic of #launchpad-dev to: http://dev.launchpad.net/ | On call reviewer: benji | Firefighting: - | Critical bugs: 4.0*10^2
jamcjwatson: did you ever get a chance to look at the Maverick filenames? Should I try to regenerate the list, or are you not going to be able to get to it for a while?12:34
cjwatsonIf you can generate something fresh, I can probably look this week, crappy Internet connection chaos notwithstanding12:34
cjwatson(My home internet connection has been down for six days)12:35
deryckMorning, all.12:58
rick_h_morning12:58
=== matsubara-lunch is now known as matsubara
deryckrick_h_, ping for standup.13:35
jamdpm: just a quick ping about where translations is at, did you get a chance to look at the imports13:35
rick_h_deryck: ah sorry, didn't get invite13:35
dpmhi jam, I just came back from holiday, but some community members manually approved and fixed the imports in the meantime. Once I've finished catching up, we'll open translations. I need to sync up with the other translations coordinators, but I think we can open and announce tomorrow or wednesday13:37
jamdpm: sounds good to me13:44
jamjust checking in on it13:45
jamI have no personal time frame in mind :)13:45
dpmok, thanks :)13:45
sinzuimrevell: do you have time today to talk about Sharing?14:03
mrevellsinzui, I sure do. My two meetings this afternoon have been cancelled, so I'm wide open.14:03
sinzuilets talk in 25 minutes.14:04
sinzui^ mrevell14:04
mrevellsinzui, ack, speak then14:05
rick_h_droidderyck sorry machine completely hung14:05
deryckrick_h_droid, np.  We eneded standup.  Will ping you shortly to chat more about mockups.14:06
rick_h_droidok14:06
deryckrick_h_ or rick_h_droid -- are you back up?14:24
rick_h_deryck: rgr14:24
deryckrick_h_, ok, let's chat in 5 then.  And bottom of hour.14:24
rick_h_deryck: k14:25
deryckrick_h_, let's use the standup hangout.14:29
timrcWe've been having intermittent build failures due to connection reliability issues with LP... has anyone else been experiencing this problem? Was there a disruption around was their a service planned (or otherwise) disruption around 2012-07-30 01:16:00 UTC ?14:56
timrcblah at my awesome editing skills14:57
czajkowskitimrc: we were due to have disruption at 11am UTC today but it didn't go ahead14:59
rick_h_deryck: ping, got a sec to hop back on a hangout?15:32
jamcjwatson: devpad: ~jameinel/cleanup-librarian/maverick-2012-07-30.log.gz15:43
jamis a new list of files15:43
cjwatsonAnyone want to comment on my suggested approach to bug 745799?16:37
_mup_Bug #745799: DistroSeries:+queue Timeout accepting packages (bug structural subscriptions) <timeout> <Launchpad itself:Triaged> < https://launchpad.net/bugs/745799 >16:37
=== deryck is now known as deryck[lunch]
=== deryck[lunch] is now known as deryck
rick_h_deryck: howdy18:01
deryckhey hey, rick_h_18:01
rick_h_deryck: got a sec?18:02
deryckrick_h_, oh, oops.  You asked while I was on another call and forgot to ping back.18:02
deryckrick_h_, sorry, dude.  let me grab headset and we can go now.18:02
rick_h_yea, np. Know it's busy but need to ask a few ?18:02
rick_h_ty much18:02
abentleyrick_h_: btw, it looks like we will prioritize private blueprints over private questions.18:03
rick_h_k18:04
deryckrick_h_, I think you is froze again :)18:11
rick_h_sinzui: ping, have time for a 2min sanity check hangout?18:27
sinzuirick_h_, yes18:32
sinzuirick_h_ https://qastaging.launchpad.net/launchpad/+admin18:41
sinzuirick_h_ http://www.youtube.com/watch?v=Vq6VsKuFY_o18:48
rick_h_sinzui: ty much18:48
abentleybenji: Could you please review https://code.launchpad.net/~abentley/launchpad/longer-mq-timeout/+merge/117324 ?19:14
benjiabentley: sure19:18
benjiabentley: done with your branch19:49
abentleybenji: ty19:51
benjiabentley: my pleasure20:05
sinzuibenji: do you have time to review https://code.launchpad.net/~sinzui/launchpad/register-project-maintainer/+merge/11733520:22
=== benji changed the topic of #launchpad-dev to: http://dev.launchpad.net/ | On call reviewer: - | Firefighting: - | Critical bugs: 4.0*10^2
maxbsinzui: In http://blog.launchpad.net/general/project-maintainer-can-see-private-bugs, people can lose access, not loose it :-)21:02
sinzuimaxb: alas. I have lost it21:02
sinzuiI will try to correct the blog21:02
wgrantabentley: Hi, https://bugs.launchpad.net/launchpad/+bug/1018235 needs QA -- can you do it or explain what needs testing?22:18
_mup_Bug #1018235: TestRunMissingJobs.test_find_missing_ready is disabled due to spurious failures <qa-needstesting> <spurious-test-failure> <test-system> <Launchpad itself:Fix Committed by abentley> < https://launchpad.net/bugs/1018235 >22:18
lifelesswgrant: where is the sso decoupling at?22:52
wgrantlifeless: Well, I shelved it while waiting for them to land my first branch22:53
wgrantlifeless: It took 3 months22:53
wgrantAnd then I forgot to pick it up again22:53
wgrantMaybe I should.22:53
lifelessthere is an RT at the moment around sso staging w teams not there etc etc22:57
lifelessit would help, I think :)22:57
* StevenK stabs mumble23:01
lifelesssinzui: how goes the blockage?23:03
StevenKwgrant: So I do think test_information_type_does_not_leak is a bong test. It structurally subscribes the product owner, creates a userdata bug for that product and then asserts they aren't notified.23:59

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