[00:11] <lifeless> flacoste: we're waiting for my patch disabling the edge redirect code to propogate through QA
[00:15] <wgrant> lifeless: What about recipes?
[00:23] <lifeless> wgrant: we're waiting for N things
[00:23] <lifeless> wgrant: one at a time
[00:32] <wgrant> lifeless: But if the redirect removal lands, then recipes vanish from Launchpad.
[00:32] <wgrant> lifeless: Which may be slightly undesirable.
[00:33] <wgrant> s/lands/deloys/
[00:33] <wgrant> +p
[00:37] <lifeless> huh, no
[00:38] <lifeless> food, whilst I leave you to look closer.
[02:11] <LPCIBot> Project devel build (156): FAILURE in 3 hr 33 min: https://hudson.wedontsleep.org/job/devel/156/
[02:11] <LPCIBot> * Launchpad Patch Queue Manager: [r=bac][ui=none][bug=666580] Make getMessageDispositions much more
[02:11] <LPCIBot> efficient in the number of DB queries.
[02:11] <LPCIBot> * Launchpad Patch Queue Manager: [r=jml][ui=none][no-qa] Remove with_statement.
[02:11] <LPCIBot> * Launchpad Patch Queue Manager: [r=jml][ui=none][bug=54946, 496574, 497282, 611258,
[02:11] <LPCIBot> 618955] New almost-fully-asynchronous buildd-manager with lots of hot
[02:11] <LPCIBot> sexy bug fixes.
[02:31] <wgrant> lifeless: I see nothing in that MP which enables BFB on lpnet.
[02:31] <wgrant> Unless you've also changed the prod configs, I guess.
[02:34] <lifeless> wgrant: disabling the edge redirect doesn't remove the edge appservers
[02:34] <lifeless> and yes, the prod configs have (naturally) changed
[02:36] <wgrant> lifeless: It doesn't remove them, but it stops people from being redirected, so it effectively removes them.
[02:36] <thumper> lifeless: did you change the prod config to enable recipes?
[02:37] <thumper> lifeless: it isn't is_edge
[02:37] <lifeless> no
[02:37] <lifeless> we're adding a feature scope to support recipes
[02:37] <lifeless> we're stalled on the edge removal on that
[02:38] <wgrant> ... that is what I was asking.
[02:38] <wgrant> Aha.
[02:38] <lifeless> wgrant: see lp-foundations bugs
[02:43] <thumper> lifeless: why stalled on edge removal?
[02:44] <lifeless> jml doesn't want recipes on prod for all users
[02:44] <lifeless> only beta
[02:44] <lifeless> (and preferrably a dedicated smaller beta team)
[02:44] <lifeless> so we need to add a scope that selects teams.
[02:45] <thumper> ok
[02:46] <lifeless> thumper: there's no panic on removing edge, we have time to do it methodically
[02:46] <thumper> ok
[02:47] <lifeless> all due haste, no panic.
[02:50] <wgrant> lifeless: So you just CP'd up to r11738?
[02:50] <lifeless> deployed, yes.
[02:50] <wgrant> Hopefully the publisher won't explode.
[02:50] <lifeless> CP's no longer exist.
[02:50] <wgrant> Shh.
[02:50] <lifeless> wgrant: why would it? We didn't deploy to soyuz machines
[02:50] <wgrant> Ah.
[02:50] <wgrant> So the Fix Released was a lie.
[02:51] <lifeless> wgrant: which bug
[02:51] <wgrant> Bug #655690
[02:52] <lifeless> wgrant: well, its a nonfunctional change, right?
[02:52] <lifeless> wgrant: or is it broken?
[02:53] <wgrant> lifeless: No, it's fine. Shouldn't be a problem, except it's happened in the past that a CP has been partially deployed, marked as Fix Released, something has broken, and then confusion abounds when you're looking at the wrong code.
[02:53] <lifeless> well the rev is on the bug
[02:54] <wgrant> True.
[02:54] <lifeless> I'm not sure what we should do here.
[02:54] <lifeless> if it was a functional change, I wouldn't have toggled it.
[02:54] <wgrant> Merge Fix Committed and Fix Released into Fixed, like mpt has wanted to do forever?
[02:55] <lifeless> :)
[02:57] <bac> thumper, did you see hudson failed on your branch?
[02:58] <bac> thumper, well not just your branch...
[03:01] <thumper> no
[03:10]  * thumper afk to collect car
[03:12] <thumper> bac: looks screwed up
[03:12] <thumper> bac: as in hudson looks screwed up, not the branch
[03:52]  * StevenK prods at hudson before bed
[03:53] <LPCIBot> Project db-devel build (103): FAILURE in 3 hr 57 min: https://hudson.wedontsleep.org/job/db-devel/103/
[03:54] <StevenK> That devel change is odd
[03:54] <StevenK> Er, s/change/test failure/
[03:55] <StevenK> The test suite is run under sudo, so I am tempted to blame a recent landing
[03:55] <thumper> yes, yes it is
[04:17] <thumper> wallyworld_: skype?
[04:17] <wallyworld_> ok
[04:22] <wallyworld_> thumper: now?
[04:22] <thumper> wallyworld_: I can't hear you :)
[04:22] <wallyworld_> i can't hear you either
[04:23] <wallyworld_> !#@#@%@ pulse or whatever
[04:23] <wallyworld_> i may have to reboot :-(
[04:23] <thumper> ack
[05:00] <thumper> contains(@class, "js-action")
[05:36] <lifeless> thumper: you might like https://code.edge.launchpad.net/~lifeless/launchpad/zope.testing/+merge/39423
[05:36] <lifeless> jml: or you may like it.
[05:36] <lifeless> gnight
[06:03] <LPCIBot> Project devel build (157): STILL FAILING in 3 hr 32 min: https://hudson.wedontsleep.org/job/devel/157/
[06:03] <LPCIBot> Launchpad Patch Queue Manager: [r=lifeless][ui=none][no-qa] Prevent the atexit warning that occurs
[06:03] <LPCIBot> when tests are run within the LibrarianLayer.
[08:54] <adeuring> good morning
[09:03] <mrevell> Hello
[09:12] <bac> hello mrevell, adeuring
[09:17] <wgrant> Someone is going to need to manually apply the permission changes from db-devel r9888, or we are going to have an awful lot of branch scan failures.
[09:18] <wgrant> (that was merged into devel later on, and has security.cfg changes, which can't be deployed directly without downtime)
[09:18] <wgrant> (but the revs that need the new perms were deployed earlier today)
[09:31] <mthaddon> wgrant: interesting - this seems to be something of a failure in process... :/
[09:32] <wgrant> mthaddon: One that people have been warned about.
[09:32] <wgrant> I don't recall exactly where.
[09:32] <wgrant> But it was brought up recently.
[09:34] <mthaddon> yeah
[09:35] <mthaddon> so allegedly qastaging should fix this, but it seems this wasn't exactly qa-ed there...
[09:36] <wgrant> qastaging may have been set up too late.
[09:36] <wgrant> So it may have had the right perms from the start.
[09:36] <mthaddon> well, and we're not running scripts on it yet...
[09:36] <wgrant> Ah, that would also do it.
[09:36] <mthaddon> but my point is the revno was blessed for rollout without having really been QA-ed
[09:37] <wgrant> It's almost impossible to completely QA something like that.
[09:37] <wgrant> But more could have been done.
[09:37] <mthaddon> anyway, thx for bringing it up
[09:37] <wgrant> It's also possible that it was QA'd properly on db-devel, and then merged without properly being QA'd on devel.
[09:37] <wgrant> But anyway.
[09:42] <henninge> jtv: yup, the main facet feigns ignorance about a series branch to non-privileged users.
[09:42] <henninge> if that branch is private.
[09:43] <jtv> henninge: and ours does the same for the development branch but not for the export branch?  Or does it fail to feign and so feint when either is present?
[09:44]  * jtv gets confused about spelling
[09:44] <henninge> jtv: ;-) the latter.
[09:45] <henninge> jtv: so, if translations would say somthing like "translations are imported from/exported to a private branch" it would already give away more information than the main page which claims "No revision control details recorded for ..."
[09:46] <jtv> Right.
[09:46] <jtv> Well, mystery solved I guess.  Good job.  :)
[09:47] <henninge> So our page will have to look to non-priv users as if no branch sync had been set up.
[10:05] <LPCIBot> Yippie, build fixed!
[10:05] <LPCIBot> Project devel build (158): FIXED in 3 hr 33 min: https://hudson.wedontsleep.org/job/devel/158/
[10:05] <LPCIBot> Launchpad Patch Queue Manager: [testfix][rs=bac][ui=none][bug=54946, 496574, 497282, 611258,
[10:05] <LPCIBot> 618955][rollback=11801]
[13:11] <lifeless> jml: oh hai
[13:11] <jml> lifeless: hello
[13:12] <lifeless> jml: I've fixed layers
[13:12] <jml> lifeless: glad to hear it.
[13:13] <lifeless> jml: it needs a review :)
[13:13] <jml> lifeless: cool. I'll look at it once I'm done w/ email
[13:17] <lifeless> -> food
[13:39] <LPCIBot> Project devel build (159): SUCCESS in 3 hr 34 min: https://hudson.wedontsleep.org/job/devel/159/
[13:39] <LPCIBot> Launchpad Patch Queue Manager: [r=allenap][ui=none][bug=665407] Add invalid-link style to invalid lp
[13:39] <LPCIBot> branch short links and prevent click through
[13:47] <lifeless> jml: have you picked up a key?
[13:47] <jml> lifeless: I don't think so.
[13:51] <lifeless> I'll go get one
[14:02] <flacoste> lifeless, jml: around?
[14:04] <lifeless> jml: bony 3
[14:04] <lifeless> flacoste: yes
[14:04] <jml> lifeless: I don't understand...
[14:04] <StevenK> It sounds like a room title to me
[14:05] <flacoste> lifeless, jml: call me when you are ready
[14:06] <lifeless> jml: all the meeting rooms are booked; marianna has put us in bonaire 3
[14:07] <lifeless> flacoste: skype ?
[14:08] <flacoste> lifeless: skype or POTS, whatever works best for you guys
[14:08] <lifeless> flacoste: rephrasing; please join skype
[14:08] <flacoste> lifeless: i should be there already
[14:09] <flacoste> lifeless: are you hearing me?%
[14:10] <allenap> jml: I have some grants for production that accompany a security.cfg change that has already landed in devel. Are you the person I should ask to review these?
[14:11] <allenap> It's probably already in stable too, but I think all the grants are for script users so it hasn't caused problems so far.
[14:14] <bigjools> allenap: he's in a session
[14:15] <allenap> bigjools: Thanks. I'll email him (unless you happen to know who else I could/should contact?).
[14:16] <bigjools> allenap: I can review/grant for you if you want
[14:17] <allenap> bigjools: Awesome, thanks. http://paste.ubuntu.com/520757/
[14:18] <bigjools> allenap: how do you know you have all the necessary changes?
[14:19] <allenap> bigjools: Because you're reviewing it for me to check ;)
[14:19] <bigjools> !
[14:19] <bigjools> allenap: it's my job to ask probing questions :)
[14:20] <allenap> bigjools: Do you know if it's possible to get Postgres to puke up it's permissions so I can compare before and after?
[14:21] <bigjools> allenap: yeah I think I've seen something, can't remember what it is
[14:21] <allenap> bigjools: Okay, I'll investigate. Thank you for your probe.
[14:22] <bigjools> allenap: so assuming that you've already landed the changes with these then it looks ok - my only concern is that you've not missed anything and it would be nice to somehow verify that.
[14:22] <bigjools> allenap: FWIW, I also bow to your grep skillz
[14:22] <StevenK> If you could get a permissions dump from a running development instance, that would probably help for comparion
[14:23] <StevenK> *comparsion
[14:23] <allenap> StevenK: Yeah, that's what I have in mind.
[14:24] <bigjools> jml: when you have a moment I could do with chatting about the new buildd-manager - the twistd process is hitting all of one core on mawson and strace is not helpful.
[14:39] <bigjools> deryck: did you see bug 667215? :)
[14:42] <bigjools> gary_poster: hi
[14:42] <gary_poster> hey on call but off soon bigjools
[14:42] <bigjools> gary_poster: np,  I am in a session soon though.  Just wanted to talk about bug 667183
[14:44] <bigjools> I'll comment on the bug
[14:45] <gary_poster> ack
[14:48] <deryck> bigjools, yeah :-)  I haven't replied or un-security'ed it yet.  It's crying out for a clever response, and I don't want to disappoint. :-)
[14:48]  * deryck kids obviously
[14:48] <deryck> I just haven't replied yet.
[14:48] <bigjools> deryck: seems ripe for "opinion" to me :)
[14:49] <deryck> heh
[14:49] <bigjools> abuse of the security tag is annoying though
[14:51] <deryck> yeah
[14:53] <deryck> launchpad session!
[14:55] <jml> bigjools: will do.
[14:55] <allenap> bigjools: You were very right to ask that question: http://paste.ubuntu.com/520782/
[14:58] <bigjools> allenap: :)
[15:33] <bac> mars ping
[15:33] <mars> Hi bac
[15:33] <mars> bac, regarding your earlier question, Ursinha would know
[15:33] <bac> oh, ok
[15:33] <mars> bac, and your EOD was 7:00am for me, I think? :)
[15:33] <bac> Ursinha: ping...
[15:34] <rockstar> sinzui, give me an example of your perfect pagetest story.
[15:34] <bac> mars: yeah
[15:34] <bac> mars: so you don't know which tools are supposed to set the bad-commit tags?
[15:34] <bac> Ursinha: do you ?  ^^
[15:35] <bac> if that could be documented on the the QAForContinuousRelease pages i think people would understand the process better
[15:35] <mars> bac, not off the top of my head, no.  Ursinha and lifeless worked that out, and I remember something on the list about it having the tags be manual(?)
[15:35] <bac> mars: really?  not what the wiki says at all.
[15:36] <bac> well, i won't be getting my answer today, then.  :)
[15:36] <jcsackett> hey, bac, as long as your online did you see my comment on the bug(s) we were talking about yesterday?
[15:36] <mars> bac, that's why I did not reply.  I thoguht lp-land or ec2 land should have done everything for you
[15:36] <bac> mars: me too.  this branch was full of mysteries.
[15:37] <bac> bugs didn't get linked, diff didn't update, tags didn't update, MP didn't get set to 'merged'.  all very odd.
[15:37] <bac> some of it may be to branch scanner weirdness today
[15:37] <bac> jcsackett: i did.  thanks for following through.
[15:37] <jcsackett> bac: no problem. were you able to qa your stuff?
[15:37] <bac> jcsackett: in the future, could you send me email?  sometimes my IRC client tells me i got pinged but i cannot find it in the scrollback
[15:38] <bac> jcsackett: i did
[15:38] <jcsackett> bac: oh, sure.
[15:38] <jcsackett> excellent.
[15:46] <bigjools> bac: hello, would you mind testing a patch for me to fix that failing test of mine?
[16:10] <lifeless> flacoste: can you invite me to the ISO call tomorrow/today ?
[16:13] <flacoste> lifeless: sure
[16:13] <flacoste> lifeless: not sure, it it's going to happen though given that elmo is at UDS, but we can probably have the call with tom
[16:16] <lifeless> flacoste: I'd like to talk with you, charlie & tom about  some ops stuff from chatting with statik
[16:17] <lifeless> flacoste: that call seems ideally structured
[16:17] <flacoste> lifeless: sure
[16:17] <flacoste> lifeless: you should have the invite
[16:18] <flacoste> lifeless: btw, you aware that converting daily builds to feature flag is a blocker for edge removal?
[16:18] <lifeless> flacoste: yes, I said so on the prereq bug
[16:19] <flacoste> what bug is it?
[16:19] <lifeless> flacoste: bug 666538
[16:19] <lifeless> (was just looking)
[16:19] <lifeless> flacoste: we don't need to panic about removing edge - all due caution, and all due haste IMO
[16:19] <lifeless> flacoste: we're already better off
[16:20] <lifeless> matsubara: ping
[16:20] <flacoste> lifeless: agreed, but the daily build conversion, did you intend to take it, or do we need to hand this off to the code team?
[16:20] <matsubara> hi lifeless
[16:20] <lifeless> matsubara: I'd like to interrupt you for a small but important thing.
[16:20] <matsubara> shoot
[16:20] <lifeless> matsubara: could you fold the 'edge' OOPS report summaries into lpnet.
[16:20] <lifeless> matsubara: they are now running the exact same code.
[16:20] <lifeless> matsubara: so we don't benefit from a separate report.
[16:21] <flacoste> lifeless: ok, i see that the bug is assigned to poolie
[16:21] <matsubara> lifeless, yes, are those instance not using the E* prefixes anymore?
[16:21] <lifeless> matsubara: prefixes haven't changed
[16:21] <flacoste> lifeless: so they are running the same code, but with a different config right?
[16:22] <lifeless> flacoste: -very- slightly different config; only practical change I know of is the recipe stuff being enabled.
[16:22] <flacoste> ok
[16:22] <lifeless> flacoste: oh, and the timeout is 13000 not 15000 - but again, the oops /types/ and /causes/ should be identical.
[16:23] <flacoste> right
[16:23] <flacoste> should we harmonize the timeouts?
[16:23] <lifeless> flacoste: on my todo :)
[16:23] <lifeless> flacoste: waiting for the 600 a day to reduce
[16:23] <flacoste> right, because of the 8.4 regressions
[16:23] <lifeless> flacoste: which will happen as more things are qad and deployed - we have several timeout fixes blocked on qa
[16:23] <lifeless> flacoste: right
[16:23] <flacoste> awesome
[16:24] <flacoste> this is really better
[16:24] <lifeless> StevenK: https://devpad.canonical.com/~lpqateam/qa_reports/deployment-stable.html - --please-- I know you're at UDS, but unqa'd code in trunk is a teamwide stall.
[16:24] <StevenK> lifeless: I'm trying!
[16:24] <lifeless> StevenK: what can I do to help?
[16:25] <StevenK> lifeless: Tell me why the function appears in the WADL but not in the actual API code
[16:26] <lifeless> flacoste: so the call is in 23.5 hours?
[16:26] <flacoste> yep
[16:26] <lifeless> StevenK: how do you mean? leonardr: we may need your help.
[16:26] <lifeless> flacoste: thanks, wicked.
[16:27] <leonardr> StevenK, give me a link?
[16:27] <lifeless> matsubara: so, for clarity - you're folding the E prefix into the lpnet reports ?
[16:27] <StevenK> lifeless: I'm in a session that I'm talking in, so I don't want to walk out
[16:27] <leonardr> what do you mean by "the api code"? you can't access it from launchpadlib?
[16:27] <matsubara> lifeless, yep
[16:27] <StevenK> leonardr: Right. I'm looking at say dir(maverick)
[16:27] <lifeless> matsubara: awesome, thank you very much. We can drop the edge-oops.html on lpqateam etc too, with this change.
[16:29] <matsubara> lifeless, I seem to remember you saying that the weekly summary is not useful, so I'll get rid of that as well
[16:30] <matsubara> Ursinha, what do you think ^?
[16:30] <lifeless> matsubara: yes please
[16:31] <Ursinha> reading
[16:31] <Ursinha> matsubara, that's cool, want me to do that along with qastaging changes?
[16:32] <matsubara> Ursinha, sure, getting you a diff, just a sec
[16:32] <leonardr> StevenK: i assume you're busy in the presentation, but when you get a minute, i need a link to the problematic branch (or maybe lifeless can give it)
[16:34] <StevenK> leonardr: rev 9303 or so in db-devel, I think
[16:34] <StevenK> http://bazaar.launchpad.net/~launchpad-pqm/launchpad/db-devel/revision/9903
[16:35] <matsubara> Ursinha, merge from here: lp:~matsubara/oops-tools/edge-no-more
[16:36] <Ursinha> thanks matsubara, will do that right now
[16:36] <matsubara> Ursinha, will go for lunch and post office errands. please add a MP and I'll take a look after lunch and will deploy this so we'll get the new reports tomorrow. thanks a lot!
[16:37] <Ursinha> sure, thanks matsubara-lunch!
[16:40] <lifeless> mwhudson: https://bugs.edge.launchpad.net/launchpad-code/+bug/667322
[16:46] <leonardr> StevenK: ok, so you have some tests that use launchpadlib, and those tests pass, so it should be working. i'd like to eliminate the possibility that your client-side launchpadlib is using a cached wadl file
[16:47] <leonardr> can you run your test script but set "httplib2.debuglevel = 1" before using Launchpad.login_with or equivalent?
[16:47] <StevenK> leonardr: Okay, doing
[16:48] <mwhudson> lifeless: i think the port already comes from launchpad-lazr.conf
[16:48] <mwhudson> lifeless: config.codebrowse.port
[16:49] <StevenK> leonardr: What do you need from that?
[16:49] <leonardr> StevenK: paste me the whole thing, but i especially need the first part
[16:49]  * mwhudson comments on the bug
[16:50] <StevenK> leonardr: http://paste.ubuntu.com/520833/
[16:50] <lifeless> mwhudson: thanks, I'll make new configs
[16:52] <leonardr> StevenK: you are using a cached wadl file. go into ~/.launchpadlib/api.dogfoot.launchpad.net/cache/ and look at the file that starts api.dogfood.launchpad.net,beta,-application,vnd.sun.wadl+xml
[16:53] <leonardr> see if derivedistroseries is in there
[16:53] <StevenK> leonardr: I don't have that directory, is: launchpad = Launchpad.login_with('qa-mawson', 'dogfood')
[16:54] <StevenK> leonardr: Is that right to to talk to dogfood?
[16:54] <leonardr> yeah. i misspelled dogfood in my earlier msg as "dogfoot"
[16:54] <leonardr> do you have a ~/.launchpadlib/api.dogfood.launchpad.net?
[16:54] <StevenK> Nope
[16:55] <StevenK> Which is why I'm questioning if my login call is right
[16:55] <leonardr> you're making calls to the web service
[16:56] <leonardr> do you have .launchpadlib at all?
[16:56] <lifeless> mwhudson: whats 'secret_path' for ?
[16:56] <mwhudson> lifeless: signing cookies
[16:56] <lifeless> is it sharable across processes ?
[16:56] <StevenK> leonardr: Sorry, I have .launchpadlib/api.dogfood.launchpad.net/ but not .launchpadlib/cache/api.dogfood...
[16:56] <mwhudson> yeah, it's a path to a file that contains the secret
[16:56] <lifeless> like, if we're running two codebrowsers
[16:57] <mwhudson> lifeless: different processes _need_ to share the same file content
[16:57] <leonardr> do you have cache *inside* api.dogfood?
[16:58] <leonardr> ie. when i do `ls /home/leonardr/.launchpadlib/api.dogfood.launchpad.net/cache/`, i see a file
[16:58] <mwhudson> lifeless: afk
[16:58] <StevenK> leonardr: Right
[16:58] <StevenK> leonardr: I do have that directory
[16:59] <leonardr> ok, is there a wadl file inside it, and if so, does the wadl file mention derivedDistroSeries?
[16:59] <StevenK> leonardr: Let me delete everything in that directory
[16:59] <leonardr> StevenK: ok, that's another effective tactic
[17:00] <StevenK> leonardr: Before I deleted it, no, it doesn't
[17:00] <StevenK> Let me do the effective tactic
[17:02] <StevenK> leonardr: Ah ha! Now it shows up
[17:02] <leonardr> StevenK: ok, that is your problem. wadl files are cached for one week
[17:02] <leonardr> this is fine for casual users, but when you do web service development, you need to make sure you clear them out
[17:03] <StevenK> leonardr: Why the two directories?
[17:03] <mwhudson> lifeless: back again
[17:03] <leonardr> StevenK: which two directories?
[17:05] <StevenK> leonardr: .launchpadlib/<api...>/cache versus .launchpadlib/cache/<api...>
[17:05] <leonardr> StevenL: you should not have .launchpadlib/cache/
[17:06] <leonardr> it may have been created by a very old version
[17:06] <leonardr> you can delete it
[17:06] <StevenK> Okay
[17:06] <lifeless> mwhudson: is cachepath safe to share ?
[17:06] <mwhudson> lifeless: yes
[17:06] <mwhudson> it's sqlite & there's no real difference between sharing between threads and sharing between processes
[17:08] <bigjools> Can I get a vic^Wvolunteer to run a test on revno 11801 of devel for me please?
[17:08] <lifeless> mwhudson: so log_folder, error_dir and oops_prefix are the only unique things ?
[17:09] <StevenK> leonardr: http://paste.ubuntu.com/520844/
[17:09] <lifeless> matsubara-lunch: when you return, can you add CB1 and CB2 oops prefixes?
[17:09] <mwhudson> lifeless: well, and port
[17:09] <mwhudson> lifeless: otherwise, yes
[17:10] <leonardr> StevenK: would it be easy for you to try to reproduce that error locally?
[17:10] <leonardr> just start up a local launchpad and run launchpadlib against 'dev'
[17:11] <StevenK> leonardr: I can try, but I also have code access to dogfood directly
[17:12] <lifeless> mwhudson: lp:~lifeless/lp-production-configs/codebrowse
[17:13] <leonardr> StevenK: ok, the most likely problem is that your named operation takes an argument that is of a schema field type for which there is no unmarshaller
[17:13] <leonardr> let me check your code
[17:13] <leonardr> i don't know why the automated tests wouldn't have caught this
[17:14] <lifeless> leonardr: if thats the case, will deploying it break other APIs ?
[17:14] <lifeless> if not, then we can qa-ok this patch and move on with deployments; we can iterate on the feature
[17:14] <leonardr> lifeless: no, it only means that this particular named operation is broken
[17:15] <lifeless> leonardr: great, thanks.
[17:15] <lifeless> bigjools: ok, so bad-commit explanation.
[17:15] <leonardr> StevenK: yeah, i don't think you can have a named operation take a List
[17:15] <StevenK> leonardr: Oh, drat
[17:15] <lifeless> bigjools: bad-commit-XXXX will block deployments until either a) the tag is removed or b) a branch with [rollback=XXXX] is landed (even if its not a rollback, thats just the tag to use.
[17:15] <StevenK> leonardr: Is there anything else I can do?
[17:16] <leonardr> let me look at the code/think
[17:16] <leonardr> bigjools or someone else who's been doing actual web service work might know
[17:16] <lifeless> the qa-* tag doesn't override the bad-commit
[17:16] <lifeless> once the rollback is present, then as long as the rollback rev will be deployed, it *unblocks* the bad-commit
[17:16] <lifeless> and at *that point* the qa-tag gets evaluated.
[17:17] <bigjools> StevenK, leonardr: nothing springs to mind but looking at IArchive might give inspiration.
[17:18] <bigjools> lifeless: where is the link between the rollback rev and the bad rev so it knows to do that?
[17:18] <leonardr> StevenK: the automated tests passed because you never passed in a value for any of the List arguments
[17:18] <bigjools> and I'm not sure I am really following this
[17:18] <jml> bigjools: StevenK: are you guys planning on going to https://blueprints.edge.launchpad.net/ubuntu/+spec/ubuntutheproject-foundations-n-releaseprocess ?
[17:18] <lifeless> bigjools: in the commit message for the rollback rev
[17:18] <bigjools> jml: yes
[17:18] <lifeless> bigjools: we need to iterate on this process support stuff too, to make it more dynamic.
[17:18] <jml> bigjools: cool. I really want to go but something just came up. glad you guys are.
[17:19] <StevenK> bigjools: IArchive.getBuildSummariesForSourceIds takes a List
[17:19] <bigjools> jml: when is it?
[17:19] <jml> 5:10
[17:20] <bigjools> StevenK: there's your inspiration then
[17:21] <leonardr> bigjools, StevenK, do we know that getBuildSummaries.. will actually work when passed a list?
[17:21] <bigjools> lifeless: I am still confused, let's go through it after this session
[17:22] <mwhudson> lifeless: i don't think you need the launchpad.conf & mail-configure-normal.zcml crap
[17:22] <bigjools> leonardr: yes. it's use in a UI page
[17:22] <mwhudson> lifeless: otherwise +1
[17:22] <bigjools> used
[17:22] <leonardr> StevenK: in that case, i think your problem is that you need to specify a value_type for the List
[17:23] <leonardr> otherwise, lazr.restful says "a list of what?" and can't validate the incoming json
[17:23] <bigjools> sounds sane
[17:24] <bigjools> hey jelmer, have you got time later today to talk about that task list?
[17:25] <jml> bigjools: do you want me to run your patch through ec2 land?
[17:26] <bigjools> jml: it would be nice to re-create it on someone's box first, but yes, that would help, thanks.
[17:26] <bigjools> jml: how's this look? http://pastebin.ubuntu.com/520807/
[17:26] <StevenK> leonardr: And then regenerate the wadl and remove the cached wadl?
[17:27] <leonardr> StevenK: i don't think you even need to do that, but it wouldn't hurt. you should be able to write an automated test that fails pretty easily, and then make it stop failing
[17:27] <jml> bigjools: you need to add a cleanup to revert the patch when the test is done
[17:27] <jml> bigjools: otherwise, perfect.
[17:27] <lifeless> mwhudson: everything has it :( don't want to experiment offhand
[17:27] <StevenK> leonardr: Right
[17:27] <bigjools> jml: why? it doesn't hurt to leave it
[17:27] <lifeless> bigjools: ok
[17:28] <bigjools> given that is going to be the "fix"
[17:28] <jml> bigjools: because you should only break test isolation when there's a very, very, very good reason
[17:28] <bigjools> hmm
[17:28] <mwhudson> lifeless: well, i'm pretty sure you don't need it, but fair enough i guess
[17:29] <mwhudson> bigjools, jml: the other option is to install the monkey patch at import time i guess
[17:29] <allenap> deryck: I just trod on your toes wrt bug 667347.
[17:29] <mwhudson> doing it in test setup and then not doing it in teardown is ick
[17:29] <allenap> deryck: Can you look at my comment in there and let me know if I should revert my change?
[17:31] <deryck> allenap, ah, no worries.  Thank thank thank you for triaging. ;) :)  It's never stepping on my toes. :-)
[17:31] <deryck> allenap, the comment is fine and good.  I just wanted to have the bugs together about trac, since his bugs came out of a UDS session.
[17:31] <matsubara> lifeless, the CB prefix is already known by oops-tools.
[17:31] <allenap> deryck: Cool.
[17:31] <lifeless> matsubara: so it will handle CB1 and CB2 automagically ?
[17:31] <lifeless> matsubara: there are two new error dirs as well
[17:32] <matsubara> well, CB1 and CB2 can't be prefixes
[17:32] <matsubara> you can't use digits in the prefix
[17:32] <lifeless> oh grah
[17:32] <lifeless> so CBA abd CBB ? Why can't you use digits ?
[17:33] <matsubara> because an oops id is formed by <day-since-epoch><prefix><unique-digit-for-the-given-oops-on-that-day>
[17:33] <matsubara> if you add a digit in the prefix, the regex will think that's part of the unique-digit part of the oops id
[17:34] <StevenK> lifeless: Ping
[17:34] <lifeless> hi
[17:34] <lifeless> matsubara: what regex
[17:34] <lifeless> matsubara: the OOPS is in a header in the file
[17:34] <StevenK> lifeless: Do you remember what you did on my laptop to make launchpad branches branch quicker?
[17:35] <lifeless> StevenK: we edited bzr to not use accelerator branches, didn't we?
[17:35] <StevenK> lifeless: It was somewhere in launchpad/.bzr ?
[17:35] <lifeless> StevenK: or was it making the source branch a lightweight branch?
[17:35] <StevenK> lifeless: It was lightweight
[17:35] <lifeless> bzr remove-tree on your devel/db-devel branches
[17:35] <StevenK> lifeless: I think it's interferring with pushing branches to lp and stacking
[17:35] <lifeless> StevenK: no
[17:36] <matsubara> lifeless, oops_re in models.py /me looking for a link
[17:37] <lifeless> matsubara: can you file a bug on this, its an unnecessary constraint, as long as no prefix is a prefix of another prefix.
[17:37] <bigjools> mwhudson: normally I'd 100% agree but I'm poking in the upstream's fix.  I guess I will do it anway since in retrospect it's kinda nasty.
[17:38] <matsubara> lifeless, https://bazaar.launchpad.net/~launchpad-pqm/oops-tools/trunk/annotate/head%3A/src/oopstools/oops/models.py
[17:38] <mwhudson> bigjools: either poke it in for the entire duration of the process or for an isolated controlled time, not "approximately half of the time"
[17:38] <mwhudson> :-)
[17:38] <mwhudson> in this case it won't matter, apart from wtfs/min
[17:39] <bigjools> mwhudson: meh :)
[17:40] <lifeless> I need someone to land a branch for me.
[17:40] <lifeless> echo "star-merge bzr+ssh://bazaar.launchpad.net/~lifeless/lp-production-configs/codebrowse bzr+ssh://bazaar.launchpad.net/~launchpad-pqm/lp-production-configs/trunk" | gpg -cl | mail launchpad@pqm.canonical.com -s "[r=mthaddon][ui=none] Reconfigure codebrowse to support HA: new log and error dirs needed."
[17:40] <lifeless> preferrably someone not at UDS (mail queuing is odd here just now, for some reason)
[17:40] <lifeless> flacoste: ^
[17:44] <bigjools> jml: http://pastebin.ubuntu.com/520864/
[17:44] <lifeless> flacoste: nvm, got it to work
[17:44] <jml> bigjools: +1
[17:44] <bigjools> jml: if that looks ok then I'll push up a new builderslave-resume and you can poke ec2land it
[17:44] <bigjools> great
[17:44] <bigjools> one sec
[17:45] <matsubara> lifeless, I don't think it's unnecessary
[17:45] <bigjools> jml: ok lp:~julian-edwards/launchpad/builderslave-resume has that change, thanks.  Maybe I should get an ec2 account.... then again maybe not.
[17:46] <lifeless> matsubara: ok, why is it necessary?
[17:46] <jml> bigjools: give a man fish... give a man a fishing license...
[17:47] <bigjools> jml: I hate fish :)
[17:47] <bigjools> come to think of it, I hate fishing
[17:48] <jml> bigjools: what was your commit message
[17:48] <bigjools> jml: [r=jml][ui=none][bug=54946, 496574, 497282, 611258, 618955] New almost-fully-asynchronous buildd-manager with lots of hot sexy bug fixes.
[17:49] <matsubara> lifeless, because it's used to find the actual prefix in the oops-id. it's useful to know the prefix to find the files in the filesystem and to query the Prefix table. and this already works as is and changing it just because isn't a good reason either
[17:50] <lifeless> matsubara: we have more servers than letters coming up
[17:50] <lifeless> matsubara: LPNETAA is rather ugly
[17:50] <lifeless> matsubara: would LPNET1- work as a prefix ?
[17:50] <matsubara> and we'll have to have something that supports the old oops-id anyway for backwards compatibility
[17:51] <lifeless> matsubara: well the old is a strict subset of the new, right ?
[17:51] <matsubara> well, let's change the oops format then
[17:51] <lifeless> matsubara: thats already happening, but I don't see why its related to this
[17:51] <matsubara> oops-wsgi already generates oops-ids in a different format
[17:52] <lifeless> what does it do?
[17:53] <bigjools> sinzui: do you know if there is a way to disable custom_widgets based on a different widget's radio button selections?  Or do I need some custom JS?
[17:55] <matsubara> lifeless, not sure exactly but they changed it to include the id of the thread the oops was generated or something like that.
[17:55] <lifeless> ok
[17:55] <lifeless> so I don't really care either way
[17:55] <lifeless> here is what I would love to see us achieve:
[17:56] <lifeless>  - use numbers for numbers.
[17:56] <lifeless> or better yet
[17:56] <lifeless>  - stop manually assigning and managing this stuff
[17:56] <lifeless> its a terrible burden on deployment to have to care about this detail
[18:00] <jml> bigjools: for your other issue, I'm free in the 16:00 session
[18:08] <matsubara> lifeless, https://bugs.edge.launchpad.net/oops-tools/+bug/667373
[18:12] <matsubara> lifeless, https://bugs.edge.launchpad.net/oops-tools/+bug/667375
[18:39] <lifeless> matsubara: 667375 is a dupe
[18:39] <lifeless> matsubara: 667373 is great, thanks.
[18:40] <matsubara> lifeless, do you think it's a dupe of bug #271411?
[18:41] <lifeless> absolutely
[18:41] <matsubara> lifeless, that's fix release :-)
[18:41] <matsubara> released
[18:41] <lifeless> matsubara: then why are we having to add things?
[18:41] <matsubara> so, yeah, I fixed #271411 but the next step is to make everything automagically
[18:42] <lifeless> matsubara: ok cool
[18:42] <lifeless> I see the difference, and the new bug does speak to the overall intent better
[18:42] <matsubara> because that's the first step. adding support to oops-tools to read the lp-production-config file and have a web ui to trigger that
[18:42] <matsubara> now we want to automate it further
[18:42] <matsubara> ok, cool
[18:42] <matsubara> :-)
[18:43] <lifeless> also
[18:43] <lifeless> 659752
[18:44] <lifeless> matsubara: and bug 658863
[18:48] <matsubara> lifeless, ah, thanks for the pointers, I'll cleanup  the mess
[18:48] <lifeless> matsubara: thank you!
[18:51] <lifeless> flacoste: ping
[18:51] <flacoste> hi lifeless
[18:51] <lifeless> flacoste: while you're doing PPR stuff, want to fold edge into lpnet ?
[18:52] <flacoste> lifeless: sure
[18:53] <lifeless> awesome!
[19:04] <lifeless> jelmer: ping
[19:04] <jelmer> lifeless, hi
[19:04] <lifeless> bug 135610 -
[19:05] <lifeless> it was qad very quickly after landing; we're just checking that it really did get vettted for ok-to-deploy
[19:05] <lifeless> jelmer: ^
[19:07] <lifeless> Ursinha: I've filed another couple of qatagger bugs, I put them on lp-foundations from lack of thought - sorry.
[19:07] <lifeless> Ursinha: they are high return ones for folk doing deploys
[19:07] <jelmer> lifeless: I probably tested that one on dogfood while it was ec2ing
[19:07] <lifeless> ok
[19:07] <lifeless> thanks
[19:08] <lifeless> Ursinha: https://bugs.edge.launchpad.net/launchpad-foundations/+bug/667390
[19:08] <lifeless> and https://bugs.edge.launchpad.net/launchpad-foundations/+bug/667389
[19:19] <Ursinha> lifeless, will check now
[19:20] <leonardr> general python question: what will happen if you try to use a unix-specific function like platform.linux_distribution on a non-unix platform? will linux_distribution raise an exception or will it not even be present?
[19:20] <lifeless> leonardr: case by case
[19:21] <leonardr> does anyone have a windows machine they can try this code on for me?
[19:25] <lifeless> sorry, no.
[19:25] <lifeless> but you can use wine
[19:25] <lifeless> matsubara: whats up with https://code.edge.launchpad.net/~ursinha/oops-tools/add-qastaging/+merge/39465 ?
[19:27] <matsubara> lifeless, tests failed, looks like postgres is not running in the oops-tools chroot
[19:27] <matsubara> losas: ping
[19:28] <lifeless> matsubara: -> #launchpad-ops as per flacostes email.
[19:28] <matsubara> oops
[19:28] <matsubara> sorry
[19:28] <lifeless> de nada
[19:44] <lifeless> jml: are you free @ 3 or 4 ?
[19:44] <lifeless> jml: and @ 9 tomorrow?
[19:44] <LPCIBot> Yippie, build fixed!
[19:44] <LPCIBot> Project db-devel build (104): FIXED in 4 hr 4 min: https://hudson.wedontsleep.org/job/db-devel/104/
[19:53] <james_w> lifeless, jml says 4
[19:56] <lifeless> james_w: thanks
[20:00] <jcsackett> someday i'm going to count how many times in a month "make" is the solution to a launchpadder's problem.
[20:02] <flacoste> jml: are we having a meeting?
[20:03] <lifeless> flacoste: 4pm
[20:03] <lifeless> flacoste: and 9 tomorrow, I hope
[20:03] <flacoste> lifeless: nope, another one
[20:41] <LPCIBot> Project devel build (160): SUCCESS in 4 hr 0 min: https://hudson.wedontsleep.org/job/devel/160/
[21:11] <deryck> rockstar, I've disabled the windmill tests I believe to be failing and sent off to ec2 again.
[21:11] <deryck> rockstar, just ec2 test to see if it works, and then you can land if so.
[21:11] <rockstar> deryck, wtf are you?
[21:12] <deryck> rockstar, in the A hallway.  Chair at the front.  Needed power and found it here :-)
[21:12] <rockstar> deryck, I gots the power here.  Just required some looking.
[21:12] <deryck> rockstar, where you at?
[21:12] <rockstar> deryck, in the arterial hallway, where all the other launchpadders were.
[21:13] <deryck> ah
[21:13] <rockstar> lifeless and I found something nasty in feature flags and I are crying.
[21:13] <deryck> rockstar, I should come there then and look into gmb's issues too
[21:13] <rockstar> deryck, yeah, "with our powers combined" and all that.
[21:13] <deryck> indeed
[21:14] <deryck> headed that way now
[21:15]  * rockstar WINS!
[21:15] <rockstar> lifeless, are you around?
[21:17] <rockstar> gary_poster or benji or other zope-y person: I has a questions.
[21:17] <gary_poster> rockstar: i has ability to pretend not here, but will not use this ability
[21:18] <rockstar> gary_poster, so, we have a new item on request.features, right?  And we use this in the base-template to assign it to features in tal.
[21:18] <gary_poster> k
[21:19] <rockstar> gary_poster, but this doesn't work if you use page fragments, since they are separate requests.
[21:20] <gary_poster> you mean separate views, I think?
[21:20] <gary_poster> should be same request
[21:20] <rockstar> gary_poster, it doesn't look to be.
[21:20] <gary_poster> ew
[21:20]  * rockstar digs for an example
[21:21] <rockstar> gary_poster, lib/lp/code/template/branch-index.pt:110
[21:22] <rockstar> gary_poster, I've exposed a page fragment, so that we have a different template file, because otherwise the branch page can get rather large.
[21:23] <gary_poster> For line 110 on that pt I get
[21:23] <gary_poster>       <tal:branch-pending-merges
[21:23] <gary_poster>            replace="structure context/@@++branch-pending-merges" />
[21:23] <rockstar> gary_poster, yeah, that one.
[21:23] <gary_poster> so, that's calling a separate view
[21:23] <gary_poster> but it's the same request
[21:23] <gary_poster> maybe this is a terminology thing
[21:23] <rockstar> gary_poster, maybe.
[21:24] <rockstar> gary_poster, the problem is that branch-pending-merges has none of the defined scope of the "parent" template.
[21:24] <gary_poster> yes
[21:24] <gary_poster> that I'd expect
[21:24] <gary_poster> course, it should be able to get to it with request/features
[21:24] <gary_poster> so shouldn't be hard to find
[21:25] <rockstar> gary_poster, but the request object also seems to be different, since I can't do tal:define="features request/features" like base-layout.pt does.
[21:25] <gary_poster> then that would support your statement that they are different request objects.  That's not...how I'd expect things to be done, though
[21:25] <gary_poster> so IOW this is not zope-y
[21:26] <gary_poster> but it may be launchpad-y
[21:26] <gary_poster> I hope not :-/
[21:26] <wgrant> gary_poster: With bug #662912, is it just that the librarian forwarder thing isn't handling restricted files?
[21:26] <wgrant> I can reproduce the same behaviour with private bug attachments.
[21:26] <gary_poster> wgrant: yes, that's what I just figured out
[21:27] <gary_poster> wgrant: do you happen to know if we only recently stopped copying files over?
[21:27] <gary_poster> in favor of the forwarder thing?
[21:27]  * gary_poster was wondering if this has always been a problem and he just didn't notice before, or what
[21:27] <wgrant> gary_poster: The forward is almost as old as staging, TTBMK.
[21:28] <gary_poster> ah ok
[21:28] <gary_poster> so MP and so on have been broken on staging forever?
[21:28] <wgrant> But that's from before my time.
[21:28] <gary_poster> probably before mine then too :-P
[21:28] <rockstar> gary_poster, so, might you have any suggestions for me?
[21:29] <wgrant> I don't know. I don't recall using MPs on staging, but it seems unlikely that they've been broken forever.
[21:29] <gary_poster> that's what I thought too wgrant.
[21:31] <gary_poster> rockstar: option 1) you give me super-easy steps to dupe and I'll try to pdb.  option 2) you do a pdb yourself.  option 3) we see if request/features is implemented in an odd way or something.  I'll look in on option 3 for a second...
[21:31] <rockstar> gary_poster, lifeless and I just had a pretty epic pdb session, so I bet I have some answers for you already.
[21:31] <gary_poster> ok
[21:33] <rockstar> gary_poster, see http://pastebin.ubuntu.com/520979/ - It was in this debugging that I recognized that we're getting separate requests.
[21:33] <rockstar> gary_poster, hit the branch page with that patch, and you'll see a few different requests being made.
[21:34] <gary_poster> ok, will try, rockstar
[21:35] <wgrant> gary_poster: Note that the restricted librarian is brand new compared to staging. So it's quite possible it was missed, as for years it was only used by the publisher, and that doesn't run on staging.
[21:36] <gary_poster> ah, wgrant, maybe so
[21:39] <gary_poster> rockstar: not having any luck with something accessing features.  Going to https://code.launchpad.dev/~name12 and https://code.launchpad.dev/~name12/landscape/feature-x for instance.  what do you mean by branch page?  or perhaps is there something I need to add to a template?
[21:40] <rockstar> gary_poster, the latter url is what I mean by "branch page"
[21:40] <rockstar> gary_poster, it seems to be starting a separate request (or at least providing a different request object) to ++branch-pending-merges
[21:41] <gary_poster> rockstar: the pdb you gave me is not being hit, presumably because the associated templates do not yet refer to request/features?
[21:42] <gary_poster> I can dig out the various templates involved, but I was hoping you'd guide me into the necessary changes to dupe
[21:42] <gary_poster> as I suspect that will be faster and more efficient, and will enable me to be lazier
[21:43] <rockstar> gary_poster, sorry, that pdb isn't going to help.  A type for if "features" in self.__dict__ was stopping at every get_features, and while dealing with every stop, we saw more requests popping through.
[21:44] <rockstar> gary_poster, really I can't tell you exactly how we re-produced, other than to say "a new request is created after pdb gets to a certain point in rendering"
[21:44] <gary_poster> ...
[21:45] <rockstar> gary_poster, I guess I should say "this is the only explanation to deal with the various issues we're seeing, and so I'd like to investigate further."
[21:49] <deryck> rockstar, https://code.edge.launchpad.net/~deryck/launchpad/populate-trac-bug-filing-form-667342/+merge/39479
[21:49] <gary_poster> rockstar: ok.  My core response is "Zope is typically not supposed to have multiple request objects for the same web request.  You generally only do that when you are changing security interactions on the fly, which is an advanced use case, and likely to need special care.  I am not aware of LP needing to change security interactions on the fly, but it is conceivable."
[21:50] <gary_poster> but pretty darn unlikely, especially with one view calling another from the page template
[21:51] <gary_poster> rockstar: I'm happy to debug something if you can give me instructions to dupe, but I'm not keen on trying to come up with abstract ways to provoke what you describe
[21:51] <rockstar> gary_poster, okay, so why would request be different between +index and ++branch-pending-merges
[21:52] <gary_poster> they are just strings to me.
[21:52] <rockstar> gary_poster, so the best way to dupe the error I'm seeing is to add a tal:condition="features/foo" to any div in lib/lp/code/templates/branch-pending-merges.pt, and see the oops.
[21:53] <gary_poster> ok cool, I'll try
[21:53] <rockstar> gary_poster, and then try to define features as being request/features - this time it'll oops with KeyError on features.
[21:55] <rockstar> gary_poster, I assume it works with any page fragment.
[21:59] <jcsackett> does anyone know some workarounds for ec2 test complaining about ssh agent? usually logout/login works for me (or failing that reboot) but nothing seems to do it now.
[22:00] <jcsackett> error is: https://pastebin.canonical.com/39136/
[22:01] <jcsackett> it's not an uncommon one, but as i said it's not usually this persistent. :-/
[22:01] <gary_poster> rockstar: I have http://pastebin.ubuntu.com/521004/ .  When I go to https://code.launchpad.dev/~name12/landscape/feature-x I see HEEY GARYYY or whatever I wrote on the main template and no OOPS and no pdb
[22:02] <thumper> rockstar: ping
[22:02] <rockstar> gary_poster, I seem to have gotten SOMETHING sorted, making me look like a crazy person.  Sorry for the noise.  I'll consult with lifeless before stirring up more trouble concerning my suspicions.
[22:03] <rockstar> thumper, pong
[22:03] <gary_poster> cool rockstar
[22:03] <thumper> rockstar: you have three cards for merge queues needing qa
[22:03] <thumper> rockstar: I wasn't sure what was needed
[22:04] <rockstar> thumper, yeah, duplication of effort.  Nothing is needed, or I would have addressed it in the bug tracker.  :/
[22:05] <thumper> rockstar: want to move the cards then?
[22:07] <wallyworld> thumper: abentle: standup?
[22:07] <rockstar> thumper, moved them.
[22:07] <thumper> rockstar: ta
[22:07] <thumper> wallyworld: sure
[22:10] <thumper> abentley: ping
[22:10] <abentley> thumper: pong
[22:10] <thumper> abentley: skype?
[22:18] <thumper> wallyworld: https://bugs.qastaging.launchpad.net/launchpad-code/+bug/634149
[22:21] <lifeless> rockstar: yes, can be now
[22:21] <rockstar> lifeless, I sorted it a bit, but I bet you'd like to investigate it a little more.
[22:34] <thumper> https://code.edge.launchpad.net/~weechat-devs/+recipe/weechat-daily WTH?
[22:34] <thumper> Unauthorized: (<lp.code.model.sourcepackagerecipebuild.SourcePackageRecipeBuild object at 0x2b9aa96eb490>, 'status', 'launchpad.View')
[22:35] <lifeless> hmm
[22:35] <lifeless> no idea ;)
[22:35] <lifeless> its still deployed via the edge config
[22:35] <thumper> I can seem my wikkid one
[22:35] <thumper> https://code.edge.launchpad.net/~thumper/+recipe/wikkid-daily works
[22:36] <lifeless> that woorks for me too
[22:46] <lifeless> jcsackett: https://devpad.canonical.com/~lpqateam/qa_reports/deployment-stable.html
[22:49] <jcsackett> lifeless: we switched it to inprogress.
[22:50] <jcsackett> i can mark it as qa-ok to unblock deployment; it just needs further work.
[22:50] <lifeless> I have done so
[22:50] <jcsackett> one sec.
[22:50] <jcsackett> lifeless: okay.
[22:50] <lifeless> qa-ok means 'ok to deploy' really ;) - but we need to tune our tools more still.
[22:50] <lifeless> jcsackett: (I grabbed curtis :))
[22:50] <jcsackett> oh, right; you two are in proximity. :-P
[22:51] <jcsackett> lifeless: how often does the deployment-stable report refresh?
[22:51] <lifeless> 10 minutes or so
[22:52] <lifeless> Once we catch up I'll ask urshina to meaure the duration and run high-frequency
[22:54] <lifeless> jcsackett: its refreshed
[22:55] <lifeless> leonardr: https://devpad.canonical.com/~lpqateam/qa_reports/deployment-stable.html
[22:55] <lifeless> leonardr: please be QAing
[22:57] <lifeless> gary_poster: in case leonardr has EOD'd, perhaps you could peek at this - its a lower commit # than the thing you're qaing.
[22:57] <gary_poster> lifeless: I have to run now I'm afraid
[22:57] <leonardr> lifeless, i'll start the qa process but it'll take about 2 hours for the request token to expire (since i'm testing that they now expire)
[22:57] <lifeless> gary_poster: kk
[22:57] <leonardr> if you want i can make sure that normal approval process works first
[22:58] <lifeless> leonardr: please do - and remember for all your landings that we need to qa as soon as possible
[22:58] <leonardr> ok, what am i testing against, dogfood?
[22:58] <lifeless> leonardr: qastaging.l.n refreshes ~30 minutes after things get through buildbot to stable.
[22:58] <lifeless> leonardr: qastaging.l.n
[22:58] <leonardr> hm, that's a new one, we should add it to launchpadlib.uris
[22:59] <leonardr> lifeless: please humor me and send me url to doc telling me what tag names to use, etc?
[23:00] <leonardr> i've verified that normal token validation still works, so that should be enough to unblock it?
[23:01] <lifeless> leonardr: qa-ok or qa-untestable if is ok to deploy
[23:01] <lifeless> leonardr: bad-commit-XXXX where XXXX is the revno in stable if it is not ok to deploy
[23:01] <lifeless> leonardr: reference material:
[23:01] <lifeless> https://dev.launchpad.net/MergeWorkflow
[23:01] <leonardr> lifeless: tagging it qa-ok. i'll come back in 2 hours and see if the tokens now expire
[23:01] <leonardr> thanks
[23:01] <lifeless> and
[23:01] <lifeless> https://dev.launchpad.net/QAProcessContinuousRollouts
[23:01] <lifeless> leonardr: ok, so its ok to deploy ?
[23:02] <leonardr> lifeless: yes, it doesn't break the existing workflow
[23:02] <lifeless> leonardr: even if it doesn't fix the bug
[23:02] <leonardr> yeah
[23:02] <lifeless> great, exactly what we want.
[23:02] <leonardr> lifeless: one question, will my database entry still be *there* in two hours, or will qastaging have been wiped?
[23:02] <lifeless> qastaging is wiped once a week
[23:02] <bigjools> jml: so, the deal is that the new b-m just eats CPU.  I restarted it and it's no different.
[23:02] <leonardr> ok, i'll come back in 2
[23:03] <bigjools> I shall debug
[23:03] <leonardr> bookmarking those pages now
[23:04] <lifeless> leonardr: cool!
[23:08] <lifeless> Ursinha-bbl: deployment report has crashed
[23:11] <lifeless> Ursinha-bbl: its the unassigned bug thing, that we *fixed*
[23:29] <thumper> lifeless: where is qastaging documented?
[23:29] <thumper> lifeless: does it have an imap folder for outgoing email?
[23:29] <thumper> lifeless: if so, where is it?
[23:30] <thumper> lifeless: by the background I'm guessing it is a copy of the database, is this right?