=== flacoste is now known as flacoste_afk === Ursinha is now known as Ursinha-dinner === flacoste_afk is now known as flacoste [03:14] spm: Users can deactivate their accounts, right..? [03:14] wg-rant: deactivate yes; purge no [03:14] if you appreciate the difference. we get very few requests for the latter, but enough. [03:14] How do you purge? Merge them away? [03:15] sql nullify the relevant bits in the appropriate tables [03:15] Ah. [03:15] not ... pretty, but. [03:15] actually.. I think that's correct. verifying... [03:17] bleh. it's not docco'd. but that'd be the likely way. [03:18] wgrant: heh, ref the 'ssh codebounce' I'd typed that much and was starting to get frustrated at why ssh tab completion wasn't. then the light came on. whee. :-D [03:19] Heh. [03:19] It's not a DNS alias yet? :( [03:23] that would be .. unwise :-) [03:24] i know we have cocobanana as an alias for a rollout target. but generally we do limit our moments of ... public silliness :-) [03:25] Pfft. [05:45] thumper: hi [05:45] thumper: Can we have a 5 minute pre-impl call ? [05:48] lifeless: sure [05:49] when suits? now would be great for me [05:49] lifeless: now is fine [05:51] lifeless: you dropped [05:53] can you hear me ? [05:53] [120531.779865] iwlagn 0000:02:00.0: Microcode SW error detected. Restarting 0x2000000. [05:54] iwlagn isn't the most stable of wireless drivers, I've had problems with it at times that required rmmod & modprobe === almaisan-away is now known as al-maisan [08:22] good morning [08:58] Morning === mrevell_ is now known as mrevell [09:23] wgrant: You around? [09:23] Any idea why this might be happening? https://quickbuild.pearsoncomputing.net/builders/vidar [09:25] * kb9vqf wonders if it's unique to Debian [09:31] kb9vqf: Not sure. Maybe check Ubuntu's console-data diff? [09:31] OK, just wondering if you guys had seen it before ;-) [09:31] Those almost look like drawing commands for the text-based interactive mode [10:05] Hmmm...why does the build farm ignore the remaining idle builders insead of assinging them chunks of the build queue? [10:06] I have two active and two idle with a long build queue... [10:06] https://quickbuild.pearsoncomputing.net/builders/ [10:06] I don't see any errors anywhere [10:07] Check the buildd-manager log for references to those builders. [10:08] Nothing [10:08] wgrant: The only thing in the log are references to the broken builders [10:08] What if you edit lib/lp/buildmaster/manager.py, replace logging.INFO with logging.DEBUG, then restart buildd-manager? [10:12] wgrant: Not much, just a bunch of [10:12] 2010-06-17 04:11:32-0500 [-] Considering odin [10:12] 2010-06-17 04:11:32-0500 [-] No build candidates available for builder. [10:12] Strangely both builders work, just not simultaneously [10:12] Ahh. [10:12] I bet it's the 80% restriction. [10:12] ? [10:13] That is, no PPA is allowed to use more than 80% of the builders for any architecture. [10:13] Makes sense [10:13] Can I override it? [10:14] No, but you can delete it. [10:14] See the end of addCandidateSelectionCriteria in lp.soyuz.model.buildpackagejob [10:14] OK, thanks (Each of my builders is a separate physical machine, so adding more builders isn't a very palatable solution) [10:14] remove the num_arch_builders stuff and everything from there until the return. [10:16] It looks like I could override it (sort of) by just changing the 80 to something else [10:16] That way it's a small change from production Launchpad, not a big one ;-) [10:16] Or just delete the bit that adds the clause. [10:17] I assume a simple restart of the buildd manager will apply the change? [10:18] Correct. [10:19] * kb9vqf needs to get to bed...it's way to early here [10:19] Thanks for your help! [10:19] Night. === al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan [11:10] Morning, all. === mrevell is now known as mrevell-lunch === mrevell-lunch is now known as mrevell === matsubara-afk is now known as matsubara === Ursinha-dinner is now known as Ursinha === zyga is now known as zyga_away [14:26] Chex, i filed an rt earlier this morning to ask for help running a performance test. it should only take a few minutes, so let me know when you can spare the time [14:29] argh, where's my receipt? [15:05] mars: I did not get an email from ec2 this morning. The instance finished, but not success or fail email [15:30] sinzui, did it finish in a reasonable amount of time? Also, was it an 'ec2 land' mail? Those can take forever sometimes. [15:30] How could I know it finished in a reasonable amount of time? [15:30] (just noticed how ridiculous that sounds - if it took forever, how would I know when it finished?) [15:30] I used ec2 test [15:30] ok [15:31] sinzui, ok, so there may still be problems, barring a few-hours delivery delay. I have a follow-up branch that should address that. [15:32] I resubmitted the test. I hope it to be complete in 4 hours [15:33] ok, please let me know what the result is. If it is a success, then we have an intermittent failure. If it eats it again, then I might have something I can reproduce. [16:36] sinzui, hi [16:38] Hi Ursinha [16:38] * sinzui was lost and could not find the window that wanted his attention [16:39] sinzui, :) [16:39] sinzui, about your email: the bugs marked as fix committed without qa tags weren't marked fix committed by my script, but manually [16:39] that's why they don't have the tags [16:40] when the script runs on them, it will mark them properly [16:40] * sinzui nods [16:40] I've stopped the script for now, I'm putting newer code there, but it should happen rsn [16:41] Ursinha, is it a concern that they are not being tracked? [16:41] * sinzui QAs every fix-committed in answers, blueprint and registry regardless of tags [16:41] sinzui, I'll run the script and check if they will be properly tagged [16:42] sinzui, yes, I often monitor those [16:42] the fixed but untagged [16:42] fab [16:42] I will not worry then [16:42] same way I monitor the orphaned ones [16:42] :) === beuno is now known as beuno-lunch === salgado is now known as salgado-lunch === Ursinha is now known as Ursinha-lunch [17:52] mars, ec2 sent me emails this time. Both instances ran about 4 hours === al-maisan is now known as almaisan-away === matsubara is now known as matsubara-lunch [18:10] Night! === beuno-lunch is now known as beuno [18:26] If anyone asks, it appears PPA publishing is broken at the moment. Working on fixing it. === salgado-lunch is now known as salgado === deryck is now known as deryck[lunch] === matsubara-lunch is now known as matsubara [18:47] g'night all. see you next week. [18:48] cody-somerville, btw, if it's down for more than 15 minutes, it's an incident. Please find someone to manage it. [18:48] * jml flees the scene [18:48] jml, trying to. It seems all the Soyuz people have EODed [18:49] flacoste, ^ ? [18:53] It appears to have been broken now for four hours and 5 minutes now. [18:54] * 10 minutes === deryck[lunch] is now known as deryck === Ursinha-lunch is now known as Ursinha === matsubara is now known as matsubara-afk === matsubara-afk is now known as matsubara === Ursinha is now known as Ursinha-afk === almaisan-away is now known as al-maisan === salgado is now known as salgado-afk === matsubara is now known as matsubara-afk [22:26] It looks like the devel build will fail. I have a fix for the two failing tests that I know about [22:26] * sinzui waits for the official failure message === al-maisan is now known as almaisan-away === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [23:33] U1 is very good at 'fixing' major security flaws but somehow managing to leave them wide open. [23:35] wgrant, that's not exactly useful [23:36] beuno: hi [23:36] wgrant, there is a roll-out to production that has been delayed 3 times already [23:36] wgrant, that contain the actual fixes [23:36] heya thumper! [23:36] beuno: Ah. That makes more sense. [23:36] wgrant, hence, the fix-committed and not fix-released [23:36] Just jdo said it was fixed... and it's not. Which reminds of last time someone said it was fixed, where the fourth fix finally worked. [23:36] Mmm, no, the bug in question here is Fix Released. [23:36] wgrant, I would of expected you to know that by now ;) [23:37] oh? [23:37] it's wrong then [23:37] he probably thinks the roll-out happened [23:37] Bug 590540 [23:37] wgrant, right, no deployed [23:37] tomorrow, hopefully [23:37] Ahhh, good. Sorry about that. [23:38] I see where the confusion came up [23:39] if PQM behaves the roll out tomorow will include all fixes [23:39] the branch for #535651 is bouncing with an unrelated error [23:39] the rest are all landed [23:40] beuno: 'if' :) [23:40] heh, yes [23:40] may be all of them minus one [23:40] OK, great. Thanks. [23:40] wgrant, thanks for the reports [23:40] it was a bit of a shock to see those open [23:41] we did some db mangling to make sure they hadn't been exploited [23:41] they haven't [23:41] * thumper afk [23:42] beuno: It returned no results at all? [23:42] Because I did try it. [23:42] wgrant, I didn't see the query, but it may of been "nobody except wgrant" ;) [23:43] wgrant: now try % encoded path seperators [23:46] sinzui: +participation 403s sometimes. [23:47] ouch [23:47] You, for example. [23:47] me [23:48] I will investigaste [23:48] Thanks. [23:52] ha ha, there are 17 deprecated private membership teams, and I appear to be a members of a few. and since the new page shows the path to membership, it breaks [23:53] I will land a fix for this tomorrow. I wish I could remove the teams too [23:59] Why can't you?