/srv/irclogs.ubuntu.com/2012/07/11/#launchpad-dev.txt

huwshimiI have some odd failures that have started appearing in my branches. http://pastebin.ubuntu.com/1085503/01:17
StevenKhuwshimi: Merge devel, wgrant fixed them last night.01:17
huwshimiStevenK: Ah, I tried that yesterday afternoon, I guess I was a little too early01:23
huwshimiAlso, if I have a bzr pipe do I need to do anything special to 'ec2 land' that pipe. I'm sure I used to just make sure I had switched to the pipe and submit, but it doesn't seem to be working anymore01:25
StevenKhuwshimi: ec2 landing one pipe is easier if you run 'ec2 land <MP URL>'01:26
huwshimiStevenK: Ah right, I'll give that a go. Cheers mate.01:27
StevenKwgrant: So, should I look at that bug you assigned me?01:31
StevenKwgrant: teach-rasj-about-branches is landing01:31
StevenKBah, wallyworld_ got r15600.01:32
* StevenK stabs him01:32
wgrantStevenK: Great01:32
wgrantwallyworld_: Huh, what's with the circular import thing you added to lib/lp/bugs/interfaces/bugtask.py?01:32
wgrantwallyworld_: It's at the top level, so it can't be for circular import avoidance.01:32
StevenKA mail from LP making the MP as merged before I get a success mail from PQM? :-(01:35
StevenKwgrant: Oh, hah. You assigned that bug to me and then closed it.01:37
wgrant_StevenK: Which bug? I think the freenode node I was on has died.01:37
StevenKwgrant_: bug 101462501:37
_mup_Bug #1014625: pkgme should have one license <pkgme:Fix Released> < https://launchpad.net/bugs/1014625 >01:37
StevenKBAH01:37
StevenKwgrant_: bug 101462401:37
_mup_Bug #1014624: Sharing details page does not show branches <disclosure> <sharing> <ui> <Launchpad itself:Fix Released by stevenk> < https://launchpad.net/bugs/1014624 >01:37
=== wgrant_ is now known as wgrant
wgrantStevenK: Right, what about it?01:38
wgrantLast I saw was:01:38
wgrant11:32:59 < wgrant> wallyworld_: It's at the top level, so it can't be for circular import avoidance.01:38
StevenK[11:31] < StevenK> wgrant: So, should I look at that bug you assigned me?01:38
StevenKwgrant: There's little point looking at it -- you closed it, I just didn't notice that bit.01:38
wallyworld_wgrant: if i put it at the top of the file the zcml won't load01:38
wgrantOh, I got that but missed it. Oops01:39
wgrantwallyworld_: Lies.01:39
* wgrant tries.01:39
* StevenK waits for "Hmmmm."01:39
wgrantUnless it's an import order issue, which we haven't really seen since c.l.i was destroyed.01:40
wgrantBut if enums is importing other stuff then enums is buggy.01:40
wallyworld_the vocab imports stuff01:40
wgrantwallyworld_: But lp.registry.enums doesn't import anything else in LP, so it can't be circular.01:41
wgrantI just moved it to its rightful location and it works.01:41
* wgrant lands.01:41
sinzui+101:41
wallyworld_not sure what happened for me then01:41
StevenKPyCharm caused it01:42
wgrantPyCharm01:42
StevenKOr something01:42
wgrantBecause it's written in Java01:42
StevenKHahahaha01:42
wgrantAnd Java is Java01:42
wallyworld_huh?01:42
wgrant:)01:42
wallyworld_i ran it from command line01:42
wallyworld_what's pycharm got to do with it?01:42
wgrantDon't you go trying to use logic on us!01:42
wgrantsinzui, wallyworld_: I'm wondering about private team junk branches... we could subscribe the team, or we could create an immutable non-pillar access policy with a single grant for the team and make the branches use that.01:46
wgrantThat would prevent the team from losing control of their branches through unsubscription.01:47
wgrantIn a project the maintainer can always regain control.01:47
sinzuiI favour the latter01:47
wallyworld_don't we want to avoid subscribe and visibility conflayion?01:47
wgrantBut in the private team case they may not be able to.01:47
wgrantwallyworld_: Unfortunately scope was cut, so it will still be slightly conflated.01:47
sinzuiI would like to think sharing will be adapted to teams one day01:47
wallyworld_the latter works for me too01:48
wgrantThe AP model is deliberately flexible to this sort of thing.01:48
wgrantThe core bits don't care about information type at all01:48
wgrantThis also means we have a well-defined owner for all branches in the system.01:48
wgrantFinally.01:48
wgrantNon-owner owner, that is.01:49
StevenKNon-owner owner?01:49
sinzuino maintainer that co-owns the branch01:49
wallyworld_registrant vs owner perhaps?01:49
wgrantWell, project maintainers own project branches01:49
wgrantBranch owners don't own their branches01:49
wgrantThe project maintainer does.01:49
StevenKRight01:49
wgrantIn terms of data ownership01:49
StevenKBranches are hard, let's go shopping.01:50
sinzuiWell the registrant is another cock-up by Lp. Lp is not a home for Mr Cock-up, but we seem to have prepared a bed for him01:50
spmthat's just begging to be quotes paged...01:51
wgrantAgreed01:51
StevenKsinzui: Just a bed? He turns up so often he has a wardrobe and a toothbrush in LP>01:51
StevenKs/>/./01:51
sinzuiStevenK, well noted. we also have given him several email addresses01:53
wallyworld_sinzui: there's a sendTeamEmailAddressValidationEmail() method that's only called if contact email is entered when creating a team. it doesn't seem to be called from the team contact address view. should it be?01:53
StevenKsinzui: Haha01:54
sinzuiwhat?01:54
nigelbspm: Srsly.01:54
nigelbI could scroll though #launchpad-dev.log every day and just find amazing quotes.01:55
sinzuiwallyworld_, all email addresses have to be validated. Maybe Lp is using the user email confirmation process by mistake01:55
* sinzui welcomes the deletion on unused code though01:55
wallyworld_sinzui: the the team contact form, a different method is used, validate_new_team_email()01:56
wallyworld_sinzui: the team creation actually sends an email01:56
wallyworld_whereas the validate_new_team_email() seems to simple parse the email01:57
sinzuiug01:57
sinzuiwallyworld_, I have more faith is the  validate_new_team_email() method. I expect barry's work it be 'canonical' approach. You can remove code I think.01:58
wallyworld_ok, thanks. it seems silly that we do it 2 ways01:59
wallyworld_sinzui: although you could enter an email that parses but is not valid01:59
wallyworld_so the sendTeamEmailAddressValidationEmail(0 does at least check that bit02:00
sinzuiwallyworld_, an email address validation RE is more than 1024 chars long and will topple Lp trying to use in pages02:01
* sinzui remembers that sad incident02:01
sinzuiwallyworld_, So we care about the email being sent to the the address, and a human being using the link to confirm to Lp that the address is owned.02:02
sinzuiwallyworld_, I will tell the squad about the email address RE tomorrow.02:02
wallyworld_sinzui: yes, that's my point. so we would want to keep the sendTeamEmailAddressValidationEmail() method and ditch the RE?02:02
sinzuithough the beer in me wants to tell the bogus yarn now02:03
wallyworld_the RE is used during form submission of the contact address edit form02:03
wallyworld_the send email and human clicks link is used for team creation02:03
wallyworld_but we are removing the latter02:03
wallyworld_so the question is - do we want to augment the RE check with the send email check on the edit contact adress form02:04
sinzuiwallyworld_,  I think we do want to keep it.02:05
sinzuisendTeamEmailAddressValidationEmail() is the proper method02:05
wallyworld_ok, thanks. will do that02:05
wallyworld_confusing that we diverged02:05
sinzuiwallyworld_, yes. I just read the code. That is the proper method. The one we send to users would be a lie02:06
wallyworld_it would be good to know why we only used that method on team creation02:07
wallyworld_and not when editing the external contact address later02:07
wallyworld_oh, i lied, we do send it02:10
StevenKsinzui, wgrant: Bug 933935 can be closed now?02:13
_mup_Bug #933935: Remove bug and branch subscription checks from visibility checks <disclosure> <sharing> <tech-debt> <Launchpad itself:Triaged> < https://launchpad.net/bugs/933935 >02:13
sinzuiI don't know, sorry02:15
wgrantStevenK: Indeed, I've closed it02:15
wgrantThe last subscription check was removed from production an hour ago :)02:15
wgrantI think that the BVP replacement I'm working on and the release of writable +sharing will close at least 25 bugs.02:19
StevenKwgrant: Can I start on that? I'm looking for something to do.02:19
wgrantStevenK: How much do you know about bug notifications?02:20
StevenKEnough to know that I don't want to know more.02:21
StevenKwgrant: Whyfor?02:21
wgrantBug #933934 is a blocker with a significant amount of remaining work.02:21
_mup_Bug #933934: Remove the bug supervisor/security contact subscriptions rules <disclosure> <sharing> <tech-debt> <Launchpad itself:Triaged> < https://launchpad.net/bugs/933934 >02:21
wgrantsinzui: ^^02:21
StevenKHello minefield, please blow my foot off.02:21
wgrantWe need structsub filters by information-type, and we need structsubs to work for private bugs.02:22
wgrantThe rules here are very well-defined, fortunately.02:22
sinzuiI think that will have to happen when sharing is out of beta02:22
sinzuiThat will be fun code to cut02:22
StevenKwgrant: bug 297756 is close to being closeable, too02:22
_mup_Bug #297756: Cannot manage access to a project's private bugs and branches <disclosure> <lp-bugs> <oem-services> <sharing> <Launchpad itself:Triaged> < https://launchpad.net/bugs/297756 >02:22
wgrantStevenK: Right, that's one of the >20 :)02:22
StevenKsinzui: Why? structsub work seems out of the way02:23
wgrantsinzui: It needs to be done before sharing can be really useful, and it has no dependency on sharing being complete.02:23
wgrantsinzui: We can't remove the default bugsupervisor sub until we've sorted out structural subs02:23
wgrantOtherwise nobody will be notified about new private bugs02:23
wgrant== bad02:24
* StevenK tosses a card from Backlog to Deployment-Ready in wgrant's name02:24
wgrantITYM Done-Done02:24
StevenKwgrant: I wasn't sure if the NDT was done because it's still Fix Committed02:25
wgrantIt's been on all the appservers for more than an hour. I think hloeung just hasn't noticed it's finished yet.02:25
StevenKHahaha02:25
sinzuiwgrant, okay, I think we have a card for that. I think there is a bug suggesting that we create structural subscriptions for security contacts and bug supervisors when we enter beta so that there is no apparent change in behaviour02:26
StevenKsinzui, wgrant: So I will look at making structsubs work with private bugs.02:27
StevenKOr I can do filter by information_type first02:27
wgrantStevenK: Right. There's two largely separate pieces of work: firstly, structsubs have to work for private bugs. Secondly, they have to be able to filter by information type02:27
wgrantYou can't do the filtering by information_type first, since most of the other information types are private :)02:28
sinzuiStevenK,  Bug #1008526 and Bug #1008538 roughly describe the forthcoming train wreck that we want to avert02:28
wgrantSo it's going to be a bit hard to test02:28
_mup_Bug #1008526: Security contacts are not notified when the project is not shared <bugs> <disclosure> <sharing> <Launchpad itself:Triaged> < https://launchpad.net/bugs/1008526 >02:28
_mup_Bug #1008538: Bug Supervisors are not notified when the project is not shared <bugs> <disclosure> <sharing> <Launchpad itself:Triaged> < https://launchpad.net/bugs/1008538 >02:28
wgrantsinzui: Bug #1008541 too02:28
_mup_Bug #1008541: Sharing policies unconfigure existing projects <bugs> <disclosure> <sharing> <Launchpad itself:Triaged> < https://launchpad.net/bugs/1008541 >02:28
sinzuiyep02:28
StevenKwgrant: Is there a bug about structsubs on private bugs?02:28
wgrantStevenK: Bug #376186 is the main bug for that02:29
_mup_Bug #376186: implicit (e.g.structural) subscriptions to private bugs don't work even when the subscriber has visibility on the bug <disclosure> <lp-bugs> <privacy> <sharing> <story-better-bug-notification> <ubuntu-qa> <Apport:Won't Fix> <Launchpad itself:Triaged> < https://launchpad.net/bugs/376186 >02:29
sinzuiStevenK, nothing old that I am aware of. We know that these three bugs assume SS work with privacy02:29
StevenKwgrant: Right02:30
sinzuiSo I tagged it but could not remember. maybe I need to switch to ice cream02:30
wgrantStevenK: Bug #901548 should be fixed implicitly by that, but it's something to keep in mind.02:30
_mup_Bug #901548: launchpad does not send emails to the assignee of private bugs <bugs> <email> <privacy> <sharing> <Launchpad itself:Triaged> < https://launchpad.net/bugs/901548 >02:30
* StevenK looks for a card for that bug02:31
StevenKSearching Kanban is as bas as searching LP bugs02:31
StevenKSo I'm glad it's not just us02:31
wgrantStevenK: I meant to create one yesterday, but then code privacy burnt down.02:31
wgrantI don't think there is one.02:31
StevenKwgrant: But then we teamed up and rebuilt it stronger, faster and better.02:32
sinzuiwgrant, I updated https://wiki.canonical.com/InformationInfrastructure/OSA/LP/DeploymentIssues/2012-07-10-revert-NDT02:32
wgrantStevenK: I hope this series of tasks is a bit less fraught with inclarity and terror than your last one with branch privacy...02:32
StevenKHaha02:32
wgrantsinzui: Thanks, looking.02:32
StevenKsinzui: ArtifactAccessGrants02:33
wgrantAccessArtifactGrants02:33
StevenKArtefact is something much older02:33
StevenKAnd I don't think it was 2500 branches02:33
wgrantsinzui: If you're still editing, it might be worth noting that 99% of the 2500 were old misconfigured branches.02:33
wgrantStevenK: Slightly under 2400.02:33
wgrantBut 2500 is close enough :)02:33
StevenKWe only fixed like 140?02:34
sinzuiI will add that in another footnote. I don't want to brag about the period were projects were setup correctly02:34
wgrantStevenK: Oh, you must have been busy last night.02:34
wgrantStevenK: There was a secondary disaster after the one sinzui notified us of.02:34
StevenKYeah, I'm reading it now02:34
StevenKI was off IRC02:35
sinzuiah 240002:37
StevenKwgrant: Can I have a starting thread to tug at?03:43
wgrantStevenK: Bug.getBugNotificationRecipients03:46
wgrantAnd get_also_notified_subscribers03:47
wgrant    if bug.private:03:47
wgrant        return []03:47
StevenKI was just laughing at the assertion in getBugNotificationRecipients03:47
StevenKwgrant: So I guess the plan would be to have the functions do the usual things (rather than bugging out early for private bugs) and then filtering the results against get_bug_privacy_filter or something like it?04:51
lifelessshouldn04:51
lifelessbah04:51
lifelessignore tht04:51
wgrantStevenK: Right04:52
StevenKwgrant: I just hate the idea of looping over get_bug_privacy_filter04:52
wgrantStevenK: There's one significant question that's unanswered.04:52
StevenKwgrant: Private dupes?04:53
wgrantStevenK: We should possibly do the filtering when we're calculating the recipients04:53
wgrantBut we don't expand teams at that stage04:53
wgrantWe only expand teams when we're sending mail04:53
wgrantWell04:54
wgrantI guess it's not clear that we want to do the filtering at the time of the action.04:54
wgrantlifeless: What do you think?04:54
wgrantYou have opinions on this matter04:54
StevenKs/ on this matter//04:54
lifelessI would like to offer some constraints04:55
wgrantThey're all wrong.04:55
lifelessdon't do something incompatible with a notification service04:55
lifelesswhich can do team expansion itself, but can't callback for individual visibility rules.04:55
wgrantIt's not at all clear that that constraint is necessary or supportable.04:56
wgrantBut it might be nice.04:56
StevenKWe certainly need it.04:56
lifelessI have every intention of landing my stuff at some point; if its incompatible with that constraint, it will get dropped/redefined/changed to be compatible at that time,.04:56
lifelessI'd rather not rework something you're reworking Right Now.04:57
lifelesswhat else04:57
wgrantI guess team structural subscriptions are evil anyway, so we can probably disregard them.04:57
lifelessuhm, yes, duplicates and notifications are a pain.04:57
wgrantDo the filtering at the time of the action04:57
wgrantSo BugNotificationRecipient will continue to have only permissible recipients.04:58
lifelessHow would it have others? [were you thinking to check subscriptions without cross referencing grants?]04:58
wgrantlifeless: Well, the other option is to insert everything into BugNotificationRecipient and filter after team expansion in the sending cronscript. That would mean members could get mail through a team subscription as long as they had a grant, even if the team did not.05:00
wgrantBut team subscriptions are evil and should probably be disallowed, so it's not a major loss to break that.05:00
lifelesswgrant: I'm not clear how team subscriptions would be broken05:00
lifelesswgrant: grants -> subscriptions -> TP -> persons.05:01
lifelessits one query, no ?05:01
wgrantlifeless: I believe BugNotificationRecipient is the un-team-expanded set.05:07
wgrantYay, bugsummaryrebuild works05:09
wgrantAnd the result is even correct05:10
lifelesswgrant: I don't see how checking access at the front end prohibits teams working in the backend05:12
wgrantlifeless: If we only insert into BugNotificationRecipient those Persons that have access, then team members that have access won't get email if their team doesn't have access.05:13
wgrantThe entire team will be mailed, or none of it will.05:13
lifelesswgrant: if you dedup before inserting ?05:14
lifelesswgrant: but that implies you are deduping before checking access05:14
lifelesswhich is precisely not checking access at the front end of the process05:15
wgrantThe current pipeline is: event -> BugNotificationRecipient -> team expansion -> email05:15
wgrantThe question is whether we put the access check after event or after team expansion.05:16
wgrantDeduping isn't relevant here05:16
lifelessoh, I see05:17
lifelessyou're postulating the following scenario:05:17
lifelessstructural subscription for team A05:17
lifelessno grant for team A05:17
lifelessperson X, a member of team A, has a grant.05:17
wgrantRight.05:17
lifelesseither via team B, or via a direct subscription and a person-X direct grant.05:18
lifelessgiven that we filter such teams from the list of who will be notified today, I would say that X should not expect a notification, except and unless A is given a grant.05:19
lifelessIts confusing and inconsistent to have such metaconfiguration possible. IMNSHO.05:19
lifelessis that a useful opinion ?05:19
wgrantIndeed, it supports my feeling, so it's useful :)05:20
wgrantStevenK: So it's nice and easy05:20
StevenKwgrant: It is?05:25
wgrantStevenK: Yeah, I think you can just remove the special-case which excludes indirect subscriptions, and add a filter on the end of getIndirectSubscribers to only return those people who satsify get_bug_privacy_filter05:28
StevenKwgrant: As well as get_also_notified_subscribers?05:29
wgrantStevenK: getIndirectSubscribers calls get_also_notified_subscribers05:29
wgrantStevenK: As well as getting dupe subs05:29
wgrantBoth of which need to be filtered, I suspect.05:29
wgrantUnless we don't want dupe subs to count at all, but that would seem odd05:29
StevenKwgrant: Right, so now I'm concerned about how to do the filtering. Since get_bug_privacy_filter only takes one user, I don't want to loop over it.05:30
wgrantStevenK: Ye of little faith05:31
StevenKwgrant: I know they're storm fragments, so it can't get that bad, but ...05:32
wgrantStevenK: RemoveArtifactSubscriptionsJob.run()05:32
wgrantStevenK: It uses get_bug_privacy_filter_terms manually to do a bulk access check05:32
wgrantIn a tasteful fashion.05:32
=== almaisan-away is now known as al-maisan
wgrantStevenK: Making any sense at all?06:26
StevenKgary_poster: I hope you mean 'July 6'07:01
adeuringgood morning07:42
=== frankban changed the topic of #launchpad-dev to: http://dev.launchpad.net/ | On call reviewer: frankban* (rvba) | Firefighting: - | Critical bugs: 4.0*10^2
StevenKjtv: Hai09:01
jtvHi StevenK09:01
StevenKjtv: Could I get your opinion on https://code.launchpad.net/~stevenk/launchpad/kill-rpsd/+merge/114300 ?09:01
jtvStevenK: people keep saying that it's been replaced by a job, but every time I check we're not quite there yet.  Where does that stand?09:02
StevenKjtv: I have no idea, TBH09:05
jtvThat might be worth checking.  The bit that was always missing was a background scrubber that fires off jobs for all POFiles, not just ones that we know need their stats updated.09:06
StevenKbenji: ^ Anything light you can shed on that? I *think* it was you that wrote the job.09:27
jmlif it's not being run at all, then why does it matter?09:53
StevenKjml: Because the job may end up relying on infrastructure I'm proposing to remove.10:57
=== al-maisan is now known as almaisan-away
jmlStevenK: so then you can restore the code if that turns out to be the case.10:58
=== matsubara is now known as matsubara-afk
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
=== almaisan-away is now known as al-maisan
gary_posterStevenK, heh, whoops, yes :-)12:08
=== abentley changed the topic of #launchpad-dev to: http://dev.launchpad.net/ | On call reviewer: frankban* (rvba), abentley | Firefighting: - | Critical bugs: 4.0*10^2
=== salgado is now known as salgado-brb
=== salgado-brb is now known as salgado
=== al-maisan is now known as almaisan-away
czajkowskigary_poster: did you get your juju mp sorted yet?14:59
gary_posterczajkowski, no, but thank you for mentioning it on G+ :-) We need juju charmers to do the work15:02
czajkowskiok15:03
czajkowskilet me go and poke15:03
gary_posterheh, thanks czajkowski15:03
=== mpt_ is now known as mpt
=== matsubara-afk is now known as matsubara
=== frankban changed the topic of #launchpad-dev to: http://dev.launchpad.net/ | On call reviewer: abentley | Firefighting: - | Critical bugs: 4.0*10^2
=== salgado is now known as salgado-lunch
=== salgado-lunch is now known as salgado
czajkowskibkerensa_: hey18:02
bkerensa_hi18:02
czajkowskibkerensa_: gary_poster is the one who is looking for juju help18:02
=== bkerensa_ is now known as bkerensa
bkerensahi gary_poster18:03
gary_posterbkerensa, hi18:20
bkerensagary_poster: I hear you are running into some issues with your charm? Perhaps I might be of assistance18:20
gary_posterbkerensa, what we need is some packaging help.18:20
gary_posterbkerensa, not exactly18:21
bkerensapackaging?18:21
gary_posterlet me get you a mp18:21
bkerensak18:21
gary_posterit is charm-helpers18:21
gary_posterbkerensa, we've talked to mark_mims and SpamapS about this before; we're just hoping to get it resolved sooner rather than later.  Here's one MP... https://code.launchpad.net/~gmb/charm-tools/add-charm-helpers/+merge/9620418:23
gary_posterThat depends on packaing python-shelltoolbox18:23
bkerensagary_poster: Were mark_mims and Spamaps not able to help? They are perhaps the best Juju Hackers :)18:23
bkerensaahh I see18:24
bkerensaso this is in regards to the juju trunk and not a actual juju charm?18:24
bkerensacharm-tools specifically18:24
gary_posterbkerensa, they want to help.  we just haven't been able to get their help.  Here is the most recent branch/MP, actualy.18:25
gary_posterhttps://code.launchpad.net/~yellow/charm-tools/trunk/+merge/10155418:25
gary_posterThey have been too busy to help18:25
gary_posterand this has gone on for months and months now18:26
gary_posterand we would like to get this resolved18:26
bkerensaahh well I'm unfortunately not the right person... I just author charms and do not work on the juju or charm-tools branches at all.... I will ping mark and Spaamaps but also have you perhaps talked to jcastro since he is the Cloud Liason?18:27
bkerensagary_poster:  bkerensa: yeah, I really need to just sit down and do this. Perhaps today18:27
bkerensaso it looks like Clint is going to get working on this18:27
gary_posterbkerensa, fantastic, thank you18:28
bkerensahopefully today but at least very soon18:28
gary_postercool18:28
czajkowskibkerensa: thanks18:28
bkerensamight wanna join #juju to follow up with him as neccesary or prod him a couple times18:28
bkerensa;)18:28
bkerensaczajkowski: no problem18:28
bacgary_poster: cool18:29
gary_posterthanks very much czajkowski !18:29
czajkowskigary_poster: see it pays to blog :)18:30
gary_posterczajkowski, :-)18:30
=== salgado is now known as salgado-afk
sinzuijcsackett, wgrant, wallyworld_, StevenK, This is my draft of a report stating what we have been doing over 13 months: http://people.canonical.com/~curtis/lp-milestone/report.html22:48
StevenKwgrant: Total: 120 tests, 3 failures, 0 errors in 2 minutes 17.362 seconds.23:03
wgrantStevenK: Not bad23:05
StevenKwgrant: Those 3 failures are all TestNotificationRecipientsOfPrivateBugs23:09
StevenKwgrant: http://pastebin.ubuntu.com/1087043/23:09
jcsackettsinzui: Mumble crashed just as you suggested we adjourn. So the tech spirits agreed with you. :-p23:15
StevenKwgrant: I've had to comment out the issuperset assert too23:17
wgrantIndeed23:24
StevenKwgrant: I'm just wondering why that assert is there23:43
StevenKwgrant: Total: 120 tests, 0 failures, 0 errors in 2 minutes 17.914 seconds.23:44
StevenK% bzr damage23:44
StevenKUsing submit branch /home/steven/launchpad/lp-branches/devel23:44
StevenKDamage: 0 lines of code23:44
wgrantStevenK: I don't really know23:45

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