/srv/irclogs.ubuntu.com/2010/07/28/#launchpad-dev.txt

wgrantmars: Could you land that branch for me, please?00:03
lifelesswgrant: have you fixed the typo00:05
wgrantlifeless: See my reply...00:06
wgrantIt was already fixed.00:06
lifelesshah00:06
wgrantIt was in a removed line.00:06
lifelessok00:06
lifelesssee, jetlag :P00:07
wgrantHeh.00:07
* wgrant -> uni00:07
lifelessits on its way00:07
marsthanks lifeless00:07
mtaylorlifeless: is there a way to track how many times a branch has been pulled00:16
lifelessdo you perhaps mean00:21
lifeless'is there a way for a branch owner to know its popularity' ?00:21
lifelesscause thats a very different question00:21
mtayloruh - I dunno... I was just asked "hey is there a way to track how many time a branch has been downloaded/pulled?"00:24
thumpermtaylor: nope00:24
mtaylorthumper: k. cool00:25
thumpermtaylor: subscriptions may indicate others interest though00:25
thumpermtaylor: if I'm really interested in a branch, I'll subscribe00:25
thumpermtaylor: but I often grab branches I've just a passing interest in00:26
thumpermtaylor: that isn't so useful to the branch owner00:26
thumpermtaylor: have you talked to sinzui about your CoC generalisation?00:27
mtaylorthumper: we spoke briefly a few months aog00:27
mtaylorago00:27
lifelessmtaylor: so tracking pull is hard for a number of reasons00:32
lifelessmtaylor: only one of which 'its distributed, fool'00:32
lifelessmtaylor: other reasons are - http gets != pulls, requests to a stacked-on don't indicate pulls but use the same network verbs, and so forth00:33
mtaylorlifeless: hrm. fair enough00:34
lifelessmtaylor: not impossible, just not done00:37
lifelesswell, I mean - its not impossible to gather the specific data we /have/. Tracking consumers of a branch is impossible in the broader sense ;)00:37
mtaylorwell yes00:38
thumpermwhudson: got a minute for a call?00:57
mwhudsonthumper: not really :(00:59
mwhudsonthumper: will do in a bit00:59
thumperafter lunch maybe?00:59
mwhudsonthumper: ok01:00
lifelessthumper: can I help ?01:00
thumperlifeless: no01:01
lifelessok :)01:01
thumperlifeless: your biggest problem being that your aren't mwhudson :)01:03
lifelessthumper: heh - I wasn't offended or anything :).01:03
thumperlifeless: testr load finished with-> id: 1 tests: 8993 failures: 22 skips: 2301:04
thumperlifeless: but testr failing shows one failure01:04
lifelessthumper: btw, if you want a weekly call with me or something-like-that, let me know. I'm inclined to just focus on good team wide dialogs fo rnow.01:04
lifelessthumper: there is an unimplemented(shock, horror!) bit of testr that should detect deleted / renamed tests.01:04
lifelessthumper: your test run 0 had the failure in it, and the failure is one for a test id not reported in your test run 1.01:05
lifelessthumper: for now, rm .testrepository/failing01:05
thumperand reload?01:05
lifelessthumper: yup01:05
lifelessoh, hangon - see, this is me just getting off a plain :)01:06
lifeless22 failures - that really should be reported by 'testr failing' :)01:06
lifelessthis is from a ec2 land response ?01:06
thumperhmm...01:06
thumperyes01:06
thumpersame result01:06
lifelessforward me the stream?01:06
* thumper deletes .testrepository01:06
thumpersame with a clean testr init01:07
thumper:(01:07
lifelessI'd like to look at the stream, if I may01:08
lifelessI'm not alert enough to do a sensible series-of-questions-to-debug01:08
thumperlifeless: email sent01:08
* thumper thinks that perhaps devel is failing again :(01:09
thumperERROR: lp.soyuz.browser.tests.test_archive_webservice (subunit.RemotedTestCase)01:09
lifelessthumper: its the same test every time01:10
thumperlifeless: yeah01:10
thumperI was just looking01:10
lifelessthumper: zcat ~/Desktop/Downloads/merge-directive-handling-no-request-mirror.log.gz | subunit-filter --no-passthrough --no-skip | subunit-ls | uniq01:10
thumperlifeless: added to .bashrc:01:16
thumperfunction lp-failing01:16
thumper{01:16
thumper  zcat $1 | subunit-filter --no-passthrough --no-skip | subunit-ls | uniq01:16
thumper}01:16
lifelessthumper: heh01:18
lifelesswgrant: what is 'lucille'01:19
thumpergah01:20
thumperWTF?01:20
thumper✁☹01:23
thumper✁☹01:23
thumper✁☹01:23
thumper✁☹01:23
thumper✁☹01:23
thumperlifeless: that failing test assumes python 2.601:24
thumperand doesn't import the with statement01:24
thumperwhich is why ec2 fails for it01:24
thumperbut the builder passes01:24
lifelessnoice01:24
lifelessby which I mean 'garh'01:24
thumperlifeless: rs from you to add the import?01:26
thumperlifeless: I'll land the "fix" now01:26
lifelessdoit01:26
lifelessdo we have a 'trivial' tag ?01:27
thumperlifeless: not any more01:27
thumperbut rs (rubberstamp) is often considered good enough01:27
thumperwe do expect to have more than one person look at things01:28
thumpereven if just in concept01:28
* thumper files a bug to make done01:28
lifelesshmmm01:28
lifelesswe should really consider rolling that back01:28
lifelesspeer review is an important thing for helping make things great, but something like this - bah01:29
wgrantlifeless: lucille was archivepublisher.01:32
lifelesshah01:48
lifelesswe still call the db user lucille01:48
wgrantWe do.01:48
wgrantAnd there's still lucilleconfig.01:48
wgrantI may one day unleash my fury on and destroy lucilleconfig.01:49
lifelessbbiab, post-travel fug is winning01:52
* thumper -> lunch01:53
mwhudsonthumper: i guess you don't want to chat then02:02
=== Ursinha-afk is now known as Ursinha
thumpermwhudson: I'm back now02:38
mwhudsonthumper: how long is the call likely to take?02:39
thumpermwhudson: not long02:39
mwhudsonthumper: i'll call your landline?02:40
thumpermwhudson: you have no skype?02:40
mwhudsonthumper: i can see if that's still working02:40
mwhudsoni'm in a cafe02:41
thumperok02:41
mwhudsonso a headset is probably actually a good ida02:41
wgrantlifeless: Ah, thanks, I didn't know you were ec2testing that.04:08
wgrantI wonder why buildd-manager doesn't log an OOPS and suspend builds when the dispatcher crashes.04:13
lifelessit just needs the same love I gave librarian, I suspect04:14
wgrantAlso, universities need to die.04:15
wgrantSeriously.04:15
spmfrom the perspective of having been nearly 20 years since I got my degree, I'm inclined to agree. Although... The Qld Uni Great Court in Summer time... ahhh. memories.04:16
thumperlifeless: still with us?04:55
lifelessish04:55
lifeless'sup ?04:55
thumpertestr run --failing fails to identify that one of the failing ones is fixed04:55
thumpertestr failing still shows it04:56
lifelesscheck that it is run - subunit-ls < .testrepository/$id | grep testname04:56
lifelessits possible the loader is doing something funky04:56
thumper$ testr run --failingrunning: xvfb-run ./bin/test --subunit --load-list /home/tim/src/launchpad/stop-mirroring-hosted/failing.list| testr load04:57
thumper$ testr failing --subunit | subunit-ls  -> now gives a shorter list04:58
lifelesscheck that it is run - subunit-ls < .testrepository/$id | grep testname04:58
thumperbut it is still showing lp.soyuz.browser.tests.test_archive_webservice04:58
thumperlifeless: I don't grok your last comment04:58
lifelesseach test run generates a new file .testrepository/ID04:58
lifelesswhere ID is printed at the end of the run04:59
thumperyes04:59
lifelessthat has in it all the tests that were run04:59
thumperrunning: xvfb-run ./bin/test --subunit --load-list /home/tim/src/launchpad/stop-mirroring-hosted/failing.list| testr load04:59
lifelessthe most likely reason for testr run --failing to not see a failing test as fixed is if the test runner (zope.testing) did not run it.04:59
thumperthat is what it says in response to testr run --failing04:59
lifelessyes04:59
lifelessthen it should say04:59
lifelessid: FOO tests run: ....04:59
thumperid: 3 tests: 18 failures: 6 skips: 105:00
lifelessright05:00
lifelessso05:00
thumperwhich I weirdly read as "18 failures" "6 skips"05:00
lifelesssubunit-ls < .testrepository/3 | grep lp.soyuz.browser.tests.test_archive_webservice05:00
thumpernot there05:01
lifelesssi05:01
lifelessso05:01
lifelessits not being run05:01
thumperwhy is it telling me it is failing then?05:01
lifelessthis suggests its not in your branch05:01
thumpertestr failing ?05:01
lifelesstestr keeps a record of all seen tests ever05:01
thumperbut it is no longer failing05:02
thumper:(05:02
lifelessif you bzr switch or whatever between branches while a test is failing, and the test is not in the new branch05:02
lifelessthen testr will still think its failing05:02
lifelessthumper: its *not being run*05:02
lifelessthumper: that means whether its failing or not is *unknown*05:02
lifelessthumper: my suggestion, when you bzr switch, nuke .testrepository05:03
thumperI don't switch05:03
lifelessthumper: try bin/test -t lp.soyuz.browser.tests.test_archive_webservice05:03
thumperthat passes05:03
lifelessbut does it run the test05:04
lifelesssee05:04
lifelessthat string looks like a module name to me05:04
lifelessand thats how zope reports a failed import05:04
thumperwhat happened was:05:04
thumperI loaded the repository with the output from ec205:04
thumpermy branch didn't have an up to date devel05:04
thumperso it didn't have the failing soyuz test05:04
thumperuntil I merged devel05:05
lifelessso as far as testr is concerned, a test has been deleted, which as I explained earlier, testr doesn't *yet* have a heuristic to guess at.05:05
thumperand committed05:05
thumpernow it is stuct05:05
thumperbut it is there now...05:05
lifelessright05:05
lifelessso ignore that one test until you've fixed all the issues05:05
lifelessthen delete .testrepository/failing05:05
* thumper looks skyward05:05
lifelesspatches accepted; its a very raw tool. I, and others, find it very useful, but its still rraw.05:06
lifelessthumper: do you see what is going on ?05:09
thumperI think so05:09
mtaylor/msg lifeless oh, and hi, btw05:21
mtaylorheh. guess people know my secrect message to lifeless now05:22
* wgrant puts it in the blackmail file.05:22
mwhudsonscandal05:27
pooliehi mtaylor, mwhudson05:46
mtaylorhi poolie05:47
poolielifeless, i worked on the flags thing on the plane, so now it only looks up scopes as needed05:47
mwhudsonhi poolie05:47
=== almaisan-away is now known as al-maisan
=== zyga-afk is now known as zyga
adeuringoodmorning08:33
wgrantbigjools: Morning.09:06
bigjoolsmorning09:06
wgrantAre you aware of the chaos this morning?09:06
* bigjools sighs heavily09:06
bigjoolsno09:06
wgrantBug #610687 caused the build farm to grind to a halt for many hours. We've disabled the archive in question (I think you might have an email about that), but it needs manual cleanup before it can be reenabled.09:07
_mup_Bug #610687: Delayed copies do not respect PPA component override <canonical-losa-lp> <Soyuz:New> <https://launchpad.net/bugs/610687>09:07
wgrantBasically, we had a build attempting to dispatch with a component of 'non-free'. This made things rather unhappy indeed.09:08
* bigjools sees the email09:08
spm3 emails to be precise, but yes.09:08
* bigjools sees why it happened and is very angry09:08
spmwgrant: pls to be ware. bigjools has a '.procmailrc' - From: spm@c.c >> /dev/null, so emails can be a tad hit'n'miss09:08
bigjoolsspm who?09:09
spmhahaha09:10
wgrant(somewhat amusingly, I was on Monday looking at the code throughout Soyuz that creates publications, and noting how badly factored it was. one of my planned cleanups would have accidentally fixed this...)09:12
bigjoolswgrant: don't let me stop you :)09:13
wgrantI need to fix it for ddeb copies, so it will be happening soon, yes.09:14
wgrantbigjools: Is cleanup just a matter of DELETEing the publications and builds, or did some stuff actually make it to disk?09:39
bigjoolswgrant: I've not analysed it yet, I've got a load of stuff to get done this morning before I can look.09:49
bigjoolsit can wait if it's not breaking anything *right now* :)09:49
wgrantWell, as long as Brian doesn't reenable it.09:51
bigjoolshe's been warned no to09:55
bigjoolsnot09:55
wgrantAh, good.09:55
* wgrant is tempted to take over the world, just to impose a global ban on shitty CS courses.10:44
jelmerheh10:51
jelmerwgrant: What are they having you do?10:51
wgrantjelmer: Well, it's so far been an excellent waste of 2.5 years, though I held some hope that the final semester project (4-5 people per team, 12 weeks in length) might hold some interesting or at least vaguely challenging material. Today, project assignments came out: most of the other teams' projects have some interesting visualisation, data processing or HID components. We were landed with a basic Web 2.0 app, remarkable only in the fact ...10:59
wgrant... that someone could think it was even close to comparable with any of the others.10:59
wgrantSo there goes any hope of some value in this course.10:59
wgrantYay.10:59
jelmer:-/10:59
jelmerThat sounds quite familiar. We had a 8 to 10 person final semester project (though I did it before my final semester) and quite a few teams ended up doing simple web services too.11:03
jelmerThe participation in a relatively large team was still quite educational though.11:03
wgrantThere was a 10-12 person project at the end of the course, but that has been cut in the new version.11:04
maxbI think I learnt about 1 weeks worth of useful stuff from my uni course. And an immense amount from open source hacking whilst at uni :-)11:05
wgrantHeh, yes.11:05
jelmerheh, indeed11:06
mwhudsoni learnt stuff during my degree11:07
mwhudsonmy phd on the other hand...11:07
mwhudson(my degree wasn't in cos, that probably helped)11:07
mwhudson*cs11:07
wgrantThe most useful thing I've learnt from the degree is to not do or trust degrees.11:07
* jelmer thought some of the more theoretical CS courses were very useful11:07
wgrantTrue, the few theoretical ones have been somewhat educational.11:08
StevenKwgrant: I learnt some useful things at uni. Most of which wasn't taught ...11:16
wgrantStevenK: Heh.11:25
jelmerEdwinGrubbs: Hi11:27
=== al-maisan is now known as almaisan-away
henningeHi!12:42
henningeDid I miss the discussion on moving the registration slot between the title and the bread crumbs or was there no discussion?12:43
maxbIt's a little jarring13:02
wgrantI like it for branches and some other stuff.13:06
wgrantBut for projects it doesn't really work, because it's not important information.13:06
wgrantThe old location wasn't good, though.13:06
EdwinGrubbsjelmer: hi13:27
=== gary_poster_ is now known as gary_poster
=== almaisan-away is now known as al-maisan
lifelessmorning all ye non-jetlaggers15:35
=== matsubara is now known as matsubara-lunch
bigjoolshello lifeless15:58
lifelesshi bigjools15:59
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
jmllifeless, hi16:25
lifelesshi16:25
lifelesshenninge: ping16:28
lifelesshenninge: your buildd manager logging patch : upstream twisted's log class supports what you want directly; I'm confused why you seem to have reimplemented it : or am I missing something ?16:29
marsjml or lifeless, around?  Would either of you feel comfortable doing a Unix build system pre-implementation call?  I am trying to figure out how much effort we should put into cleaning up the process tree16:39
jmlmars, otp right now16:40
marsk16:40
jmlmars, happy to in a little while16:40
lifelessmars: sure16:40
henningelifeless: Hi16:44
lifelesshi henninge; I'm really excited to see the twisted log rotation stuff getting fixed for us - we've a lot of daemons (buildd,librarian, codehosting) that all need it16:45
lifelesshenninge: I'm just hoping we don't need to maintain code [and thus tests] for it16:45
henningelifeless: I don't see how this could be done any other way in twisted16:45
henningelifeless: It does not re-open logs on SIGUSR1 but rotates them (in its own way).16:46
lifelesshenninge: just use a LogFile(foo, bar, rotateLength=0)16:47
lifeless?16:47
henningelifeless: that's what I do, don't I?16:47
lifelesshmm, let me re-read16:47
lifelesshenninge: ok16:50
lifelessotp for a sec16:51
=== beuno is now known as beuno-lunch
=== zyga is now known as zyga-afk
rockstarbigjools, dogfood fall down go boom.17:15
bigjoolsrockstar: will look later, OTP17:16
=== EdwinGrubbs is now known as Edwin-lunch
henningelifeless: I'll be finishing off now. I replied on the MP. ;)17:40
lifelessyeah thanks17:40
=== Ursinha_ is now known as Guest58336
=== Guest58336 is now known as Ursula
=== Ursula is now known as Guest16602
=== Guest16602 is now known as Ursula_
lifelessok, I think I'm going to pull on this librarian thing a bit, it should make a big difference17:56
=== beuno-lunch is now known as beuno
=== al-maisan is now known as almaisan-away
mtaylorbac: ah... so perhaps it's because of the commercial subscription ?19:06
bacmtaylor: that's what i'm investigating19:06
bacif so, it should be easy to fix.  this problem has been infested with red herrings19:06
mtaylorhehe19:06
mtaylorfish are difficult to catch19:06
bacslippery19:07
mtayloryup19:07
baci'll let you know what i find19:07
jmlthumper, are you guys planning on doing anything with https://code.edge.launchpad.net/~jml/launchpad/private-branch-lookup-bug-26160919:12
thumperyes19:12
jmlthumper, it's been stale for a while now, and I'm really keen to get it off my branch list.19:13
thumperjml: I was finishing off another tech-debt branch, this is next19:13
jmlthumper, cool, thanks.19:13
=== Edwin-lunch is now known as EdwinGrubbs
james_wthe code users of the job system raise SQLObjectNotFound in a couple of places, is there something that should be used instead, or is this still the idiom?19:29
james_wit's raised in a get @classmethod on a Storm object19:30
james_wabentley: any idea? ^19:33
abentleyjames_w, I'm not aware of something that should be used instead.19:48
james_wabentley: is get() raising an exception a required thing? It seems to me that the only callers convert the exception to None, so the work of converting None to the exception is not needed.19:49
abentleyjames_w, I don't know if it's a required thing, but I would expect that retrieving an object that doesn't exist is usually a serious error.19:51
lifelessjml: am I on th eplanet ?19:52
lifelessjml: I don't think I am... can I be added ?19:52
james_wlifeless: is it a requirement to get a review from both you and stub for db patches?19:54
lifelessyes to deploy, no to merge19:55
james_wok, good19:55
jmllifeless, sure. email mrevell.19:57
lifelessjml: you know, if lp knew about blogs, the planet could be auto maintained ;P19:58
jmllifeless, patches tolerated.19:59
lifelesshaha19:59
lifelessI only get to code if I'm a *good boy*19:59
lifelessmatsubara: hi20:03
matsubaralifeless, hey20:04
lifelessI put a patch up for getting bug numbers in the timeout section20:04
lifelessbut I can't bootstrap properly to test it20:05
lifelessdid you have any thoughts on it20:05
matsubaralifeless, I didn't get an email notification about  the merge proposal20:06
lifelessmatsubara: I put it in the bug20:06
matsubaralifeless, looking20:09
Ursinhalifeless, bug 607776 is testable or not?20:11
_mup_Bug #607776: +filebug-show-similar FTI query timeouts <qa-needstesting> <timeout> <Launchpad Bugs:In Progress by lifeless> <https://launchpad.net/bugs/607776>20:11
benjilifeless: if you have a working buildout you can use it to bootstrap a new buildout cd path-to-new-project; path-to-working-project/bin/buildout bootstrap20:11
lifelessUrsinha: no20:12
benjiunfortunately, having a bootstrap.py script in a buildout is an attractive nuisance20:12
lifelessUrsinha: I have a follow on branch that drops the time by ~ 75%20:12
Ursinhalifeless, cool20:13
Ursinhathat's cool20:13
lifelessbenji: it seems the oops tools want stuff that isn't in the dep cache20:13
Ursinhalifeless, will remove the qa-needstesting tag for now20:13
lifelessUrsinha: thanks, wasn't sure if I should / shouldn't20:13
benjican't help you there :)20:13
lifelessbenji: :/20:13
matsubaralifeless, what's the error?20:13
Ursinhalifeless, that's the incremental change, if it's not testable, doesn't make sense to keep the tag there20:13
lifelessUrsinha: kk20:14
lifelessmatsubara: bootstrapping?20:14
benjimaybe you need to bzr up the dependencies (~/launchpad/lp-branches/devel/download-cache20:14
benji)20:14
matsubaralifeless, I'm not sure the patch is going to do what you want. My initial impression to the bug report is that the static summary (https://devpad.canonical.com/~lpqateam/oops-20:14
matsubarasummaries/lpnet-2010-07-20.html#time-outs) was generated before the bug was linked to the oops20:14
matsubaralifeless, yes, what dependency oops-tools is asking that's not in the cache?20:15
lifeless  Getting distribution for 'zc.buildout==1.4.1'.20:15
lifelessError: Couldn't find a distribution for 'zc.buildout==1.4.1'.20:15
lifelessmatsubara: when I traced the code, it seemed like it was simply that the bug wasn't being set for the reporter20:16
abentleyjames_w, I'm looking at the build emails, and the ordering of items looks like it could be improved.  I'd put the buildstate high.20:16
lifelessmatsubara: you could try it and see ;P20:16
matsubaralifeless, you want this cache: bzr+ssh://bazaar.launchpad.net/~launchpad/lazr-source-dependencies/download-cache/ not the LP one20:17
benjiindeed, zc.buildout 1.4.1 doesn't appear to be in the centrally-managed cache; I suspect 1.4.0 would work for you20:17
lifelessmatsubara: thanks20:18
james_wabentley: yeah, that would be a good idea20:18
lifelesspulling it20:18
lifelessmatsubara: was that in README.txt and I was simply blind ?20:18
abentleyjames_w, in your bug, you seem inconsistent about whether the component should be included.20:19
matsubaralifeless, yep, it's explained there and the make command should fetch the right cache. not sure why it didn't work for you20:20
james_wabentley: bug number?20:20
abentleyjames_w, 60360620:20
abentleyjames_w, or what is RELEASE?  the pocket?20:20
james_wabentley: pocket, yes20:21
abentleyjames_w, and that's not listed in binary build email body, just subject.  I see.20:21
james_wabentley: the pocket will be important once it is possible to target non-release pockets, but for now there is only one choice, so I say put it in there20:21
lifelessmatsubara: my bad!20:22
james_wabentley: I'm not particularly keen on the binary build email, but it's better than what was there for recipes IMO, and I think they should at least be largely consistent. If you want to improve both, that would be even better20:22
abentleyjames_w, what about distroseries?20:22
james_wabentley: that's a requirement IMO, it's especially important with multi-series builds.20:23
abentleyjames_w, err, we don't have multi-series builds.20:23
james_wwell, one recipe being dispatched to multiple series at the same time20:24
james_wif I wake up to a daily build failure, I want to be able to work out which series failed, without having to query them each in turn20:24
abentleyjames_w, well, you can click though and get all the information, and more.20:25
abentleyjames_w, but you didn't ask for distroseries.20:25
abentleyjames_w, do you prefer pocket and distroseries separate, or do you want "suite"?20:25
james_wabentley: the series is in the subject as well20:26
james_wabentley: I don't mind20:26
james_wI would prefer it was the same as binary builds20:26
abentleyjames_w, binary builds don't list the pocket or distroseries in the message body at all.20:27
james_windeed20:27
abentleyjames_w, so you're saying it shouldn't be included?20:27
james_wabentley: I want it there somewhere. I don't have particularly strong preferences on where.20:28
james_wabentley: are you redesigning binary build failure messages too?20:28
lifelessmatsubara: now it wants distribute 0.6.1220:29
abentleyjames_w, no, not my domain.20:29
lifelessmatsubara: with that new cache20:29
james_wabentley: in that case, I would prefer that the recipe build failures just follow the binary build failures.20:30
abentleyjames_w, seems like a lowest-common-denominator approach to me.20:30
james_wabentley: why?20:30
abentleyjames_w, because you don't especially like binary build mails, but you want me to make source build mails just as bad.20:31
james_wabentley: they are better than what we currently have for recipes, and I value consistency. If you see ways to improve the binary build mails then I encourage you to improve those as well.20:33
abentleyjames_w, so you're basically asking me to make recipe build mails no better than binary build mails.20:34
james_wabentley: I'm asking you to make them equally as good, yes. I'd love for you to make them both excellent.20:34
abentleyjames_w, It's not my job to make binary build mails better, but perhaps if I make recipe build mails better, soyuz will see and follow suit.20:35
james_wabentley: I don't see why it isn't your job20:35
abentleyjames_w, I am a member of the code team, not soyuz.20:36
james_wand I don't think that is an approach that has worked particularly well in the past20:36
matsubaralifeless, hmm I think I saw that distribute problem before with gary_poster and was unable to reproduce locally. would you mind filing a bug on oops-tools so I can investigate this further later on?20:36
abentleyjames_w, I'm not going to go trampling though another team's code for no especially good reason.  That will just upset them.20:38
james_wabentley: I think that characterisation isn't helpful. I would imagine the soyuz team would be overjoyed at someone looking at this area of the project and improving it.20:38
james_wI doubt anyone is particularly attached to the status quo20:38
james_wfwiw, upload acceptance emails were redesigned about a year ago, with great success. They are now for more readable and usable than before.20:39
abentleyjames_w, improvement is very much in the eye of the beholder.  I would be very upset if someone made this kind of change to my code without consulting me.20:40
lifelessmatsubara: sure20:40
james_wabentley: then consult them?20:40
bigjoolsabentley: BFNs are crap, fee l free to fix them :)20:41
abentleyjames_w, it's simpler to just ask them to do it instead.  They have the experience with the code and the domain knowledge to do a better job.20:41
marslifeless, ping, any chance you could point to some example code that uses testtools.clone_test_with_new_id() ?20:46
lifelesstestscenarios20:46
lifeless(apt-get install python-testscenarios, or grab it from pypi, or lp:testscenarios)20:46
marsthanks, looking at the code now20:47
lifelessmars: start with the readme20:59
marslifeless, hmm, I'm getting no text21:13
lifelesswhat do you mean ?21:14
marshttp://bazaar.launchpad.net/~lifeless/testscenarios/trunk/annotate/head:/doc/example.py?file_id=lib-20090307095458-ntl18b730pwjf0qy-10 is empty21:14
marsfor instance21:14
marsdoes that mean codebrowse is going to die? :(21:14
lifelessI don't know what it means21:15
lifelesshttp://bazaar.launchpad.net/~lifeless/testscenarios/trunk/revision/1#doc/example.py21:15
lifelessclicking on doc/example.py there worked21:15
marslifeless, neat, that is a useful tool.  Parameterization made easy21:16
lifeless:)21:17
mwhudsonmorninh21:36
mtaylormorning lifeless21:38
lifelesshiya21:48
bdmurrayI just got oops-1670ea4372 when reporting a bug and the traceback did not look to my untrained eye22:00
lifelesslook what?22:01
=== matsubara is now known as matsubara-afk
bdmurraylook good?22:01
lifelesshttps://lp-oops.canonical.com/oops.py/?oopsid=1670EA4372 looks sane (but sad) to me. otp for now, chat in a sec22:12
lifelessbdmurray: ok, off the call23:17
lifelessbdmurray: that timeout looks legit23:18
* wgrant looks at the build queues with dismay.23:18
wgrantbarry!!!!!!!!23:18
wgrantOh, no, it's not all py27stack423:19
wgrantThen what is it...23:19
wgrant.....23:19
wgrantpy27stack5.23:20
jelmer'evening23:20
wgrantCan we at lest score that archive down a few hundred points, or something like that?23:21
mwhudsonjelmer: i wanted to ask you something a minute ago but now can't remember what :-)23:22
pooliehi lifeless, wgrant, mwhudson23:24
pooliethanks for the review lifeless23:24
wgrantMorning poolie.23:24
lifelesspoolie: my pleasure23:28
pooliehow should i write tests for the page macros?23:28
pooliepreferably not as doctests23:28
lifelessyou get a browser instance23:28
lifelessand use some template that uses the macros so you get a rendered view23:29
* wgrant whispers 'really bad user experience', and points at #launchpad and the build queue which is currently being eaten by an unimportant rebuild.23:29
lifelesswgrant: the magic phrase is 'losa ping'23:29
wgrantWell, no, there are underlying issues.23:29
pooliewgrant: i was thinking about proposing an "i care about this" button that can only be pressed by a human (not in the api) that adds X to the build score23:29
pooliethis will of course only work if people don't press it for everything23:30
wgrantThe problem at the moment is that people do partial archive rebuilds without telling anyone, so they are scored like normal PPA builds.23:30
wgrant(well, that shouldn't be a problem, except our queue discipline is pathetic)23:31
lifelessperhaps subtract the queue length for a PPA from uploads to the PPA23:31
bigjoolswho is rebuilding?23:31
wgrantbarry.23:31
wgrantI thought it was py27stack4.23:31
* bigjools scores it down23:31
wgrantBut I was wrong; there's only a few there.23:31
wgrantNow it's py27stack5.23:32
bigjoolsI asked him to use rebuild archives23:32
wgrantIf he doesn't want to do that, he could at least get someone to add a score delta to the archive first.23:32
wgrantScoring them down to <900 might be nice, otherwise recipe builds won't happen.23:33
lifelesswhats a rebuild archive ?23:33
bigjoolsI scored everything -10023:33
wgrantHaha. Even better.23:33
bigjoolsthat'll free the farm up23:33
wgrantThanks.23:33
bigjoolswhen I say -100 I mean a delta23:33
bigjoolsnot absolute :)23:33
wgrantlifeless: ArchivePurpose.COPY. Doesn't accept source uploads, and has a forced build score of -10.23:33
wgrantOh :(23:34
wgrantSo recipe builds are screwed for the next couple of days. I guess that's not tooo bad.23:34
bigjoolshmmm23:34
wgrantAlso, will that affect existing builds?23:34
bigjoolsyes23:34
bigjoolsanything needsbuild23:34
wgrantBut I thought queuebuilder didn't run any more.23:34
bigjoolsoh arse23:35
bigjoolsI need to manually rescore them23:35
bigjoolswell, it's only a 4 hour wait23:36
wgrantAssuming perfect efficiency.23:36
bigjoolsif it were days...23:36
wgrantIt's lots of short builds.23:36
wgrantTrue.23:36
wgrantBut it'll be more like 24 hours.23:37
wgrantOnce you take into account the continuing pileup of builds, and the fact that they're short builds, which buildd-manager really doesn't handle well.23:37
bigjoolsit will, soon23:38
wgrantIndeed.23:38
wgrantThat will be good.23:38
bigjoolsI should fix that score delta stuff so it applies the delta on the query23:39
bigjoolsthen it'll work on existing builds23:40
wgrantThat sounds confusing.23:40
wgrantBut maybe better.23:40
* bigjools shoos a fox away23:41
bigjoolsanyway it's seriously antisocial to upload 500+ packages for rebuild in a normal PPA23:42
bigjoolsg'night23:50
wgrantNight.23:50
poolieare developer docs in the tree ever built into web pages people can read?23:53
poolielike for bzr's?23:53
lifelessthere is apidoc.launchpad.dev now23:53
wgrantHow does one create code imports these days?23:53
wgrantI can't see a way to do it outside +setbranch.23:54
jelmerwgrant, some project code pages don't have a link, but https://code.launchpad.net/ has a link to create imports for all projects23:54
wgrantAh, +new-import23:55
wgrantI was using +newimport :(23:55
thumperthe theory was...23:55
thumperthat we wouldn't show "new import" for a project that uses launchpad codehosting23:55
thumperhowever it seems its all gone to pot23:55
wgrantIt seems to just not show the link if there is a dev focus.23:56
wgrantAFAICT.23:56
jelmerthumper: I can think of some (pehaps not common, but possible) situations where an import would be useful even if the trunk is hosted on Launchpad.23:56
thumperjelmer: like?23:56
jelmerthumper: dulwich is maintained in bzr, but I keep a mirror of it in git and some external contributors host their branches on github23:57
jelmer(I did emphasize it wasn't a common situation :-)23:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!