[00:05] <LPCIBot> Project devel build (151): STILL FAILING in 3 hr 37 min: https://hudson.wedontsleep.org/job/devel/151/
[00:05] <LPCIBot> Launchpad Patch Queue Manager: [r=abentley][ui=none][bug=620615,
[00:05] <LPCIBot> 659078] change Launchpad to use Storm 0.18
[00:25] <wallyworld> thumper: they can suck, you just have to know how to tune them :-) i think storm may not be as advanced as say hibernate in this area
[00:25] <thumper> wallyworld: I'm attacking a place in the code where there is simplistic thinking
[00:25] <wallyworld> hibernate has all sorts of goodies, including support for batch updates and mixing native sql with it's object query language (HQL)
[00:25] <thumper> wallyworld: so does storm
[00:26]  * wallyworld needs to learn more storm
[00:28]  * wallyworld wonders, does storm support per query fetching strategies and pre-fetch sizes, or lazy instantiation of collections?
[00:37] <thumper> wallyworld: kinda
[00:38] <wallyworld> it's stuff like all that which is needed to properly tune one's app of course
[00:39] <LPCIBot> Project db-devel build (98): SUCCESS in 3 hr 37 min: https://hudson.wedontsleep.org/job/db-devel/98/
[00:39] <LPCIBot> Launchpad Patch Queue Manager: [rs=thumper][ui=none][no-qa] Manual merge of stable into db-devel.
[00:40] <wallyworld> hey thumper, i'm likely the last to realise - i suppose you know about http://blogs.computerworld.com/17224/ubuntu_changes_its_desktop_from_gnome_to_unity
[00:40] <thumper> no
[00:40] <wallyworld> someone emailed it to me
[00:43]  * wallyworld gets out the tissues and blubbers over how unloved KDE is :-(
[00:43] <jcsackett> wallyworld: if it helps, i know in OS X circled KDE 4 got serious circulation. :-P
[00:44] <jcsackett> s/circled/circles/
[00:44] <wallyworld> it would help more if KDE had more support on Ubuntu :-)
[00:46] <wallyworld> at least maybe there's a growing realisation that Qt is good. one step forward...
[00:47] <jcsackett> it helps that Qts license situation got cleaned up.
[00:47] <jcsackett> (or the FUD around it got cleaned up; whatever your preference might be)
[00:49] <wallyworld> jcsackett: same thing really, given the impact it had...
[00:49] <jcsackett> wallyworld: fair point.
[00:51] <jcsackett> wallyworld: these days i'm a wmii man, if you want to talk no love. :-D
[00:51] <wallyworld> :-)
[00:53]  * thumper afk for walk to shops and lunch 
[01:19] <maxb> Does anyone have any idea why ~vcs-imports is associated with https://code.edge.launchpad.net/~brian-rogers/gnome-power/report-percentage/+merge/39329 ?
[01:19] <jelmer> maxb, it's probably the default reviewer for some reason
[02:08]  * thumper needs coffee badly
[02:25]  * thumper has coffee and is screaming at his screen
[02:25]  * thumper dodges a tumbleweed
[02:26] <thumper> why is that damn test being run twice?
[02:26] <thumper> lifeless: ping
[02:26]  * wgrant rolls some more tumbleweed in.
[02:26] <lifeless> hi
[02:26] <wgrant> It's not one of those tests which is confusingly run with the same name for several object types?
[02:27] <thumper> lifeless: when running a doc test with "bin/test -vvt message-holds-xmlrpc.txt" it runs twice
[02:27] <thumper> lifeless: any idea?
[02:27] <thumper> lifeless: btw, this will fix the mailman xmlrpc call when it makes 5000 database calls
[02:28] <lifeless> nice
[02:28] <lifeless> what causes that ?
[02:28] <thumper> simplistic iteration over a large result set
[02:28] <lifeless> lack of eager loading ?
[02:29] <thumper> and silly logic
[02:29]  * thumper is enfixorating
[02:29] <thumper> I'm changing it slightly
[02:29] <thumper> so will just do 6
[02:29] <thumper> I could attempt to make it 2, but I don't see the benefit for that
[02:29] <thumper> the logic would be harder to follow if I did
[02:30] <thumper> 5000 -> 6 is much better
[02:30] <lifeless> I think 6 queries is fine ;)
[02:30] <lifeless> sometimes less is worse too
[02:30] <lifeless> depending on the related data density
[02:30] <rockstar> deryck, lp:~rockstar/launchpad/javascript-refresh
[02:31] <thumper> lifeless: this one: OOPS 1758XMLP341
[02:32] <lifeless> nice
[02:34] <lifeless> thumper: I see the double run in trunk
[02:34] <lifeless> thumper: its being loaded twice by whatever module constructs it
[02:34] <thumper> lifeless: is it all doc tests or just some?
[02:34] <lifeless> lp/registry/tests/test_doc.py
[02:35] <lifeless> will be a buglet in there
[02:35] <lifeless> ignore for this branch IMO
[02:36] <thumper> ok
[02:36] <thumper> lifeless: are you going to file a bug for it?
[02:36] <thumper> lifeless: if it is simple, I could fix in this branch
[02:36] <lifeless> its late + jetlag
[02:37] <lifeless> I haven't looked
[02:38] <thumper> lifeless: ah, it seems to have two different setup methods
[02:38] <thumper> lifeless: so it is testing things twice
[02:39] <thumper> one with the real mailinglist api and another with a fake
[02:51] <jcsackett> thumper: you mean it's doing two tests in one via diff setUps?
[02:51] <thumper> kinda
[02:52]  * jcsackett pulls up code.
[02:53] <jcsackett> or not; i forgot my dev machine doesn't multitask well when updating.
[02:53] <jcsackett> and here i thought i might be helpful. this is a test in registry?
[02:54] <thumper> it is, and there isn't a problem
[02:54] <thumper> just my misunderstanding
[02:55] <jcsackett> thumper: ah, dig.
[03:03]  * wgrant WTFs at launchpad-users.
[03:04] <lifeless> oh?
[03:04] <wgrant> The last email to it.
[03:05] <lifeless> on oct 15th?
[03:05] <wgrant> About 47 minutes ago.
[03:06] <lifeless> swiss branded watches?
[03:06] <jcsackett> chain letter about returning vets, looks like.
[03:07] <wgrant> It looks like it.
[03:07] <jcsackett> that does seem about as Off-topic as you're going to get...
[03:07] <lifeless> \o/ edge bye bye
[03:07] <wgrant> :( poor edge
[03:09] <lifeless> hah
[03:10] <jcsackett> i had only just met poor edge.
[03:10] <bac> wgrant: the previous one about getting mugged in KL was mighty off topic too
[03:10]  * wgrant remembers back when it was 'beta', restricted access, and had the shiny new UI.
[03:10] <wgrant> bac: Ah yeah, I forgot about that one.
[03:14] <jcsackett> bac: that one is however the result of a compromised account.
[03:14] <jcsackett> my sister had some people get into her yahoo account a few months back and received (nearly) word for word that email. it's apparently a pretty popular scam.
[03:23] <thumper> lifeless: has edge gone?
[03:23] <wgrant> Heh. I was about to ask if someone had turned off the redirect.
[03:23]  * thumper imagines some people getting a little miffed at no recipes ...
[03:23] <wgrant> Then I noticed the last rev.
[03:41] <EdwinGrubbs> thumper: ping
[03:41] <thumper> EdwinGrubbs: hi
[03:42] <LPCIBot> Yippie, build fixed!
[03:42] <LPCIBot> Project devel build (152): FIXED in 3 hr 37 min: https://hudson.wedontsleep.org/job/devel/152/
[03:42] <LPCIBot> * Launchpad Patch Queue Manager: [r=lifeless][ui=none][no-qa] Refactor page-performance-report to use
[03:42] <LPCIBot> less memory by using a SQLite3 db to hold the requests and
[03:42] <LPCIBot> generating statistics for only one key at a time.
[03:42] <LPCIBot> * Launchpad Patch Queue Manager: [r=henninge][ui=none][bug=659085] Remove
[03:42] <LPCIBot> getBugNotificationRecipients()
[03:42] <LPCIBot> * Launchpad Patch Queue Manager: [r=henninge][ui=none][bug=628762] Ditch property cache adapters in
[03:42] <LPCIBot> favour of plain old Python. The IPropertyCache adapter is
[03:42] <LPCIBot> replaced by get_property_cache() and the IPropertyCacheManager
[03:42] <LPCIBot> adapter is replaced by clear_property_cache().
[03:42] <wgrant> !
[03:43] <thumper> now that is a bit of IRC spam
[03:43] <wgrant> Does this mean we are green?
[03:43] <wgrant> Yes!
[03:43] <wgrant> Both are green!
[03:43] <wgrant> For the first time!
[03:43] <EdwinGrubbs> thumper: according to bzr annotate, you worked on canonical.launchpad.webapp.sorting.sorted_version_numbers. I'm wondering why you the numbers are sorted in the reverse order as the letters. For example, [3, 2, 1, A, B, C], which looks wrong if a version combines letters and numbers like [5a, 4a, 3a, 3b, 3c].
[03:44] <thumper> holy crap that is quite a while ago...
[03:44] <EdwinGrubbs> thumper: I'm in the process of moving the sorting into the db so that the results can be batched. It looks like this is just used for the productseries.
[03:44] <thumper> EdwinGrubbs: I think the reasoning was we wanted newer version numbers first
[03:45] <EdwinGrubbs> thumper: ok, so there shouldn't be a problem in making the letters sort descending like the numbers?
[03:45] <thumper> ahh...
[03:45] <thumper> find out where it's used forst
[03:45] <thumper> first
[03:45] <thumper> I really don't remember
[03:46] <EdwinGrubbs> thumper: so far, it looks like it is just used for https://qastaging.launchpad.net/launchpad/+series
[03:46] <EdwinGrubbs> but I'll double check with sinzui
[03:46] <thumper> EdwinGrubbs: in which case it is all yours :)
[03:46] <thumper> who whatever you like
[03:46] <thumper> s/who/do/
[03:46] <EdwinGrubbs> thanks
[04:18] <LPCIBot> Project db-devel build (99): FAILURE in 3 hr 39 min: https://hudson.wedontsleep.org/job/db-devel/99/
[04:18] <LPCIBot> * Launchpad Patch Queue Manager: [rs=buildbot-poller] automatic merge from stable. Revisions: 11791
[04:18] <LPCIBot> included.
[04:18] <LPCIBot> * Launchpad Patch Queue Manager: [r=henninge][ui=none][no-qa] Fix the models and accompanying tests
[04:18] <LPCIBot> for Branch Merge Queues to use the secured utilities, etc.
[04:27] <rockstar> How does launchpad not depend on beautiful soup anymore?
[04:53] <thumper> rockstar: eh?
[04:54] <rockstar> thumper, launchpad used to use beautiful soup a lot, but apparently it doesn't anymore.
[04:54] <thumper> ah ...
[04:54] <thumper> really?
[04:54] <rockstar> Also, I SHOULD go to bed, but deryck and I is watching teh football.
[04:54] <rockstar> thumper, yeah, I just added soupmatchers to Launchpad and it needed BeautifulSoup.
[04:55] <thumper> rockstar: still used by canonical.launchpad.testing.pages
[04:55] <thumper> rockstar: it may be an egg
[04:55] <rockstar> thumper, no, it wasn't in versions.cfg or setup.py
[04:55] <rockstar> Weird.
[04:56] <rockstar> At least, buildout couldn't find it, even when I just installed the package.
[04:57] <thumper> rockstar: it is LP telling you to sleep
[04:57] <thumper> :)
[04:57] <rockstar> thumper, probably.
[05:49] <bac> matsubara-afk: ping me when you arrive
[05:49] <bac> rockstar: who is playing?
[07:21] <LPCIBot> Project devel build (153): FAILURE in 3 hr 38 min: https://hudson.wedontsleep.org/job/devel/153/
[07:21] <LPCIBot> * Launchpad Patch Queue Manager: [r=julian-edwards][ui=none][bug=662912][incr] Add diagnostics for bug
[07:21] <LPCIBot> 662912
[07:21] <LPCIBot> * Launchpad Patch Queue Manager: [r=henninge][ui=none][no-qa] Remove the beta redirect and is_edge facilities.
[07:53] <LPCIBot> Yippie, build fixed!
[07:53] <LPCIBot> Project db-devel build (100): FIXED in 3 hr 34 min: https://hudson.wedontsleep.org/job/db-devel/100/
[07:53] <LPCIBot> Launchpad Patch Queue Manager: [rs=buildbot-poller] automatic merge from stable. Revisions: 11792
[07:53] <LPCIBot> included.
[08:12] <al-maisan> Hello! I cannot push branches to launchpad. Can somebody please look into this?
[08:13] <al-maisan> Here's the error I get: $ bzr push
[08:13] <al-maisan> Using saved push location: bzr+ssh://bazaar.launchpad.net/~al-maisan/landscape/edit-computer
[08:13] <al-maisan> Traceback (most recent call last):
[08:13] <al-maisan>   File "/srv/bazaar.launchpad.net/production/launchpad-rev-9885/eggs/bzr-2.2.0-py2.6-linux-x86_64.egg/EGG-INFO/scripts/bzr", line 140, in <module>
[08:13] <al-maisan>     exit_val = bzrlib.commands.main()
[08:13] <al-maisan>   File "/srv/bazaar.launchpad.net/production/launchpad-rev-9885/eggs/bzr-2.2.0-py2.6-linux-x86_64.egg/bzrlib/commands.py", line 1191, in main
[08:13] <al-maisan>     _register_builtin_commands()
[08:13] <al-maisan>   File "/srv/bazaar.launchpad.net/production/launchpad-rev-9885/eggs/bzr-2.2.0-py2.6-linux-x86_64.egg/bzrlib/commands.py", line 182, in _register_builtin_commands
[08:13] <al-maisan>     import bzrlib.builtins
[08:13] <al-maisan> ValueError: bad marshal data
[08:13] <al-maisan> bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist.
[08:13] <al-maisan> sorry
[08:13] <al-maisan> meant to paste pastebin url
[08:34] <adeuring> good  morning
[09:07] <wgrant> rockstar: BeautifulSoup is included via the Java Mentality.
[09:18] <mrevell> Hi
[10:57] <LPCIBot> Yippie, build fixed!
[10:57] <LPCIBot> Project devel build (154): FIXED in 3 hr 35 min: https://hudson.wedontsleep.org/job/devel/154/
[10:57] <LPCIBot> * Launchpad Patch Queue Manager: [r=lifeless,thumper][ui=none][no-qa] Slightly fix the IDSJob tests.
[10:57] <LPCIBot> * Launchpad Patch Queue Manager: [r=lifeless][ui=none][bug=664012] Fix the oopses raided by +branch
[10:57] <LPCIBot> navigation when there is no referrer to be 404s.
[13:21] <bigjools> good morning
[13:22] <wgrant> Morning.
[14:23] <mwhudson> jam: staging codehosting seems to be working
[14:23] <mwhudson> this surprises me :-)
[14:23] <jam> mwhudson: well, we haven't updated the config for the new code yet
[14:23] <mwhudson> oh of course
[15:17] <lifeless> poolie: bug 666765 is also on my nice-to-have for scopes
[15:29] <StevenK> lifeless: Didn't you mention a fix for the "No module named mailman.monkeypatches.defaults" ? I seem to recall it involved wielding rm over a directory
[15:31] <lifeless> rm -rf lib/mailman; make
[15:31] <jml> why is stdout a text stream rather than a bytes stream in Python 3?
[15:31] <lifeless> because python three
[15:31] <lifeless> jml: hows your session
[15:32] <jml> lifeless: not exactly riveting
[15:35] <bigjools> lifeless: so, running tests locally I get a lot of errors about librarians either running when they should not be or vice versa
[15:36] <bigjools> this Is Bad.
[15:36] <rockstar> james_w, can we chat at some point about soupmatchers?
[15:36] <bigjools> lifeless: looks like some layer issues
[15:37] <rockstar> bigjools, yeah, I've had those problems for about three weeks.
[15:37] <rockstar> bigjools, did you bin/kill-test-services ?
[15:38] <bigjools> yes
[15:38] <rockstar> bigjools, where is you?
[15:38] <bigjools> rockstar: boner 6
[15:38] <rockstar> bigjools, is there a session in there, or are you loitering?
[15:38] <bigjools> rockstar: linaro session
[15:38] <rockstar> bigjools, ah.
[15:38] <bigjools> rockstar: but I may duck out RSN
[15:39] <rockstar> bigjools, okay.  I'm at the end of the arterial hallway.
[15:39] <lifeless> bigjools: last time I saw that I had a prod librarian running
[15:40] <bigjools> I am getting motivated to fix test_on_merge
[15:45] <bigjools> rockstar: wtf is the arterial hallway? :)
[15:45] <lifeless> antigua
[15:45] <rockstar> bigjools, the hallway that acts as artery to all the dead end hallways.
[15:46] <bigjools> rockstar: which end?
[15:48] <poolie> lifeless, replied
[15:49] <poolie> lifeless, please tag them so i can find them later
[15:50] <bigjools> lifeless: it was a stale pidfile
[16:05] <lifeless> jml: :(
[16:06] <james_w> rockstar, sure thing
[16:06] <rockstar> james_w, are you going to be in a session after the one that just started?
[16:07] <james_w> rockstar, yes. I think my afternoon is quieter though
[16:07] <james_w> rockstar, or lunch?
[16:08] <rockstar> james_w, lunch will work.
[16:17] <StevenK> Is it just me or is codehosting down?
[16:40] <fjlacoste> lifeless: around?
[16:41] <lifeless> ys
[16:44] <lifeless> fjlacoste: yes
[16:44] <fjlacoste> lifeless: i need your advice, i'm working on a version of the ppr report that computes everything using SQL, that will operate in constant memory
[16:44] <fjlacoste> lifeless: i have all the stats covered except the median
[16:44] <fjlacoste> i know how to compute it, but it is very expensive
[16:44] <lifeless> fjlacoste: btw, disk space on sodium - we had to kill your thing
[16:45] <fjlacoste> i know
[16:45] <fjlacoste> that's fine
[16:45] <fjlacoste> we can sort that out later
[16:45] <lifeless> it was using 5% of the disk :)
[16:45] <fjlacoste> 2.9G
[16:45] <lifeless> yeah
[16:45] <lifeless> thats ~ 5%
[16:45] <fjlacoste> it needs a bigger disk :-)
[16:45] <fjlacoste> anyway
[16:45] <fjlacoste> so the way i can compute the median is by sorting on the column and using LIMIT 1 OFFSET n/2 to get the value
[16:46] <fjlacoste> but this seems like very expensive to do given that we are taking about millions of records
[16:46] <fjlacoste> and we are computing 3 medians
[16:46] <fjlacoste> and we can only do that by key
[16:46] <lifeless> WHERE Rank = (SELECT (COUNT(*)+1) DIV 2 FROM
[16:46] <fjlacoste> ah
[16:47] <lifeless> also
[16:47] <lifeless> http://wiki.postgresql.org/wiki/Aggregate_Median
[16:47] <lifeless> though I haven't looked into that implementation
[16:47] <fjlacoste> lifeless: i'm using sqlite
[16:47] <lifeless> oh
[16:47] <lifeless> :P
[16:47] <fjlacoste> i was asking if you mind dropping it :-)
[16:48] <fjlacoste> but your rank thing gave me an idea
[16:48] <lifeless> fjlacoste: hmm, so if the column is indexed grabbing the median should be darn cheap
[16:49] <fjlacoste> the question is how do I index the column relatively cheaply
[16:49] <lifeless> insert the data
[16:49] <lifeless> index the column
[16:49] <lifeless> then start querying
[16:50] <lifeless> oh
[16:50] <lifeless> you'll want to increase the sqlite cache size too
[16:50] <lifeless> because its like 2MB or something insane by default
[16:50] <lifeless> give it 200MB or so
[16:50] <flacoste> create an index on category, time for example?
[16:50] <flacoste> ok
[16:50] <lifeless> yeah
[16:50] <lifeless> remember that the query prefix has to match the index
[16:51] <flacoste> right
[16:51] <lifeless> category,time won't help time only sorts
[16:51] <lifeless> IIRC
[16:51] <flacoste> well i need the rank of time within each category
[16:51] <flacoste> (or url, or pageid)
[16:51] <lifeless> yack
[16:52] <jcsackett> lifeless: any chance you could help me think through bac's notes on bug 652156 and bug 652149?
[16:52] <jcsackett> basically, it looks to me like the timeouts there aren't related to either bug/branch.
[16:52] <lifeless> qastaging has a 10second timeout
[16:52] <abentley> lifeless: do you mean yak (-shaving), yuck, or some combination?
[16:53] <lifeless> I meant 'acl'
[16:53] <lifeless> bah
[16:53] <lifeless> 'ack'
[16:53] <lifeless> jcsackett: so any page that has a timeout bug open (https://bugs.edge.launchpad.net/launchpad-project/+bugs?field.tag=timeout) is almost certain to timeout on [qa]staging too
[16:54] <lifeless> jcsackett: I would not stress about incidental timeouts there (but I *would* fix the page to not timeout at all :P separately :) )
[16:54] <mwhudson> mtaylor, jam: launchpad/bzr planning over lunch?
[16:54] <jcsackett> lifeless: that makes sense. so bac and i can mark ours qa-ok if the functionality is working (aside from the branchbug timeout)?
[16:55] <lifeless> jcsackett: as long as the page is already timing out with bug, production oops)
[16:56] <flacoste> lifeless: actually, there is no Rank expression in sqlite
[16:56] <flacoste> and generating the rank seems as costly as getting the median using iterative limit/Offset
[16:58] <lifeless> flacoste: how slow is slow
[16:58] <flacoste> several hours
[16:59] <flacoste> actually, i don't know
[16:59] <flacoste> just guessing here
[16:59] <flacoste> i'll measure and see
[16:59] <flacoste> assess
[16:59] <jcsackett> lifeless: so, there isn't a bug filed against project/+branches, but person/+branches has one (bug 627945) and the query is the same in both. i'm thinking either add detail to that bug or file a new bug for project linked to it. thoughts?
[17:01] <mwhudson> mtaylor, jam: which isn't right now, of course
[17:01]  * mwhudson was just getting hungry and optimistic
[17:02] <flacoste> lifeless: http://oreilly.com/catalog/transqlcook/chapter/ch08.html#Calculating%20a%20Median has an actual elegant solution :-)
[17:02] <jam> mwhudson: sounds good
[17:02] <jam> I'm pretty sure poolie is interested too
[17:04] <lifeless> jcsackett: add the page id for the other case to the title, done.
[17:04] <jcsackett> lifeless: fantastic. thanks.
[17:11] <flacoste> hmm, that query does look expensive
[17:12] <lifeless> flacoste: up the cache size as a start
[17:12] <flacoste> lifeless: ack
[17:12] <lifeless> you could denormalise the counts per category
[17:12] <lifeless> given you're starting with a fresh db each run, right ?
[17:18] <mtaylor> mwhudson: yes
[17:20] <mwhudson> jam, mtaylor: i'll loiter by the registration desk
[17:20] <mwhudson> poolie: ^^
[17:55] <lifeless> jml: https://code.edge.launchpad.net/~lifeless/testtools/fixtures/+merge/39388
[18:14] <LPCIBot> Project db-devel build (101): SUCCESS in 4 hr 4 min: https://hudson.wedontsleep.org/job/db-devel/101/
[19:09] <jml> lifeless: reviewed
[19:13] <lifeless> gary_poster: http://pypi.python.org/pypi/storm - needs 0.18 ?
[19:15] <mars> the PyPi version is almost a year old
[19:15] <gary_poster> lifeless, yes, remaining release of storm (per the release instructions) is stalled until Jamu gives me privs to upload docs or does it himself.  There are a number of small things remaining (also announcing it on ML, for instance).
[19:15] <gary_poster> For PyPI, Storm didn't release 0.17 there and it's not on their release checklist, but I got privs to do it anyway, so I'll do it then.
[19:16] <lifeless> gary_poster: Jamu here, go ahead and release, I'll deploy docs later.
[19:16] <gary_poster> Cool Jamu, thanks
[19:16]  * mars loves UDS :)
[19:22] <mwhudson> i am inpressed by the fact that people are just registering kernel imports, and they basically work
[19:23] <mwhudson> it would be much better if we supported stacking for import branches sensibly but well
[19:24] <jelmer> mwhudson: +1
[19:24] <jelmer> it shouldn't really be all that hard if I understand correctly
[19:24]  * mwhudson quickly reaches for his "not a launchpad developer" hat
[19:24]  * jelmer reaches for his "not a launchpad-code developer" hat :-)
[19:25] <mwhudson> jelmer: i think the bug report on this describes what to do fairly clearly
[19:26] <mwhudson> i hope so,  becuase i'm fairly sure i knew what to do at one point and certainly don't any more
[19:33] <jml> lifeless: do you still thing that https://bugs.edge.launchpad.net/testtools/+bug/584824 is still worth doing?
[19:33] <jml> think
[19:36] <jml> lifeless: also, https://bugs.edge.launchpad.net/testtools/+bug/666923 wrt previous discussions
[19:58] <jkakar> gary_poster: Hi!
[19:58] <gary_poster> jkakar: hi :-)
[20:05] <lifeless> deryck: hey
[20:05] <deryck> hi lifeless
[20:05] <lifeless> https://devpad.canonical.com/~lpqateam/qa_reports/deployment-stable.html
[20:06] <deryck> looking....
[20:06] <deryck> slow openid dance
[20:09] <lifeless> deryck: so https://bugs.qastaging.launchpad.net/ubuntu/+source/xorg/+bug/10000 looks ok
[20:09] <lifeless> deryck: I'm not entirely sure how to validate it further
[20:09] <deryck> lifeless, yeah, I'm looking at the changes now to see.
[20:13] <deryck> lifeless, I smell a bad rev.  https://bugs.qastaging.launchpad.net/bugs/10000/+bug-portlet-subscribers-content
[20:14] <deryck> hmmm, maybe that's not gmb's
[20:18] <lifeless> deryck: whats wrong with it ?
[20:18] <deryck> lifeless, that link OOPS for me.
[20:19] <deryck> https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1760QS46
[20:21] <deryck> oh, that's security.cfg permissions again.  Like bug expiry script.  We missed something in pg 8.4 migration, I guess.
[20:22] <deryck> lifeless, ok, so gmb's is qa-ok.  Visiting https://bugs.qastaging.launchpad.net/ubuntu/+source/xorg/+bug/10000/+subscribe confirms the new code is hit and works fine.
[20:23] <lifeless> deryck: will you mark it as such? the two bugs ?
[20:23] <deryck> lifeless, indeed.
[20:23] <lifeless> thanks
[20:25] <deryck> lifeless, do you not get an OOPS at the first URL I provided?  the portlet one.
[20:25] <lifeless> yes, I do, i thought it might be transient but its very quick
[20:26] <deryck> lifeless, transient?  You mean timeout?  I get ProgrammingError.
[20:26] <lifeless> deryck: I meant I thought it might be a slow db or something
[20:27] <deryck> lifeless, ah, ok
[20:27] <deryck> lifeless, we should talk more about this after we get out of sessions, since I saw the same on expiry script test runs.
[20:27] <bigjools> THE EAGLE HAS LANDED
[20:28] <bigjools> where eagle == new buildd manager
[20:28] <deryck> bigjools, awesome!
[20:28] <bigjools> 7k branch with no mechanical changes!
[20:29] <thumper> bigjools: what does it give us?
[20:30] <bigjools> asynchronous comms
[20:30] <bigjools> and far, far better failure detection and dealing with failures
[20:30] <bigjools> lp:~julian-edwards/launchpad/builderslave-resume if you want gory details :)
[20:31] <deryck> hi thumper.  Being at UDS makes us overlap for once. :-)
[20:31] <rockstar> james_w, are you going to have some bandwidth this afternoon?
[20:31] <thumper> deryck: hey
[20:32] <james_w> rockstar, the next session looks pretty good to me
[20:34] <rockstar> james_w, okay, I think I need to make some hard choices here.
[20:34] <james_w> rockstar, 6pm would also work for me
[20:34] <rockstar> james_w, yeah, that won't work at all.  Next session is good, I'll just chat with aq before the next session.
[20:37] <james_w> rockstar, well, that was the session I was thinking going to as well :-)
[20:37] <james_w> rockstar, are you here all week?
[20:37] <rockstar> james_w, indeed I am, but I want to land some work before next week.  :)
[20:37] <james_w> rockstar, sure :-)
[20:38] <james_w> rockstar, where are you now?
[20:38] <rockstar> james_w, I'm in the game development session, but it's a bust, so I can get out now if you can.
[20:38] <james_w> rockstar, I can
[20:38] <james_w> rockstar, outside the plenary room?
[20:40] <rockstar> james_w, I'm in the hall.
[21:12] <jml> bigjools: grats!
[21:13] <rockstar> \o/ BrowserTestCase just got a whole lot better.
[21:13] <bigjools> jml: and thanks to you!
[21:19] <bigjools> jml: FWIW I hammered it on DF with a load of production builders that were borrowed and it didn't put a foot wrong.
[21:19] <jml> bigjools: sweet.
[21:23] <lifeless> rockstar: what got better about it ?
[21:23] <bigjools> jml: of course, I just set myself up for a big fall :)
[21:23] <jml> bigjools: sure. :)
[21:23] <jml> bigjools: it's not going to work the first time. never does.
[21:23] <rockstar> lifeless, I'm teaching it about james_w's soupmatchers.
[21:23] <bigjools> kiko's 1st law of software?
[21:23] <jml> bigjools: exactly
[21:24] <jml> lifeless: https://code.launchpad.net/~jml/launchpad/atexit-warning/+merge/39403
[21:24] <lifeless> jml: I saw, i don't understand it. It seems wrong
[21:24] <jml> lifeless: that's why I wanted to talk about it :)
[21:24] <lifeless> why not just remove the atexit call
[21:25] <lifeless> and if things go screwy fix the code that isn't using a finally where needed.
[21:25] <jml> lifeless: I don't know why the atexit call was there. it seems like a belt-and-braces thing
[21:26] <lifeless> I think its because zope.testing stops teardown when a NotImplemented is enoucountered except in the last runner instance
[21:26] <jml> lifeless: I guess I should do some archeology and find out why it was added.
[21:27] <jml> lifeless: ok. I'm not sure what to do with that though.
[21:27] <lifeless> jml: change zope.testing to not mess about
[21:28] <lifeless> if a layer is setUp, it should tear it down
[21:28] <lifeless> perhaps we could use Fixture to do that ;)
[21:28] <jml> lifeless: I don't want to fix zope.testing to silence this warning
[21:28] <lifeless> jml: the warning is a symptom of the root cause
[21:28] <lifeless> the root cause is that teardown is inconsistently called
[21:29] <lifeless> and because of that we have:
[21:29] <jml> lifeless: the root cause being that layers is a pos
[21:29] <lifeless>  - ordering problems
[21:29] <lifeless> jml: well, what do you want to do?
[21:29] <lifeless> jml: I don't want the fixture code to silently accept teardowns when torn down
[21:30] <lifeless> that seems prone to hiding things
[21:30] <jml> lifeless: it's not doing that, there's a special tear down for atexit, since there's no way of cancelling atexit calls
[21:31] <lifeless> jml: you can use atexit._exithandlers.remove()
[21:31] <jml> lifeless: you think that would be better than the code in the patch?
[21:31] <lifeless> yes
[21:31] <lifeless> because the ugliness would be outside the island of sanity I've created
[21:32] <lifeless> better would be fixing the root cause: zope.testing
[21:32] <jml> I'm not going to fix zope.testing to address this issue
[21:32] <lifeless> well, I may :)
[21:33] <jml> lifeless: you're welcome to it
[21:33] <lifeless> jml: I'm not terribly concerned about pushing it upstream, because I think layers is so poor, I want a good platform for migrating from though.
[21:33] <lifeless> jml: I want us to stop papering over things like this.
[21:36] <jml> lifeless: sure, me too. but to me this is an incremental improvement. we're using atexit today to paper over an issue, and it's generating a warning that has little to do with the underlying issue....
[21:36] <jml> lifeless: I'm patching it to not generate useless the warning.
[21:36] <lifeless> StevenK: https://devpad.canonical.com/~lpqateam/qa_reports/deployment-stable.html tag, you're it.
[21:38] <lifeless> jml: but, you're:
[21:38] <lifeless>  - duplicating code
[21:38] <lifeless>  - adding a silent-wrong code path
[21:38] <lifeless>  - leaving the underlying issue open
[21:39] <lifeless> jml: I think its a much better use of your time to just fix the basic cause
[21:39] <jml> lifeless: no, it's not. because that's a significantly larger amount of work, and I've got other things I want to do.
[21:39] <lifeless> jml: I'd be happy with a change that didn't duplicate code and make the server.py module less clear
[21:40] <jml> lifeless: ok. I'm moving to atexit._exithandlers now
[21:44] <jcsackett> i may have missed an email on this topic, but does launchpadlib work on qastaging?
[21:44] <lifeless> it should, but it may need a glue update
[21:45] <jml> lifeless: patch updated.
[21:48] <jcsackett> hm. question the second: is lplib supposed to work with regular staging?
[21:51] <LPCIBot> Project db-devel build (102): SUCCESS in 3 hr 36 min: https://hudson.wedontsleep.org/job/db-devel/102/
[21:51] <LPCIBot> Launchpad Patch Queue Manager: [rs=lamont][ui=none][no-qa] Update the changelog for launchpad-buildd.
[21:53] <jml> lifeless: yes.
[21:53] <jml> jcsackett: yes.
[21:53] <jml> (sorry lifeless)
[21:55] <jcsackett> jml: thanks. i must just have something wrong in my setup; staging is telling me that it can't connect b/c it can't forward a request.
[21:55] <thumper> morning fellow hackers
[21:55] <jcsackett> i'll continue futzing with it.
[21:56] <jml> jcsackett: hmm.
[21:56] <jml> thumper: hi
[21:56] <thumper> jml: do you have a few minutes?
[21:56] <jml> thumper: I will very soon.
[21:56] <jml> thumper: in a session right now
[21:57] <thumper> jml: well, I have the standup shortly, and a talk with flacoste after that
[21:57] <jml> thumper: when are you next free?
[21:57] <thumper> jml: probably in 1.5 hours
[21:58] <jcsackett> jml: if that "hmm" indicates interest, the response is pasted here https://pastebin.canonical.com/39102/
[21:58] <flacoste> thumper: i'm free whenever you are
[21:58] <flacoste> i know that our call is only in 30 mins
[21:59] <jml> jcsackett: that looks like a bug that a losa ought to know about
[21:59] <jcsackett> jml: yeah? okay. i was assuming my own screw up, but i'll go tell one.
[21:59] <jml> jcsackett: I don't know
[22:00] <jcsackett> jml: dig. i'm getting a losa now.
[22:01] <jml> thumper: I can be around in 1.5hrs time
[22:02] <thumper> jml: ok
[22:11] <wallyworld_> thumper: abentley: standup?
[22:20] <lifeless> StevenK: ping
[22:21] <StevenK> lifeless: O hai
[22:21] <lifeless> I can has QA? https://devpad.canonical.com/~lpqateam/qa_reports/deployment-stable.html
[22:21] <lifeless> (Is it deployable)
[22:22] <StevenK> lifeless: Yes, but let me finish what I'm in the middle of
[22:23] <StevenK> I was unblocked to do so on Friday, and then there was a weekend and a plane trip
[22:38] <LPCIBot> Project devel build (155): SUCCESS in 3 hr 56 min: https://hudson.wedontsleep.org/job/devel/155/
[23:18] <lifeless> StevenK: bigjools I've requested a review of what was qa'd. Please unblock the queue as soon as possible.
[23:18] <lifeless> or tell me enough to do it myself
[23:18] <bigjools> lifeless: pardon?
[23:18] <lifeless> s/review/deploy/
[23:18] <bigjools> lifeless: need moar context
[23:18] <lifeless> bigjools: https://devpad.canonical.com/~lpqateam/qa_reports/deployment-stable.html
[23:19] <lifeless> bigjools: 9 day old unqa'd patch
[23:19] <lifeless> bigjools: (which is to be expected, we're only just in the actually-use-it stage of RFWTAD
[23:20] <bigjools> lifeless: Steve was in the middle of QAing that as far as I know
[23:21] <lifeless> cool
[23:24] <thumper> rockstar: ping
[23:28] <jml> thumper: ping
[23:28] <thumper> jml: just finishing off with flacoste
[23:28] <jml> thumper: ok.
[23:32] <wgrant> "The size of the diff (7194 lines) is larger than your specified limit of 1000 lines" D:
[23:32] <jml> wgrant: it's a big patch.
[23:35] <StevenK> lifeless: Are you saying "Please QA this right now", in leiu of say, dinner?
[23:36] <StevenK> lifeless: And it would take me longer to explain how to QA it than to just do it myself. :-)
[23:38] <flacoste> lifeless: what's the status of removing edge?
[23:41] <flacoste> i actually need to go afk, let's talk about it tomorrow