[14:28] <deryck> ok....
[14:28] <deryck> we can just meet without all the formal meeting begin stuff. :)
[14:29] <deryck> henning is away today unexpectedly if you all didn't know yet.
[14:29] <abentley> deryck: sounds like you're having an interesting day.
[14:29] <deryck> abentley, dude!  A rough start, but it's all good now.
[14:29] <abentley> deryck: yes, he said something to us.
[14:29] <deryck> the 5-10 mins late was my own fault, as usual.  the keys were Wendy's :)
[14:30] <deryck> So let's start with landing lane....
[14:30] <deryck> adeuring, I see you finished up that work yesterday.  Is it in ec2 or buildbot at this point?
[14:30] <adeuring> it's in ec2; I had to fix a failing test
[14:30] <deryck> ok, cool.
[14:31] <deryck> and now you're on to a new bug.  a timeout again?
[14:31] <adeuring> right
[14:31] <adeuring> deryck: 'll ask you to run an Explain analyze"
[14:31] <deryck> adeuring, ok, cool.  I can do that whenever you need.
[14:31] <adeuring> cool, thanks
[14:31] <deryck> thanks again for taking on another timeout! :)
[14:32] <deryck> abentley, and your work is in the process of landing too?
[14:32] <adeuring> timeouts are fun :)
[14:32] <abentley> deryck: I've just fixed the failing tests, so I'll get it landing after the stand-up.
[14:32] <deryck> abentley, ok, great.  and the on to some new bug, I assume?
[14:32] <deryck> s/the/then/
[14:33] <abentley> adeuring: I'm glad you think so, because we're running out of anything but timeouts.  Maybe you can teach me.
[14:33] <abentley> deryck: Gonna focus on the presentation for now.
[14:33] <deryck> abentley, ah, right.  Good call.
[14:33] <deryck> abentley, and can we move our call either later today or later in the week, being that I can't get in my own office yet? :)
[14:33] <adeuring> abentley: sure, but my method is mainly: stare long enough at the OOPS report, if things aren't obvious :)
[14:33] <abentley> deryck: of course.
[14:34] <deryck> abentley, great, thanks.
[14:34] <deryck> adeuring, actually, I think you have a good sense of how to track down timeouts.  a very practical approach....
[14:34] <adeuring> deryck: mybe, but it's hard to explain...
[14:34] <deryck> adeuring, you should consider sharing you approach more widely.  start with abentley, of course. :)
[14:34] <abentley> deryck: the presentation is mainly why I'm interested in YUITestLayer right now.
[14:35] <deryck> abentley, right.
[14:35] <adeuring> sure, I'll try...
[14:35] <deryck> so that brings me to me.... :)
[14:35] <deryck> I'm trying to land some YUI test improvements I did at Velocity but can't run them like abentley because of seq fault....
[14:35] <deryck> so I'll try working with sinzui more today and get that resolved.
[14:35] <deryck> then I'll land my work, when I'm sure it's actually helped.
[14:36] <deryck> I also have a presentation to work on, and some email/blogging to follow up from the conference last week.
[14:36] <deryck> that's it for me, I think.
[14:36] <abentley> Me too.
[14:37] <deryck> adeuring, anything else?
[14:37] <adeuring> no
[14:37] <deryck> adeuring, abentley -- great, thanks guys! Have a great day.
[14:37] <adeuring> abentley: bug 799785 (what I'm working on) is for a start obvious: one SQL statement needs 9 seconds or so. I have no clue what's wrong with the statement, so I'll ask deryck to run an "explain analyze".
[14:37] <abentley> deryck: you too.
[14:37] <adeuring> abentley: next step will be to see what postgresql tell me.
[14:37] <deryck> thanks!
[14:38] <deryck> adeuring, abentley -- do you guys mind moving the timeout/tech discussion back to #launchpad-dev?
[14:38] <deryck> others could find this useful.
[14:38] <adeuring> ah, right ...