/srv/irclogs.ubuntu.com/2010/11/10/#launchpad-dev.txt

lifelessStevenK: hi00:22
StevenKlifeless: Hello00:27
lifelessbigjools asked me to chat with you about derivation logic00:30
lifelessand proffer my modest assistance if needed00:30
lifelesswgrant: are you around perchance?00:36
lifelessjames_w: hi01:38
james_whi lifeless01:38
lifelessI was wondering if there are test helprs for populating ppas already?01:39
james_wlifeless, SoyuzTestPublisher01:39
james_wit's not very pleasant though01:39
james_wthe factory has some stuff too01:39
lifelessI'm working on https://bugs.edge.launchpad.net/soyuz/+bug/67237101:40
_mup_Bug #672371: Archive:+packages timeouts <ppa> <timeout> <Soyuz:Triaged> <https://launchpad.net/bugs/672371>01:40
lifelessI want a query scaling test01:40
james_wbut you don't want "put 200 packages in this PPA"?01:40
lifelessso I need to put some packages (in different staes I guess) into a test ppa01:40
lifelessand I don't care about publishing an archive at all01:40
james_warchive = self.factory.makeArchive(purpose=ArchivePurpose.PPA)01:41
james_wfor i in range(3):01:41
james_w    self.factory.makeSourcePackagePublishingHistory(archive=archive)01:41
james_wsomething like that will give you the db gunk, and not do any actual publishing or anything01:42
lifelesssweet, giving it a spin now.01:42
james_wbigjools has hinted in the past that using the factory for soyuz is a bad idea, but I don't really understand why01:42
lifelessthe factory is a bit monolithing01:43
lifelesss/ing/ic/01:43
lifelessI'd like to split into different fixtures01:43
lifelessZOMG01:43
lifelessDifference: queries do not match: 25 != 3801:43
lifelessadding one package.01:44
lifelessthanks!01:44
james_wnp01:44
james_wyou can obviously change statuses with that01:44
james_wbut you might want to also add a scaling test for binary publications too01:44
james_wthough that might affect the main PPA page rather than +packages01:44
lifelessIts like playing whackamole with dyanmite01:44
james_wI think there's a makeBinaryPackagePublishingHistory or something too01:45
lifelessas long as we plug each hole, its an upwards trend.01:45
lifelessmy first focus is unfucking +packages today01:45
james_wright, but as you are there a test for binaries not scaling badly on +packages is probably worth 10 minutes01:48
lifelessjames_w: the problem isn't the test01:48
james_wif it passes you can leave it to catch problems in the future, if it doesn't you can decide whether to fix it, or just defer01:48
lifelessjames_w: its the fix.01:48
lifelessjames_w: I appreciate the moral support, but I'm optimising this for landing, nothing else at this point.01:49
james_wok01:49
lifelessjames_w: wgrant: Is there any existing class that models 'set of SourcePackageRelease objects' ?02:21
james_wlifeless, not that I know of, but that doesn't mean there isn't02:21
lifeless\o/ flat query counts on +packages04:01
nigelbwhoa 6500 bugs..... O_O04:22
lifelessheh04:30
StevenKlifeless: Right, so I'm looking at this graphing -- looks like the changelog is easily grapable from the librarian without having to pull apart the source package to get it04:36
lifelesswhats the processing model for this04:48
lifelessis it per-distroseriesdiff-package04:48
lifelessor are you doing many packages at once ?04:48
* StevenK peers at the db-devel failure05:07
StevenKlifeless: It will be per spr05:08
StevenKIt's been a while since I've played with the librarian, so I'm trying to recall how to get content out of a LFA05:08
lifelessStevenK: look at the merge proposal code05:10
StevenKlifeless: How does that help?05:17
nigelbouch, http://www.linuxjournal.com/content/ubuntu-bug-reporting05:25
wgrantlifeless: There isn't.05:31
lifelesswgrant: ECONTEXT05:51
lifelessStevenK: the merge proposal code gets the diff from the librarian in-appserver, then marks it up05:51
wgrantlifeless: There is no SPRSet.05:54
wgrantOr anything like it.05:54
wgrantStevenK: What are you graphing changelogs for?05:56
lifelesswgrant: thanks05:56
StevenKwgrant: Find the base version between Ubuntu and Debian06:05
wgrantRight.06:06
wgrantSo we will need to fix gina and run my script of dogfood-murder.06:06
StevenKIf we want to pull the changelogs directly from the librarian, and I think we do06:07
lifelesswell06:07
wgrantUnless you want to be unpacking source packages.06:07
lifelessunpacking sp's is nuts06:07
StevenKSource unpack just to graph versioning makes me cry06:07
lifelessputting this in the db would be better than using the librarian, unless you *know* that you'll only hit 4-5 versions on most packages.06:07
lifeless(because the db runs in-ram, the librarian doth not)06:08
StevenKWe can't say for absolutely certainy06:08
wgrantThe DB is crazy, though, as changelogs can be many megabytes.06:08
wgrantI imagine we should only need to look at the latest changelog.06:08
wgrantUnless someone's been doing Bad Things.06:09
StevenKNo, I can forsee us stepping back a few revisions06:09
wgrantHowso?06:09
StevenKPicture foo 1.4-1 in Debian, and foo 1.4-1ubuntu8 in Ubuntu06:09
wgrantStevenK: The 1.4-1ubuntu8 changelog will have 1.4-1 in it.06:10
wgrantDone.06:10
wgrantOne librarian read.06:10
lifelesswgrant: we don't need the whole cl06:12
lifelesswgrant: just the graph pointer to the next version that has a cl prefix06:13
wgrantlifeless: We in theory have something like that with changelog_entry.06:13
wgrantBut that relies on people using -v properly.06:13
wgrantWhich they don't.06:13
wgrantIn the normal case we should need to read one SPR's changelog from the librarian.06:15
wgrantI think.06:15
wgrantIs that really bad?06:15
lifelesswell06:16
lifelessits going to be diskio most of the time06:16
lifelessprobably tolerable06:16
lifelessnigelb: thanks for pointing that out, I've replied on it06:21
nigelblifeless: \o/06:21
nigelbIts nice to tell folks that people are working on the timeouts06:21
wgrantOTOH it's not really nice that it was left to rot for years :)06:22
lifelesswell06:23
lifelessI think the coding style being used was a big driver06:23
wgrantOh yes, certainly.06:23
lifelesswithout that being identified *and changed* it wouldn't matter how much one tried, it wouldn't be fast.06:23
=== almaisan-away is now known as al-maisan
stubtest_bzrsync.py has exploded on db-devel putting us in testfix.07:07
wgrantStevenK: Still around?07:27
wgrantAh, nevermind. gina is just confusing.07:28
adeuringgood morning08:45
stubI can't see any particular change that would have caused the bzrsync test failure.08:54
lifelesssweet - http://morepypy.blogspot.com/2010/11/snake-which-bites-its-tail-pypy-jitting.html08:56
mrevellHola08:59
bigjoolshey09:01
allenapMorning.09:06
wgrantbigjools: Is there a significant penalty in not caching the build behaviour?09:28
bigjoolswgrant: given the queries it's running, I expect so yes09:29
wgrant:(09:29
bigjoolswell, take a look for yourself ...09:29
wgrantCan we use the existing cachedproperty stuff which has proper invalidate hooks?09:29
bigjoolsthat's exactly what I was thinking09:29
wgrantThat was all fixed recently to not suck.09:29
bigjoolsI'm going to go over it with noodles09:30
wgrantA good plan.09:30
bigjoolswgrant: actually it's not *quite* the same as a cached property09:35
bigjoolsor is it ...09:36
wgrantbigjools: Ideally anything that changed the current job would invalidate it.09:39
wgrantBut that sounds hard.09:39
wgrantBut in the new code we probably invalidate the object lots anyway.09:39
bigjoolswgrant: see _setCurrentBuildBehavior which is for that purpose09:39
bigjoolswgrant: so my theory is that although the storm properties of self.builder are getting refreshed, the other ones are not09:40
bigjoolswhich makes no sense since self.builder is re-assigned09:40
bigjoolsbut as Sherlock Holmes said ...09:41
wgrantI forget exactly how Storm invalidation works.09:42
bigjoolsit uses pixie dust09:44
jmlwhat's up with the test failure?11:12
deryckMorning, all.12:08
bigjoolsmorning deryck12:11
bigjoolsjml, I re-created the b-m problem in a test \o/12:11
jmlbigjools: yay12:11
bigjoolsit's utterly bizarre though12:11
jmlbigjools: using actual APIs or by poking the db?12:11
bigjoolsre-fetching the builder object doesn't reset the behaviour12:11
bigjoolsactual API12:12
=== jml changed the topic of #launchpad-dev to: Launchpad Development Channel | Week 3 of 10.11 | PQM is open | firefighting: test failure on db-devel | https:/​/​dev.launchpad.net/​ | Get the code: https:/​/​dev.launchpad.net/​Getting
bigjoolsjml: it's caused by another builder building the job and then when it destroys the buildqueue, the scan of the old builder goes bang12:12
=== jml changed the topic of #launchpad-dev to: Launchpad Development Channel | Week 3 of 10.11 | PQM is open | firefighting: test failure on db-devel (since Nov 9, 1612UTC) | https:/​/​dev.launchpad.net/​ | Get the code: https:/​/​dev.launchpad.net/​Getting
jmlbigjools: interesting12:13
jmlbigjools: so is the problem that another builder builds the job, or that the old builder doesn't reliably handle another builder doing so?12:15
bigjoolsjml: it could be one of 2 things:12:16
bigjools1. the job on the old builder is not getting reset properly12:16
bigjools2. the pseudo-cached current_build_behavior property is not getting reset on the builder object12:16
bigjoolsI am highly suspicious of the latter, but now I have a test case I can work it out12:17
jmlbigjools: cool.12:17
bigjoolsI can just switch it to a @cachedproperty since lifeless fixed that12:18
bigjoolsjml: right, it's the latter.  Re-assigning the builder seems to retain a private property.  WTF?12:26
wgrantwallyworld: Have you seen DecoratedResultSet? Does it not fulfill your needs?12:27
wallyworldwgrant: i haven't come across that class yet. thanks for the pointer12:28
wallyworldi'm clearly still getting across the full api12:28
wgrantwallyworld: It's not actually in Storm core yet, AFAIK.12:29
wgrantwallyworld: It's in the Launchpad tree somewhere.12:29
wgrantlib/canonical/launchpad/components/decoratedresultset.py12:29
wallyworldwgrant: cool thanks. i'll take a look. it perhaps should be moved to storm i guess12:30
wgrantIndeed.12:30
lifelessjelmer_: bigjools: My branch has a test failure - I failed to delete the check that the ArchivePublication delegate can return a false list of builds, which should be irrelevant now that its given a complete answer rather than injecting a cheap build callback.12:33
lifelessI've forwarded the failure from ec2 to jelmer12:33
* lifeless goes back to sleep12:33
lifeless(and I'm on leave tomorrow/friday)12:33
jmlbigjools: I'm not sure what that means12:35
bigjoolsjml: me neither, I'm still debugging12:35
wgrantbigjools: The object will just be reretrieved from Storm's cache.12:36
bigjoolsI'm trying to work out if the current_build_behavior property is retained or recalculated12:37
jelmer_lifeless: Thanks, mine is still in progress12:42
bigjoolswgrant, jml:12:45
bigjoolsremoveSecurityProxy(getUtility(IBuilderSet)[builder.name])._current_build_behavior12:45
bigjools<lp.soyuz.model.binarypackagebuildbehavior.BinaryPackageBuildBehavior object at 0xd388650>12:45
bigjoolsI guess storm is returning not only the cached data but the actual object I already have :/12:45
* bigjools plays with cache invalidation12:46
jmlbigjools: are you sure the thing returned by getUtility(IBuilderSet)[builder.name] is a different object?12:46
jml(i.e. id(foo) != id(bar))12:46
* bigjools is checking12:47
bigjoolsjml: it's the exact same object12:47
bigjoolseven if I invalidate the cache it returns the same object12:48
jmlhow do you invalidate the cache?12:48
bigjoolsStore.of(builder).invalidate()12:48
jmlhmm. I wonder what that is supposed to do.12:49
bigjoolsI guess storm is jsut refreshing the object it already has for performance reasons12:49
bigjoolsso I should be able to fix this by invalidating that cached property12:49
* bigjools haxors12:49
jml        This prevents Storm from returning the cached object without12:49
jml        first verifying that the object is still available in the12:49
jml        database.12:49
bigjoolsit also re-reads the object from the db12:50
jmlwell, it might, but that's not what the docs say12:50
bigjoolsthey're incomplete then12:50
bigjoolsbut then this is storm docs ...12:51
jmlright, looking at it the implementation it calls _mark_autoreload, which (at a guess) tells storm to reload column values when they are next asked for.12:52
jmlbut there's absolutely no way storm could even know about user-maintained state12:54
bigjoolsyup12:54
bigjoolsbut the end user has no way of knowing that storm is going to return you the same python object that it already knows about12:55
bigjoolsso naive code like this will break12:55
jmlhmm.12:56
bigjoolsnow, how do I define an invalidation hook for storm12:56
jmlI was just asking that12:56
jmlself._run_hook(obj_info, "__storm_invalidated__")12:57
jmlthat's in _mark_autoreload12:57
jmlbigjools: ^12:57
bigjoolsjust found it :)12:57
jmlhow did this code work at all previously?12:59
bigjoolsnfi12:59
bigjoolsreally, nfi12:59
jmlI guess we're out of testfix now.13:02
* jml pours the first bowl of wrath onto an unsuspecting code base13:03
bigjoolshurray, my test passes now13:03
jmlcrap. apparently I have to re-authorize my ec2 app13:08
jmlleonardr: what does it mean when I have multiple applications with the same name & permission but different dates on https://launchpad.net/~jml/+oauth-tokens?13:10
leonardrjml: it probably means you cleared out your .launchpadlib directory and your client forgot about the earlier token and had to create a new one13:10
jmlleonardr: ok, that makes sense. should Launchpad clean up old tokens?13:11
jmlI guess we don't know for sure they are now unused13:11
jmlor, different computers or what have you13:11
leonardrjml: we've kicked around ideas, but none of them have been airtight enough to implement13:12
leonardronce we release the code for desktop integration, the situation should improve significantly13:12
leonardrsince there will be fewer tokens13:12
jmlleonardr: ahh yes.13:12
bigjoolsjml: I think my branch might benefit from a quick review, would you care to do the honours please?13:13
jmlbigjools: sure.13:13
jmldidrocks: hi13:13
jmldidrocks: I just landed a branch that removes the need to sign the CoC before uploading to a PPA13:14
didrocksjml: hey! awesome, that will make everything so much easier! :)13:14
jmldidrocks: I know you don't have much time to work on quickly (unity unity unity unity), but I thought you'd like to know :)13:14
didrocksjml: yeah, that's kind of you to hilight that :) (and you are correct about your assumption :))13:15
didrocksthanks a lot :)13:15
=== danilo_ is now known as danilos
=== Ursinha-brb is now known as Ursinha
jmlevery fricking time I need to do something with datetime I need to look up the API docs13:27
jelmer_jml: perhaps you should add another module for dealing with times and dates to Python ? :-P13:28
jmlgood idea!13:28
jmlbut I'll add it straight to the stdlib without actually using it in live code first13:29
jmlbecause standardizing on well-tested, commonly-used code is unpythonic13:29
jelmer_ah, I see you've got experience in this area13:29
=== jelmer_ is now known as jelmer
jmlding ding ding!13:54
deryckgmb, question about bug 485627, if you have a sec14:21
_mup_Bug #485627: Prompt user to subscribe when marking a bug as duplicate <email> <qa-ok> <story-better-bug-notification> <ubuntu-qa> <Launchpad Bugs:Fix Released by gmb> <https://launchpad.net/bugs/485627>14:21
gmbderyck: Shoot.14:21
deryckgmb, do we now *not* subscribe a user to the master bug via the duplicate?14:22
marssinzui, ping14:24
gmbderyck: Well, you're still showed as subscribed via dupes in the UI, but I don't think you get notification about the master bug unless you subscribe to it directly any more.14:24
sinzuihi mars14:24
marsHi sinzui.  I was hoping you could help me with an account registration question14:24
=== adeuring1 is now known as adeuring
marssinzui, I just created a second account, using my work address, for some work I am doing.  I used the login/register link to create the account - it seems to have gone fine14:25
deryckgmb, ah, ok.  So we have some cleanup around that then.  I'm thinking of the bug from jam about not having a direct link any longer.14:26
gmbderyck: Yes, I think there's some cleanup needed.14:27
marssinzui, I just received a mail that says "If this was you, perhaps you've forgotten your password?", otherwise "If not, someone may be trying to impersonate you.".  I have *not* received my mail with my confirmation code and/or link.14:27
deryckgmb, I think we should drop the subscriber from the web ui, preserve the old text about "the dupe is at LINK", and then add the new additional notice:  "You are not subscribed, if you want to, go to LINK"14:27
sinzuimars, are you saying that U SSO did not know about the other address, and Launchpad did not either, so Lp created a profile when U SSO said you logged in?14:27
sinzuimars, okay,14:27
marssinzui, I hit "Log out" on Launchpad before doing this14:27
sinzuimars, U SSO know a lot of email addresses. I believe it knows every email address that Lp knows via replication14:28
gmbderyck: That would also mean that we don't have to hit the API for subs-from-duplicates for each bug page, which would be nice.14:28
sinzuiso you did not register14:28
deryckgmb, would it?  We would still need to show current and past subscribers from dupes, right?14:28
marssinzui, ok.  I am worried, because from my perspective as a user, Launchpad just slapped me for trying to register a second account using my existing address.14:29
deryckgmb, or are we not sending duplicate subscribers emails at all any more?14:29
sinzuimars, you have not talked to Lp!14:29
gmbderyck: OICWYM. What's a past subscriber from a dupe? Someone who was subscribed via a dupe but now isn't?14:29
sinzuimars, as I keep saying, registration, login, and reset are U SSO. those pages and emails are not Lp14:29
gmbderyck: Honestly, I'm not acutally sure now. Maybe we are but we're just sending it with the "Subscribe to the master bug" footer.14:30
marssinzui, ok, but I used the green Launchpad login screens on login.launchpad.net - again, from my perspective, I have only been working with Launchpad.14:30
sinzuimars, yes, that is why I keep send emails to fix this. You have not and when users go directly there to register with lp, they are *not* redirected to real Lp to login...the profile is not created14:31
deryckgmb, ok, so I think we need to find out for sure.  and then do cleanup.  Let's use bug 673203 to track this.14:32
_mup_Bug #673203: Duplicate email sends link to +subscribe <email> <regression> <Launchpad Bugs:Triaged> <https://launchpad.net/bugs/673203>14:32
gmbOk14:32
deryckgmb, since I'm stuck on lazr-js still, would you mind including that in your "bugs I'm working on until deryck is done" list? :)14:33
gmbderyck: Sure, no worries. Can you add a card for it to the bugs lane? I'll take a look once I'm done with this blasted test that I'm trying to write.14:35
marssinzui, ok.  I am sorry to hear the experience has those problems, and glad to hear that you know what is happening.  I was just looking for some help finding a way to register my account, not to accuse.14:35
deryckgmb, sure, thanks!.  on the bugs backlog, or the task lane for the story?  I'm not picky either way myself.14:37
sinzuimars, visit U SSO and login as old identity, view the email address that you cannot use. logout. register with an unknown email address.14:37
gmbderyck: Task lane would make more sense, actually14:37
deryckgmb, ok will add it now14:37
gmbcool14:37
* gmb -> afk to run an errand; bbiab14:38
marssinzui, ok, I'll do that.  Thank you for your help.14:38
jmlbigjools: you know that thing with twisted xmlrpc that you had to monkey patch?14:57
jmlbigjools: I just landed the fix upstream14:57
bigjoolsjml: \o/14:57
bigjoolsI forgot what it was patching now14:57
jmlthe xmlrpc client14:57
jmlto make sure it disconnects properly14:57
bigjoolsoh and hugs for fixing glob imports!14:57
bigjoolsthat's the badger14:57
jmlbigjools: ta, but I really just put the cherry on top of a cake made by others. sinzui's been working at it for months14:58
bigjoolsmy heroes14:58
deryckgmb, allenap -- checkwatches hasn't run for two days according to the errors emails.  Should we be concerned?14:59
=== matsubara is now known as matsubara-lunch
flacostejml: i'm on mumble15:08
allenapderyck: Yeah, probably.15:18
allenapderyck: Can you direct me to what you're looking at?15:18
deryckallenap, do you get emails from script-failures?15:19
deryckallenap, I fwd'ed you a mail.  Do you mind chasing it up with a losa?15:20
=== salgado is now known as salgado-lunch
allenapderyck: I do get them, but I mark them as read immediately! I keep them only for reference (one which I forgot I had until now).15:26
allenapderyck: I'll chase it down.15:27
deryckallenap, thanks, I appreciate it.15:27
gary_postersinzui, you probably saw my request for a reviewing mentor for benji.  Someone from Registry would be my first choice, if you or EdwinGrubbs are willing and able.  Is that a possibility?15:40
sinzuigary_poster, I will be mentoring jcsackett next week. I will ask EdwinGrubbs. He is at a conference this week15:43
EdwinGrubbsgary_poster: I can start on it after the openstack conference.15:43
gary_posterEdwinGrubbs, thank you!15:43
gary_posterand thank you sinzui15:43
sinzuiEdwinGrubbs, I just reviewed your branch.15:44
EdwinGrubbssinzui: thanks15:44
gary_posterI'll reply to my email requesting a mentor.  Thanks, I really appreciate it, EdwinGrubbs.15:44
bacgary_poster, EdwinGrubbs: hurrah.  thanks edwin.15:49
gary_poster:-)15:49
=== matsubara-lunch is now known as matsubara
=== beuno is now known as beuno-lunch
=== salgado-lunch is now known as salgado
LPCIBotYippie, build fixed!16:39
LPCIBotProject devel build (207): FIXED in 3 hr 43 min: https://hudson.wedontsleep.org/job/devel/207/16:39
=== beuno-lunch is now known as beuno
=== elmo_ is now known as elmo
=== benji is now known as benji-lunch
=== benji-lunch is now known as benji
=== al-maisan is now known as almaisan-away
rockstarderyck, hi18:45
lifelessjelmer: hi, I'm really not here, but how is it going ?18:46
deryckhi rockstar18:48
rockstarderyck, how goes the lazr-js battle?18:48
deryckI hope you have windmill magic in your pocket18:48
rockstarderyck, :(18:48
deryckIt's playing in ec2 again.18:49
lifelessflacoste: do you know?18:49
deryckrockstar, I think one of the issues was without fetchCSS: false used globally, yui was attempting to go offsite for CSS, this 404s, the test runner got into thread contention, and tests started failing.18:50
rockstarderyck, ah, yeah, I just ran into that here.18:50
rockstarderyck, I think this was a change in 2.2.18:50
deryck3.2?18:50
rockstarYeah, that's what I meant.18:51
rockstar(I'm tired...)18:51
deryckno worries :-)18:52
deryckrockstar, how is yui conf?  Fun and useful, I hope.18:52
rockstarderyck, very much so.  I wish we could have had more people go.  I went to a workshop yesterday that gave me the desire to delete most of lazr-js.18:54
rockstarderyck, I'll be typing up a thorough report on the way home.18:55
deryckyeah, I would have loved to have gone.18:55
deryckwe've learned a lot as we've gone along, but yui devs view js the crockford way.  Would be nice to absorb some understanding of that more fully.18:56
flacostelifeless: last i saw was the tag qa-ok being applied to the bugs18:57
rockstarderyck, funny you should say that... I'm sitting next to the Crock right now...19:01
rockstar(He's wearing purple sneakers)19:02
deryckall the cool js hackers do19:02
rockstarWell, at least the Yahoos19:03
jamChex: ping, for great justice! (question about lp-forking-server and getting testools upgraded on bzr's pqm)19:09
lifelessflacoste: ok, so we haven't deployed it19:12
flacostelifeless: i don't think so19:12
flacostelifeless: not according to LPS19:14
lifelesshttps://devpad.canonical.com/~lpqateam/qa_reports/deployment-stable.html doesn't show a fix19:15
lifelessand its not in pqm19:15
lifelessand there's no qa-ok on https://bugs.launchpad.net/soyuz/+bug/67237119:15
_mup_Bug #672371: Archive:+packages timeouts <ppa> <regression> <timeout> <Soyuz:Triaged by lifeless> <https://launchpad.net/bugs/672371>19:15
lifelessflacoste: I promised Lynne I'd really have a day off today.... are you able to figure out where its up to and either deploy 11887 (take the faulty rev off) or get the fix 'out there' ?19:19
flacostelifeless: 11887?19:20
lifeless11888 is faulty19:20
lifelessI started a thread on lp-dev about it19:20
lifelessits making ppa/+packages pages timeout19:20
flacostelifeless: is it deployed?19:21
lifelessyes19:21
flacostelifeless: ok, i'll handle this19:21
lifelessI'm checking devel in case buildbot is currently munching on it19:22
flacostelifeless: do you have any scripts to prepare for a nodowntime roll-out?19:25
lifelessflacoste: I've sent a followup mail just now.19:25
flacostelifeless: adding bug numbers, moving stuff to Fix released, etc.?19:26
lifelessflacoste: none at all; I've filed bugs for the bits I think are reasonable to automate.19:26
flacosteok, so it's all manual for now19:26
flacostethanks19:26
flacostelifeless: enjoy your day off19:26
lifelessthanks19:26
lifelessthe thread name is 'possible regression on bug 672371'19:26
_mup_Bug #672371: Archive:+packages timeouts <ppa> <regression> <timeout> <Soyuz:Triaged by lifeless> <https://launchpad.net/bugs/672371>19:26
flacostejelmer: around?19:28
lifelessflacoste: I'll forward you the test result too19:29
=== flacoste changed the topic of #launchpad-dev to: Launchpad Development Channel | Week 3 of 10.11 | PQM is open | firefighting: - | https:/​/​dev.launchpad.net/​ | Get the code: https:/​/​dev.launchpad.net/​Getting
LPCIBotProject devel build (208): FAILURE in 3 hr 16 min: https://hudson.wedontsleep.org/job/devel/208/19:55
LPCIBot* Launchpad Patch Queue Manager: [r=jml][ui=none][bug=671242] Ensure that the custom19:55
LPCIBot_current_build_behaviour property on Builder is invalidated19:55
LPCIBotwhen Storm invalidates the database values. Fixes the19:55
LPCIBotbuildd-manager so that it doesn't disable builders erroneously19:55
LPCIBotdue to code tracebacks.19:55
LPCIBot* Launchpad Patch Queue Manager: [r=gmb][ui=none][bug=667340] Add a new 'fixverified' status mapping19:55
LPCIBotfor Trac external bug trackers. Maps to 'Fix Released'.19:55
LPCIBot* Launchpad Patch Queue Manager: [r=mars][ui=none][bug=621090] fix content type on two JSON views19:55
LPCIBot* Launchpad Patch Queue Manager: [r=mwhudson][ui=none][bug=384831,19:55
LPCIBot539496] Do not re-export anything from19:55
LPCIBotlib/canonical/launchpad/interfaces/__init__.py. Explicitly19:55
LPCIBotregister webservice code.19:55
LPCIBot* Launchpad Patch Queue Manager: [r=mars][ui=none][bug=673015] Allow people to upload to PPAs without19:55
LPCIBothaving previously signed the code of conduct.19:55
=== matsubara is now known as matsubara-afk
=== Ursinha is now known as Ursinha-afk
deryckbye, all.21:03
jmlthumper: ping21:11
thumperjml: hi21:11
thumperjml: I normally have the standup around now, but wallyworld doesn't seem to be here yet21:11
=== Ursinha-afk is now known as Ursinha
jmlthumper: that's ok, I need a few minutes anyway21:11
wallyworldthumper: i'm here now :-)21:14
jmlanyone mind if I fix the test failures in devel?21:14
=== jml changed the topic of #launchpad-dev to: Launchpad Development Channel | Week 3 of 10.11 | PQM is open | firefighting: devel failing, jml fixing | https:/​/​dev.launchpad.net/​ | Get the code: https:/​/​dev.launchpad.net/​Getting
thumperjml: no... go ahead21:14
thumperabentley: around?21:15
abentleythumper: hi.21:15
thumperabentley: mumble21:15
=== salgado is now known as salgado-afk
lifelessflacoste: no, I hadn't fixed the test - it was 0130 when I found that it was failing21:19
flacostelifeless: it's in PQM right now21:20
lifelessflacoste: thanks21:20
abentleythumper: BTW, I think we should switch the build delay stats to past-six-hours rather than past-24-hours.  I.e. data since last sample.21:37
rockstarHeh.  I just ran into Mikael in the Yahoo cafeteria.  He says Windmill is dead.21:38
thumperheh21:38
thumperhmm21:38
thumperrockstar: was he a windmill author?21:38
rockstarthumper, he was one of them.  He doesn't do anything with windmill anymore.21:39
jml:( :(21:39
thumperrockstar: what did he suggest to use?21:39
rockstarAaron is apparently still taking patches, but isn't maintaining it.21:39
thumperjml: mumble?21:39
jmlthumper: sure21:39
rockstarthumper, I quote "Everything we complained about in Selenium is basically fixed now."21:39
rockstarthumper, and YUITest now has a Selenium shim in it as well.21:39
rockstarAlthough YETI was also brought up21:40
rockstarthumper, I may as well show everyone what I've got now...21:44
rockstarSo, we currently have this pretty-overlay widget that's kinda messy but all our overlays inherit from it.  It looks like this: http://people.canonical.com/~rockstar/pretty-overlay.png21:44
rockstarIn ~20 lines of plugin js and some custom CSS, I've made the standard Y.Overlay do the exact same thing.  It looks like this: http://people.canonical.com/~rockstar/overlay.png21:45
rockstarThe latter loads from cold cache uncompressed 5x than the pretty overlay does completely compressed.21:46
rockstarEr, 4-5x faster.21:46
jmlthumper: https://bugs.launchpad.net/launchpad-code/+bugs?field.searchtext=&orderby=-importance&field.status:list=NEW&field.status:list=INCOMPLETE_WITH_RESPONSE&field.status:list=INCOMPLETE_WITHOUT_RESPONSE&field.status:list=CONFIRMED&field.status:list=TRIAGED&field.importance:list=HIGH&field.importance:list=UNDECIDED&field.tag=recipe&21:47
jmlthumper: e.g. http://paste.ubuntu.com/529601/21:52
jmlthumper: https://code.launchpad.net/~testtools-dev/testtools/trunk/+new-recipe21:55
marsrockstar, so it sounds like you are saying, it has been two years since we started this, time for a technology refresh?22:01
marsrockstar, because everything we started with has been fixed (lazr to make up for gaps in YUI core) or shaken out (windmill v selenium)22:02
rockstarmars, no, more like "we over engineered it, and now it's time to simplify it"22:02
marsrockstar, that too :)22:02
rockstarmars, the overlay code is a good example of us not really knowing what the capabilities of YUI were.22:02
rockstarmars, my goal is to shrink the maintenance footprint of our code.22:03
rockstar(because we don't have a lot of resources to maintain javascript)22:03
rockstarmars, did you see my previous statement about windmill?22:05
marsrockstar, I did.  It does not surprise me.22:06
rockstarmars, yeah, he was talking about the difficulties in doing event driven stuff in python.22:07
marsrockstar, I think you are right, going by what you are saying, we should have sent more people.  We are new at this: we get a lot out of it compared to, say, going to PyCon.22:10
marsPyCon is cool, but what you get out of the conference changes as you gain more experience with the language, tools, and community22:11
rockstarmars, yeah, maybe.  I don't think there's much interest in writing javascript on the team though.22:11
marsrockstar, I was actually thinking of people from other projects, too.  They use YUI too.  (I'm surprised Sidnei isn't there)22:12
rockstarSome of that might be that javascript (and YUI in particular) can be REALLY confusing.  :)22:12
rockstarmars, sidnei has new twins.  I think he's tied up somewhere.22:12
marsoh, yeah, I forgot.  (not that I would know /anything/ about that little life change...)22:12
jmlrockstar: event-driven stuff in Python is easy and fun!22:13
jmlPython is so awesome for events22:13
rockstarjml, not when you're tied to an existing event loop (firefox, in this instance)22:14
jmlrockstar: well, that's not doing event-driven code in Python, surely22:15
jmlrockstar: otherwise, I don't see where the difficulty is. it's easy to write code that responds to events from external systems, regardless of how they're written22:16
rockstarjml, yeah, there's definitely some bias there.22:16
rockstarEr, I mean in the case of saying python isn't good for event driven development.22:17
jmlrockstar: next time someone says that, point them to #twisted :)22:19
marsrockstar, well, I'm looking forward to seeing what comes out of this.22:19
rockstarjml, yeah, yeah.  :)  Basically, he was telling me what I wanted to hear (windmill is dead) so I smiled and nodded to everything else he said.22:19
marsrockstar, when can the rest of us expect your trip report? :)22:21
rockstarmars, I'm going to type it up tonight after Douglas Crockford's verbal abuse.22:21
marsclosing keynote?22:22
rockstarmars, I think it's just a Bayjax meeting that coincides with the end of YUIConf.22:23
jml<lp.buildmaster.model.buildfarmjobbehavior.IdleBuildBehavior object at 0x88a8750> is not an instance of <class 'lp.buildmaster.model.buildfarmjobbehavior.IdleBuildBehavior'>22:34
jmlwhat am I missing? that seems nonsensical?22:35
rockstarjml, instance v. class?22:35
mwhudsonjml: security proxies?22:35
jmlmwhudson: sterling concept22:35
* jml tries22:35
wgrantBut security proxies are meant to preserve isinstance, aren't they/22:36
wgrantEr, instanceof.22:36
mwhudsonwgrant: not instanceof -- isn't that js?22:36
jmlwgrant: nope, zope has special thingummies22:36
wgrantmwhudson: Uh, yes. Been dealing with too much Java at uni lately.22:37
jmlhttp://pastebin.ubuntu.com/529617/  – can someone please eyeball that testfix?22:38
jmlmwhudson: it was indeed rSP22:42
mwhudsonargh, my brain is reading that as "the register that contains the stack pointer"22:42
mwhudsonjml: wow, that assertIdentical looks optimistic22:43
mwhudsonjml: looks fine, i was vaguely under the impression that we had an assertIsInstance that did that already?22:44
jmlmwhudson: we do, but trial base class22:44
mwhudsonah ok22:44
jmlmwhudson: I'm fixing that after I fix circular stuff :)22:44
mwhudsonr=me then, if you like22:44
jmlmwhudson: thanks.22:49
* jml submits22:49
* jml waits for pqm22:59
thumperjml: I'm looking at the db-devel failure23:01
jmlthumper: thanks :)23:01
thumperit seems intermittant23:01
jmlthumper: yeah, that's my guess. I didn't get it doing a few spins locally.23:01
thumperI have23:01
jmlthumper: but I can't find the race in the code23:02
jmlthumper: cool. you've made more progress than me.23:02
jmlthumper: also, I can't see anything that's changed recently there. (but I had a pretty shallow & quick poke through the vcs log, so I probably missed something)23:02
thumperhmm23:03
thumperit seems the latest testtools is a bit tempermental23:03
thumperI ran a test with -D to break on failure23:03
thumperbut it broke into the debugger on success23:03
jmlthumper: I don't know of anything that's changed in testtools along those lines23:05
jmlbigjools: hi23:09
jmlbigjools: don't worry about the test failure23:09
jmlbigjools: http://pastebin.ubuntu.com/529617/23:09
jmlbigjools: I've got a fix churning in PQM right now23:09
* jml continues to sit around, waiting for PQM to churn.23:13
=== jml changed the topic of #launchpad-dev to: Launchpad Development Channel | Week 3 of 10.11 | PQM is open | firefighting: devel failing, jml fixing; db-devel failing, thumper fixing | https:/​/​dev.launchpad.net/​ | Get the code: https:/​/​dev.launchpad.net/​Getting
lifelessjml: hi23:22
jmllifeless: hello23:23
lifelessI've pushed a big chunk of the testrepository test helpers into fixtures23:23
lifelessand I've some matchers to push into testtools23:23
lifelesswhat do you think of making testtools depend on fixtures23:23
jmllifeless: I'm not exactly against it, although doesn't fixtures depend on testtools?23:24
lifelessfor its tests only23:24
jmllifeless: what do you think of merging them?23:26
lifelessthe only thing that makes me hesitate is that fixtures are useful outside of tests23:26
lifelesslike we might move matchers out of testtools eventually23:26
jmlI can imagine the first with less stretching than it takes to imagine the second23:27
lifelessheh23:28
jmllifeless: in any case, I'm vaguely positive toward the idea, but I'd need to sleep on it23:29
jmllifeless: could I persuade you to push a new release of testrepository into debian sometime soon?23:29
lifelessthats what I'm heading towards23:29
lifelessfixtures is in NEW23:30
jmllifeless: yay23:31
jmllifeless: I've made a ~testing-cabal team w/ a PPA. I want to be building dailies of stuff into that23:31
lifelessyes23:31
jmllifeless: unfortunately, I suck hard at packaging and haven't had a spare moment to actually fix them to not suck.23:31
lifelessyou might want to add that team to the recipes beta23:31
lifelessso that I can see it :)23:31
jmllifeless: you should be able to see it. launchpad-beta is in recipes beta23:32
lifelesskk23:32
* jml ec2 submits database-apocalypse23:32
lifelessah there it is23:33
lifeless\o/ success23:33
lifelessjml: so, we can nuke edge now ?23:36
jmllifeless: you tell me :)23:36
jmllifeless: you don't need edge to get at recipes23:36
jmlthat's all I know23:37
wgrantSo all we need edge for is API scripts for the next 4.5 years :D23:37
wgrantAlternatively we could hunt down edge API scripts using the stats which probably don't exist.23:37
mwhudsona redirect in the frontend doesn't sound like much burden23:38
mwhudson(assuming scripts will work with that)23:38
wgrantIt won't work.23:38
wgrantAt least I don't think it will.23:39
wgrantThe WADL has edge stuff hardcoded.23:39
wgrantUnless you translate the outgoing WADL too...23:39
jmlor23:43
jmlyou could just leave api.edge as is, put a redirect up for all the other subdomains and bring the edge machine(s) into the lpnet pool23:44
wgrantTrue.23:44
pooliewallyworld: is bug 636930 now fixed in launchpad, or at least inprogress?23:44
wgrantAs well as looking for any authenticated edge API requests and severely chastising those users.23:44
_mup_Bug #636930: Upgrading a repository fails with 'Inter1and2Helper' object has no attribute 'source_repo' <bazaar> <sru> <upgrade> <verification-done> <Bazaar:Fix Released by spiv> <Bazaar 2.2:Fix Released> <Launchpad Bazaar Integration:Triaged> <bzr (Ubuntu):Fix Released> <bzr (Ubuntu Maverick):Fix Released> <https://launchpad.net/bugs/636930>23:44
jmlsilly conflict :(23:45
* jml runs ec2 land again23:45
pooliejml, i think my dkim branch just needs to be submitted23:46
poolieit may fail in ec223:46
jmlpoolie: cool.23:46
wallyworldpoolie: you mean upgrading lp to use bzr 2.2.1?23:46
jmlpoolie: I was meaning to ask you23:46
pooliewould you be so kind as to send it for me, and i'll in parallel run the tests here and see what happens23:46
jmlpoolie: I mean, in real time in addition to my earlier askinations23:46
jmlpoolie: will do. you'll be CCd the results of the run23:46
spiv'bzr ping lp:bzr' still reports 2.2.0, so I don't think 636930 is fix released yet.23:46
wallyworldpoolie: spiv: i have tried for several days to land the @%@! fix but we seem to be permanently in textfix mode :-(23:47
wallyworldie my lp-land keeps getting rejected23:47
jmlpoolie: conflicts23:47
jmlpoolie: also, commit message23:47
=== jml changed the topic of #launchpad-dev to: Launchpad Development Channel | Week 3 of 10.11 | PQM is open | firefighting: db-devel failing, thumper fixing | https:/​/​dev.launchpad.net/​ | Get the code: https:/​/​dev.launchpad.net/​Getting
pooliejml, ok, it's on my queue to fix them, test, and then i'll let you know23:49
jmlpoolie: thanks. If I hear from you, I'll land it tomorrow23:50
lifelessmwhudson: they won't23:54
lifelessmwhudson: I filed a bug on foundations if you want the gory details23:54
lifelessmy current basic plan is - shrink edge as fast as we can23:55
lifelesskeep looking at how to fold the machines into the one cluster23:55

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