[05:05] <jamalta_> hi, does anyone know how i can get a reference to the default db user?
[05:06] <wgrant> jamalta: There isn't really a default user. What are you trying to do?
[05:12] <jamalta> wgrant: i'm writing a test that needs to create fake records to the karmacache table
[05:13] <jamalta> so i have to switch db users to one that has write access to that tab le
[05:13] <jamalta> table*
[05:13] <jamalta> and i need to switch back to the regular user after i'm done
[05:13] <jamalta> but i can't find how to get a reference to it
[05:13] <jamalta> wgrant: you can look at the diff here https://code.edge.launchpad.net/~jamalta/launchpad/bug-127489/+merge/10785 to see what i'm doing exactly
[05:14] <wgrant> jamalta: Ah, I see.
[05:14] <wgrant> Let me have a look...
[05:14] <jamalta> wgrant: Thank you :)
[05:14] <jamalta> I got lost trying to find it
[05:15] <wgrant> jamalta: Have a look at lp.registry.tests.test_distributionsourcepackage
[05:15] <wgrant> switchDbUser is the magic method.
[05:17] <jamalta> wgrant: Oh, ok.. that should work then, thanks :)
[05:17] <jamalta> I am using config.karmacacheupdater.dbuser, so should I change it to match the way it is done in that test instead?
[05:18] <wgrant> jamalta: Probably. It probably doesn't really matter, but most tests seem to use a literal.
[05:19] <jamalta> wgrant: Thank you for your help, I will use that route then
[08:37] <lifeless> hmmm, I think that makes 5 bugs submitted today
[08:42] <wgrant> Ah, excellent. It is fairly easy to get dev primary archives set up to overlay on top of a real primary archive. That makes testing muuuuch easier.
[08:49] <wgrant> lifeless: What's the best way to get lpnet7 kicked?
[08:57] <lifeless> spm: ^
[08:57] <lifeless> try a sysadmint hat might be around
[08:57] <lifeless> failing that I'll escalate
[08:58] <lifeless> how long as it been down for?
[08:58] <wgrant> lifeless: Around 1.5 hours, I'd say
[08:58] <wgrant> Could be more.
[08:59] <lifeless> is it still in rotation?
[08:59] <wgrant> It is.
[08:59] <lifeless> ok
[08:59] <wgrant> So 502s are more frequent than they should be.
[08:59] <lifeless> we'll give spm 5-10 then I'll ring the SA's
[08:59] <wgrant> Great.
[09:10] <lifeless> escalated
[09:11] <lifeless> thought I really have to wonder just how much you're using lp that you're noticing :P
[09:13] <wgrant> lifeless: 1/8 isn't small.
[09:20] <lifeless> anyhoo I escalated
[09:21] <wgrant> lifeless: Thanks.
[09:21] <lifeless> the long suffering elmo is on the case
[10:37] <wgrant> maxb: I still can't reproduce those failures on a clean Karmic installation.
[10:37] <maxb> hrm
[10:37] <maxb> Most puzzling
[10:38] <maxb> What about the "Unable to find mandatory field 'files' in the changes file." ones?
[10:38] <wgrant> I installed it by using plain rocketfuel-setup, then adding your PPA and installing launchpad-developer-dependencies.
[10:38] <wgrant> maxb: Those work fine.
[10:39] <maxb> This is quite confounding
[10:39] <wgrant> Incredibly so.
[10:39] <wgrant> You say you can reproduce on two systems?
[10:40] <maxb> certainly the DONE != ACCEPTED one
[10:41] <wgrant> I've run that test on two machines in three configurations (one was reinstalled as another arch yesterday).
[10:41] <wgrant> It works fine.
[10:41] <wgrant> How strange.
[10:43] <maxb> Hm. I wonder if it's some bizarre interaction with something in my user account
[10:44] <maxb> My entire homedir is under Subversion, so the different machines are somewhat similar
[10:44] <wgrant> Are things oddly shared?
[10:44] <wgrant> Ahhh.
[10:44] <wgrant> That is possibly relevant.
[10:44] <wgrant> adduser will tell.
[10:49]  * maxb pondering what to chown, etc.
[11:24] <maxb> gary_poster: When you fix up the symlinks, don't forget to also fix up sourcecode/Makefile!
[11:27] <maxb> gahh, I hate shhh.py
[11:30] <maxb> wgrant: You didn't get bitten by Getting distribution for 'lazr.uri==1.0.1'.
[11:30] <maxb> Installing lazr.uri 1.0.1
[11:30] <maxb> Caused installation of a distribution:
[11:30] <maxb> lazr.uri 1.0
[11:30] <maxb> with a different version.
[11:30] <maxb> When doing your clean karmic test
[11:30] <maxb> Got None.
[11:30] <maxb>  ?
[11:30] <wgrant> maxb: No -- I didn't have launchpadlib installed yet.
[11:31] <wgrant> I've since installed it (which brought along python-lazr-uri), and everything remains happy.
[11:45] <maxb> huh
[11:45] <maxb> so now even if I purge python-lazr-uri, a clean make is now impossible
[11:45] <maxb> ImportError: No module named uri
[11:46]  * maxb has breakfast instead
[11:46] <wgrant> maxb: Impressive.
[11:47] <wgrant> Do you have any other lazr.* installed?
[11:47] <wgrant> eg. lazr.restfulclient?
[12:06] <maxb> wgrant: aha, that's it exactly
[12:07] <maxb> Gah. So now I have to choose whether to attempt to debug buildout or attempt to debug launchpad.
[12:07] <wgrant> maxb: buildout is scary. Run away.
[12:10] <maxb> Hrm. I wish launchpad wasn't so messy in /var/tmp/
[12:13] <wgrant> It's not too bad.
[12:13] <wgrant> You can blow it all away and it will be happy.
[12:13] <wgrant> And at least it puts stuff only there.
[12:16]  * mwhudson isn't completely sure about that
[12:17] <mwhudson> i think some tests still scribble into /tmp
[12:17] <maxb> Ideally it would all go under /var/tmp/launchpad-$USER/
[12:17] <mwhudson> (they should be fixed though)
[12:17] <maxb> Scribbling into /tmp/ isn't wrong, if it's genuinely temporary
[12:17] <maxb> WTF!?!?!? wgrant it works in my clean user
[12:17] <mwhudson> maxb: you are right about /var/tmp/launchpad-$USER/, but thinking about it makes me want to cry a little
[12:18] <wgrant> maxb: Excellent!
[12:18] <wgrant> maxb: Now, bonus points for working out what it was.
[12:18] <wgrant> maxb: My first try would be copying over bashrc and the like.
[12:24] <gary_poster> maxb, wgrant: what's the problem?
[12:24] <maxb> gary_poster: Which problem would you like to talk about first? :-)
[12:24] <wgrant> There are a few.
[12:25] <gary_poster> maxb: oh I dunno.  Just list em for me/
[12:25] <maxb> I have a couple of weird test failures that happen only for me, but on all my systems. We're now thinking that it's something in my common .bashrc or similar
[12:25] <gary_poster> huh
[12:25] <maxb> And, it's currently impossible to bootstrap launchpad on karmic, if you have python-lazr-* system packages installed. buildout gets confused
[12:29] <maxb> And, when you fix up the zope-removal properly, don't forget to look at sourcecode/Makefile :-)
[12:29] <gary_poster> grr.  I spent a fair amount of time trying to make that kind of bootstrap problem go away.
[12:29] <gary_poster> and did so for all of the instances I knew about.
[12:29] <gary_poster> zope-removal: ack, I saw your ping.  thanks.
[12:31] <gary_poster> so maxb, those are the 3 problems: (1) something on your system causes test failures only for you.  (2) buildout's bootstrap is broken on karmic if you have lazr.* Installed.  (3) I missed some things in my zope branch removal.
[12:32] <maxb> yup
[12:33] <wgrant> (1) is more specifically something to do with a shared home directory
[12:33] <maxb> I think it's down to my .bashrc
[12:33] <maxb> I'm bisecting it now
[12:33] <gary_poster> maxb: I can dupe 2 and 3 on my own.  Fixing 3 should be relatively easy, and once I've seen 2 hopefully I'll know what's up.  1 is harder.  I see your clean user works fine.  oh, shared home directory...
[12:33] <gary_poster> ok
[12:34] <gary_poster> maxb: could you pastebin me the traceback from (2)
[12:34] <gary_poster> when you get a chance
[12:35] <maxb> There's two flavours of (2) - if you have python-lazr-uri installed, buildout goes to install lazr.uri==1.0.1, but ends up installing 1.0 instead, catches this mistake, and aborts
[12:35] <maxb> Then, if you purge python-lazr-uri but still have python-lazr-restfulclient, you get a horrendous traceback with the ImportError I mentioned
[12:37] <maxb> I'll get pastes for both, but it'll be 15mins or so
[12:38] <gary_poster> maxb: is this during the bootstrap or the buildout?  It sounds like buildout.
[12:38] <maxb> um, the bit where it populates eggs/ from download-cache/dist/ ?
[12:38] <gary_poster> buildout, ok
[12:41] <gary_poster> maxb: I suspect this is new because we have things packaged for karmic that are not packaged in jaunty; and our lazr packages have had some build issues.  I think I've addressed all of them in branches as of this weekend--need to get some reviewed and landed.  I still had hoped that we would be isolated from things like this, but oh well, I'll try again.
[12:42] <maxb> :-) thanks
[12:44] <gary_poster> maxb: IRT the two flavors, the first flavor is more interesting to me.  The second one is kind of corollary of the first.  The first problem is "Gary thought we were protected from site-packages now (we are in Jaunty), but it is still leaking."  (Or lazr.uri packaging is more hosed than I thought--it's possible that it is packaged as 1.0.1 but then declares that it provides 1.0, which would explain the problem)
[12:45] <maxb> !info python-lazr-uri karmic
[12:46] <gary_poster> maxb: the second problem is: when you take out a dependency of a package, and you try to use that package, it breaks. :-)  the only way it is related to buildout/launchpad is that I had hoped we wouldn't see those packages
[12:46] <gary_poster> we don't in jaunty :-/
[12:46] <gary_poster> at least for the examples I have seen
[12:47] <maxb> I don't really understand what you mean by "when you take out a dependency of a package, and you try to use that package"
[12:48] <maxb> And unrelated: wgrant: So the DONE != ACCEPTED failure is apparently caused by me changing my umask from 022 to 002
[12:48] <gary_poster> maxb: lazr.restful depends on lazr.uri.  you removed lazr.uri, and lazr.restful breaks.  It makes sense in isolation.
[12:48] <maxb> oh.... but what stopped it from trying again to install lazr.uri first?
[12:48] <gary_poster> Ah, yes, I vaguely recall having been burned by umask in the past
[12:49] <gary_poster> I'm sorry you were hit by it.  Would you send an email to the list about it?  Others will have more context on that than I
[12:49]  * maxb afk 5mins
[12:49] <gary_poster> why didn't it try to install lazr.uri?  Yeah, good question.
[12:50] <wgrant> maxb: I spent some hours this morning working out a lp-buildd umask issue...
[12:50] <gary_poster> I regard it (maybe incorrectly) as a corollary of the first one, like I said
[12:50] <gary_poster> anyway, I need to run go do family things, but maxb, these things (2 and 3, in particular; someone else may need to look at what seems to be the umask issue, maybe wgrant?) will be top billing for me.
[12:52] <wgrant> maxb: Let's see if I can repro it.
[12:56] <wgrant> maxb: That does the DONE != ACCEPTED one, but not the others :(
[13:01] <maxb> mhm, ok then
[13:03] <maxb> I wasn't actually running anything but that one test whilst searching for the problem, I'm trying the other two now
[13:05] <wgrant> maxb: Ahaha.
[13:06] <wgrant> ERROR: Queue item ignored: Bad umask; expected 022, got 002
[13:06] <wgrant> So, not an entirely unexpected failure.
[13:07] <maxb> ah... where did that vital piece of info disappear to?
[13:07] <wgrant> maxb: The BufferLogger that the previous statement logs to.
[13:07] <maxb> So did it actually end up anywhere useful in a test run, or did you have to run things manually?
[13:08] <wgrant> maxb: Had to alter the code manually.
[13:09] <wgrant> maxb: (print logger.buffer.read())
[13:11] <maxb> ok, I'm on the trail of what's breaking the uploadprocessor tests for me
[13:12] <wgrant> Great.
[13:21] <maxb> riiight
[13:21] <maxb> so the last two are due to my ~/.devscripts
[13:25] <wgrant> Aha.
[13:26] <wgrant> So.
[13:26] <wgrant> On to 2.5!
[13:26]  * wgrant shall try to set it up tonight.
[13:31] <maxb> DEBUILD_DPKG_BUILDPACKAGE_OPTS="-us -uc"   <-- upsets launchpad
[13:32] <maxb> so I guess I need to find the appropriate place to apply a --no-conf option in the testsuite
[14:32] <wgrant> maxb: OK, test suite running fairly happily with 2.5. I'll poke at any real failures (eg. soyuz-set-of-uploads.txt, which looks unfortunate...) tomorrow.
[14:32] <maxb> nice :-)
[14:33] <maxb> Now if I can just figure out why bzr import-dsc is barfing, I'll try to get my launchpad-dependencies branches created.
[14:33] <maxb> And then progress to actually preparing submission branches for some of the stuff I've accumulated in ~maxb/launchpad/python2.5
[14:34] <wgrant> maxb: Did you turn of shhh.py in there?
[14:34] <wgrant> I noticed the build was fairly noisy.
[14:34] <maxb> yes
[14:35] <maxb> accidently at first, but I didn't feel like reverting :-)
[14:36] <wgrant> Are you getting lots of "/home/wgrant/launchpad2.5/lp-sourcedeps/eggs/pytz-2009j-py2.5.egg/pytz/__init__.py:32: UserWarning: Module lazr was already imported from None, but /home/wgrant/launchpad2.5/lp-branches/python2.5/lib is being added to sys.path\n  from pkg_resources import resource_stream"?
[14:43] <maxb> yes, and that's recent
[14:44] <maxb> but I think Gary's aware and has some thoughts on that one
[20:44] <lifeless> moin
[20:54] <mwhudson> good mornign
[21:20] <lifeless> mwhudson: so, liking your current role?
[21:20] <lifeless> or going whoa, where to start?
[21:25] <maxb> Gah. gah. gah. /me is constructing a branch for launchpad-dependencies, and has just discovered that it basically forked for dapper vs. feisty, with each branch using the same version numbers for entirely different packages
[21:27] <mwhudson> lifeless: somewhere in between those two :)
[21:27] <mwhudson> i'm glad i've got 4 weeks left, let's say
[21:28]  * mwhudson breaks fast
[21:28] <lifeless> mwhudson: :P
[21:28] <lifeless> maxb: whats the goal of this archaeology/
[21:29] <thumper> morning
[21:29] <maxb> There is very little point. I'm just being obsessive about producing an accurate branch representing past history, if I do so at all
[21:30] <thumper> mwhudson: still up for a call at 9?
[21:35] <mwhudson> thumper: sure
[21:55] <mwhudson> thumper: having said that, 9:10 or so would be better
[21:58] <thumper> ok
[22:12] <wgrant> Gr.
[22:13] <wgrant> Tests that rely on set() ordering make me sad.
[22:13] <mwhudson> wgrant: KILL
[22:13] <mwhudson> thumper: call?
[22:15] <wgrant> maxb: Dammit. I managed to run 'make check' in the same shell that I had my umask set to 002 from earlier.
[22:15] <maxb> :-)
[22:15]  * thumper nods
[22:16] <maxb> ah well, you know exactly what failure that causes, so no problem :-)
[22:16] <mwhudson> thumper: skype desn't think you're online, is it wrong?
[22:16] <thumper> mwhudson: yes, I'm trying to get to you too
[22:16] <wgrant> maxb: I'm hoping it won't cause any others.
[22:16] <maxb> it didn't for me
[22:17] <wgrant> maxb: Not even on 2.5?
[22:18] <maxb> Well I admit I'm conjecturing a bit, but the chances of a test being disrupted by umask on 2.5 but not being disrupted by umask on 2.4 seem vanishingly small
[22:18] <thumper> https://answers.edge.launchpad.net/launchpad-code/+question/81385
[23:00] <jml> hi
[23:04] <spm> hey jml
[23:04] <jml> spm, hi :)
[23:05] <lifeless> hi jml
[23:05] <jml> lifeless, g'day
[23:05] <jml> lifeless, I had a look at your subunit filter patch last night. It looked like it deserved more concentration than I had though.
[23:06]  * jml fires off 4 ec2test runs
[23:08] <lifeless> jml: thanks
[23:17] <jml> thumper, hi
[23:17] <thumper> jml: morning
[23:17] <jml> thumper, you available to talk today?
[23:18] <thumper> yes, at some stage
[23:19] <jml> thumper, cool. when do you think?
[23:19] <thumper> jml: when did you want to talk?
[23:19] <thumper> I think all the time :)
[23:19] <jml> thumper, soon-ish, so I can get on with other stuff
[23:19] <thumper> jml: ok, give me a few minutes to get a cuppa, then we can tal
[23:19] <thumper> k#
[23:19] <jml> thumper, cool.