/srv/irclogs.ubuntu.com/2015/09/14/#juju-dev.txt

davecheneyhow are we doing on those blockers ?01:14
davecheneymwhudson: did you fix http://pad.lv/149444101:15
davecheney>01:15
axwthumper: re #1495320, why should we have any of those things? IMO we should have per-facade mock states, which is what some of the newer facades have been doing already01:15
mupBug #1495320: New base test suite for apiserver <tech-debt> <juju-core:Triaged> <https://launchpad.net/bugs/1495320>01:15
thumperaxw: fair point...01:17
axwwallyworld: FYI, https://bugs.launchpad.net/juju-core/+bug/149533801:35
mupBug #1495338: cmd/juju/storage: "volume list" YAML/JSON format is non-obvious <juju-core:In Progress by axwalk> <https://launchpad.net/bugs/1495338>01:35
wallyworldnp, ty01:35
anastasiamacaxw: this is a nice bug :D i wish they were all like that!01:37
mupBug #1495338 opened: cmd/juju/storage: "volume list" YAML/JSON format is non-obvious <juju-core:Triaged by axwalk> <juju-core 1.25:In Progress by axwalk> <https://launchpad.net/bugs/1495338>01:59
wallyworldthumper: waigani: please don't use JujuConnSuite for testing new apiserver facades02:10
wallyworldthere's plenty of existing apiserver facades that have been written with better tests you can copy fro02:11
waiganiwallyworld: okay, sorry02:11
wallyworldwaigani: best not to perpetuate our misery :-)02:12
wallyworldespecially for new work02:12
wallyworldadding a new test i could live with02:12
wallyworldbut a whole new facade package, not really02:12
waiganiwallyworld: yep, understood - fixing it now02:13
wallyworldwaigani: there should be a happy path feature test though that (for now) does use jujuconnsuite to ensure it is glued together end-end02:14
wallyworldin the featuretests package02:15
waiganiwallyworld: I was going to add a feature test once the api and worker have landed, to make sure they all work as intended.02:17
axwwallyworld anastasiamac: how's this look as an alternative "volume list" YAML format? http://paste.ubuntu.com/12405626/02:27
anastasiamacaxw: "machines" as a collection? :D02:28
anastasiamaclooks nice :))02:28
axwwallyworld anastasiamac: there will be a "units" field below "machines" when the data is available in the API02:28
anastasiamac\o/02:28
anastasiamacpersonally, i like :)02:28
wallyworldaxw: "provider-id" - could that be just "id", or "volume-id"02:28
axwwallyworld: hum, I'm trying to distinguish between the internal and provider-supplied one. it's kinda ambiguous02:29
wallyworldyeah02:29
anastasiamacaxw: is status per volume or machine/unit? coz what does "attached" mean when there r 1+ machines/units?02:29
axwanastasiamac: currently only per volume, but later we'd have per-machine and per-unit also (and they'll go in the "machines" struct, along with "device" and "read-only"02:30
axwanastasiamac: atm, "attached" means all attachments are created02:30
axwotherwise it's "attaching"02:31
anastasiamacaxw: sounds great! let's remember to deal with/display multiple status when we have per-machine and per-unit specific ones :D02:32
axwanastasiamac: I'll adda  TODO in the relevant structs02:32
anastasiamacaxw: tyvm for making output user-helpful \o/02:32
axwanastasiamac: np02:33
wallyworldaxw: the id i think should be whatever we expect the user to use when we add CLI that requires it to identify a volume02:33
axwwallyworld: yeah, that's the top-level string "1/0"02:33
axwwallyworld: same sort of format for machine IDs as in "juju status"02:33
wallyworldok, yeah, that makes sense02:34
axwwallyworld: so, yea or nay?02:38
wallyworldaxw: oh sorry, +1 i think02:38
wallyworldis the user generally inetrested in provider id?02:39
wallyworldcould it be left off?02:39
axwwallyworld: same level of interest as people have in instance IDs02:39
axwwallyworld: useful for matching up juju resources with things in your cloud provider02:39
wallyworldso it adds value in showing it02:40
axwwallyworld: I think so02:40
wallyworldsgtm02:40
thumperwallyworld: got 10 minutes for a quick chat about a critical bug?02:47
thumperwallyworld: it has to do with the new uniter code02:47
wallyworldsure02:47
thumperhttps://bugs.launchpad.net/juju-core/+bug/149435602:47
mupBug #1494356: OS-deployer job fails to complete <blocker> <ci> <regression> <juju-core:In Progress by thumper> <https://launchpad.net/bugs/1494356>02:47
thumper1:1 hangout02:47
mupBug #1495320 changed: New base test suite for apiserver <tech-debt> <juju-core:Invalid> <https://launchpad.net/bugs/1495320>03:14
mupBug #1495320 opened: New base test suite for apiserver <tech-debt> <juju-core:Invalid> <https://launchpad.net/bugs/1495320>03:17
mupBug #1495320 changed: New base test suite for apiserver <tech-debt> <juju-core:Invalid> <https://launchpad.net/bugs/1495320>03:23
mupBug #1495320 opened: New base test suite for apiserver <tech-debt> <juju-core:Invalid> <https://launchpad.net/bugs/1495320>03:29
mupBug #1495320 changed: New base test suite for apiserver <tech-debt> <juju-core:Invalid> <https://launchpad.net/bugs/1495320>03:32
thumperah fuck03:40
thumpermy passport hits the <6 months until expiry mid-sprint03:40
davecheneyyou shall receive an imigration fail03:41
davecheney3 weeks, you should be able to get an expidited one by then03:42
thumper10 working days for NZ is normal03:44
thumperFile type: Jpg or Jpeg03:44
thumperheh03:44
thumperfor photo03:44
davecheneywill they accept JPEG ?03:47
thumperhmm... deems dubious03:47
thumperseems03:48
wallyworldthumper: i got my passport in 2 days after paying an exhorbitant fee after i put it through the wash 10 days before the malta sprint03:50
thumperheh03:51
thumperI don't want to pay the 2x amount for 3 day shipping03:51
thumper10 should be fine03:51
mwhudsondavecheney: yes, but the fix will take a loong time to get anywhere i suspect04:03
davecheneymwhudson: that's what I figured04:11
davecheneyit looks like the commit that used the encoding package got rolled back for unrelated reasons04:11
davecheneycan we mark that issue as not a blocker for now ?04:11
mwhudsoni don't actually understand all steps of the process by which the fix will get into trusty-updates, i guess it would be good to learn that04:12
mwhudsonbut oops, i'm supposed to be on leave today :-)04:12
thumperwallyworld: http://reviews.vapour.ws/r/2650/04:18
wallyworldlooking04:18
wallyworldthumper: +104:19
thumperwallyworld: pretty dull fix I admit04:19
davecheneyship it04:21
thumperoh fuck04:29
* thumper found a bad bug04:29
thumpertesting bug only04:29
thumperwindows only04:29
thumperbut bad none the less04:29
* thumper things04:30
thumperand thnks04:30
* thumper gives up04:30
* thumper head-desks04:33
thumperMEH04:37
thumperanyone got a windows 2012 image running?04:38
thumperwallyworld: another quick sanity check chat?04:38
wallyworldsure04:38
thumperwallyworld: http://reviews.vapour.ws/r/2651/diff/#05:02
wallyworldlooking05:02
wallyworldthumper: thanks for fixing that05:04
thumperwallyworld: np05:04
thumperdavecheney: that last one was just a windows time bomb05:16
thumperdavecheney: it was bound to fail eventually05:16
thumper:)05:16
waiganithumper: http://pastebin.ubuntu.com/12406461/05:31
waiganithumper: first three is using jujuconnsuite05:32
waiganithumper: second three, after pop, are using a mock state05:32
waiganiwallyworld, thumper: updated PR: http://reviews.vapour.ws/r/2649/05:39
wallyworldlooking05:39
wallyworldwaigani: i don't like how getEnvironment is patched. hopefully my comments make sense05:51
wallyworldit's unnecessary05:51
waiganiwallyworld: okay, thanks for the review05:51
waiganiwallyworld: btw rewriting from jujuconnsuite to mock state afforded me the opportunity to benchmark the two: http://pastebin.ubuntu.com/12406461/05:54
waiganiwallyworld: after the pop is with the mock05:54
wallyworldwaigani: yeah. although even with the mock the numbers look too high05:55
wallyworldi would expect say 5 or 10ms05:55
wallyworldbut still a good reduction05:55
waiganihmm, that could be my laptop..05:55
wallyworldmaybe there's something else there that needs fixing also05:55
wallyworldwaigani: did you remember to remove the ngotestsuite05:56
waiganiwallyworld: I think so... I'll check05:56
waiganiwallyworld: good catch, that was it.05:57
wallyworldthought so :-)05:58
wallyworldi didn't believe you when you said you'd removed it :-)05:58
wallyworldaxw: this fixes a ci blocker, removes a crappy initial port of the update status stuff that i did http://reviews.vapour.ws/r/2652/05:59
axwwallyworld: okey dokey, looking05:59
axwwallyworld: is operation.State.UpdateStatusTime used at all after these changes?06:03
wallyworldaxw: no, not supposed to be, did i forget to remove it06:04
axwwallyworld: I think so06:04
wallyworldffs, so i did06:04
axwwallyworld: can you please explain how it was spinning before?06:05
wallyworldtl;dr; the decoupling of remote state from the update status hook action meant that the previous helper to find the duration to wait based on now and last fire time would always trigger a very short wait06:06
wallyworldand that would caue the timer to fire again06:06
wallyworldand again06:06
wallyworldand again06:06
axwwallyworld: ah, I see06:06
wallyworldthe old world and new didn't match06:07
axwwallyworld: so now we always just wait for the full period, right?06:07
axwwallyworld: and if somethign else happens within that period, we'll wait again for another full period06:07
wallyworldyeah, but all we do is update the counter06:07
axwyep06:07
wallyworldeach time the update status hook runs, it sets current value to current counter06:08
wallyworldcounter could be +10 or +20 over last local recorded value, we dont care06:08
wallyworldwe just wait till idle and see if counters are different06:08
axwwallyworld: yeah I was just thinking about the difference in when the remote state watcher is triggered. I think with this change we'll never set status until the unit has quiesced, and *then* the update-status idle period has elapsed06:09
axwas opposed to period since the last update06:09
axwwallyworld: (which seems fine to me)06:09
wallyworldme too06:09
wallyworldbecause when hooks are run, unit can set status06:09
wallyworldso it could have done it during config changed or something06:10
axwwallyworld: thanks. reviewed06:11
wallyworldtyvm06:11
wallyworldaxw: i had a small unit test that showed the spinning, but it used wall clock so i removed it06:11
wallyworldi'll test live also after school pickup06:12
axwwallyworld: don't suppose you're still working are you?08:10
wallyworldaxw: hey08:13
voidspacefrobware: dimitern: TheMue: dooferlad: morning, I'm back in the UK09:58
dimiternvoidspace, morning :)09:58
frobwarevoidspace, hiya09:59
dooferladvoidspace: welcome back. Enjoy the rain!09:59
voidspaceo/10:00
voidspacedooferlad: hehe, we had quite a lot of rain (warm rain though) in North Carolina. A couple of impressive thunderstorms.10:01
voidspacedooferlad: a few days of good sun too though.10:01
voidspacedimitern: frobware: so fwreade gave me a comprehensive review on my "unit public address branch"10:02
voidspacedimitern: frobware: I've already started work on it - the biggest change is to set the "preferred addresses" (he doesn't like the Default name) when the addresses are set rather than when they're fetched10:02
voidspacedimitern: frobware: plus a bunch of issues he identified in existing code that the PR touches10:03
voidspacedimitern: frobware: so that's what I'm up to...10:03
voidspacefrobware: when is good for you to chat?10:03
frobwarevoidspace, now is good.10:03
voidspacefrobware: cool10:03
voidspacefrobware: hmm.... the one-to-one isn't on my calendar for some reason10:04
voidspacefrobware: what hangout should we use?10:04
frobwarevoidspace, I just sent you an invite (https://plus.google.com/hangouts/_/ejtwk7d5mqnwljcwmbxkvzi2uaa?hl=en-GB&authuser=0)10:05
voidspacefrobware: gah, I have to do the authentication dance - there in a minute10:06
voidspacefrobware: https://bugs.launchpad.net/juju-core/+bug/143528310:18
mupBug #1435283: juju occasionally switches a units public-address if an additional interface is added post-deployment <addressability> <bug-squad> <network> <openstack-provider> <juju-core:Triaged by mfoord> <https://launchpad.net/bugs/1435283>10:18
voidspacefrobware:  http://reviews.vapour.ws/r/2593/10:20
dimiternvoidspace, I'm fine with calling it preferred instead of default10:23
voidspacedimitern: yeah, me too10:30
rogpeppemwhudson, anyone else: do you know the status of this bug? https://bugs.launchpad.net/juju-core/+bug/149444112:12
mupBug #1494441: ppc64el: cannot find package "encoding" <blocker> <ci> <ppc64el> <regression> <unit-tests> <juju-core:Triaged> <gccgo-go (Ubuntu):Invalid> <gccgo-go (Ubuntu Trusty):In Progress> <https://launchpad.net/bugs/1494441>12:12
perrito666hey, if I wanted to stop/start juju mongo on local provider, where would I find the start/stop script?12:19
perrito666meh systemv12:26
rogpeppejam1: any idea if this bug is likely to be fixed, by any chance? https://bugs.launchpad.net/juju-core/+bug/149444112:42
mupBug #1494441: ppc64el: cannot find package "encoding" <blocker> <ci> <ppc64el> <regression> <unit-tests> <juju-core:Triaged> <gccgo-go (Ubuntu):Invalid> <gccgo-go (Ubuntu Trusty):In Progress> <https://launchpad.net/bugs/1494441>12:42
rogpeppejam1: it's blocking us currently12:42
=== akhavr1 is now known as akhavr
=== jam1 is now known as jam
jamrogpeppe: this is the first that I've heard of the problem. It is marked as In Progress my mwhudson12:45
rogpeppejam: ok, thanks. i'll wait for him to come online12:46
jamwhich might be the patch he proposed, I'm not sure the timeline for getting that actually into the trusty gcc-go build12:46
jamalexisb would be another person to raise awareness of the bug to12:46
mattywwallyworld, just saw the news, congratulations12:52
wallyworldmattyw: 4th one in 5 years :-(12:53
wallyworldas bad as italy12:53
mattywwallyworld, you going to put your name forward?12:53
wallyworldthinking about it12:53
wallyworldcan't do any worse12:54
=== akhavr1 is now known as akhavr
fwereadeok, I have been pushing through a filthy headache for a while, and I'm not actually getting anything done13:03
* fwereade goes to lie down13:03
=== natefinch-afk is now known as natefinch
mupBug #1495542 opened: 1.20.x cannot upgrade to 1.26-alpha1 <blocker> <ci> <regression> <upgrade-juju> <juju-core:Triaged> <https://launchpad.net/bugs/1495542>14:22
katcoericsnow: natefinch: looks like there is a new blocker: 149554214:27
katcobug 149554214:27
mupBug #1495542: 1.20.x cannot upgrade to 1.26-alpha1 <blocker> <ci> <regression> <upgrade-juju> <juju-core:Triaged> <https://launchpad.net/bugs/1495542>14:27
ericsnowkatco: related to #1494070, perhaps?14:28
mupBug #1494070: unit agent upgrade steps not run <juju-core:Triaged> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1494070>14:28
katcoericsnow: sounds plausibly correct. sinzui is that a dupe?14:28
katcoericsnow: at any rate, pick that one up and maybe you'll find they're the same thing14:30
katcoericsnow: pick the blocker up that is14:30
ericsnowkatco: k14:30
natefinchgodspeed, ericsnow14:30
mgzkatco: my guess is it's not related14:30
natefinchI've always wanted to say that14:31
mgzkatco: as we have to un-run upgrade steps, one long standing, and casey hacked around the other one14:31
ericsnowkatco, natefinch: FYI, looks like the 1.25-beta1 list has several open that have been resolved14:32
katcoericsnow: example?14:33
ericsnowkatco: #146531714:34
mupBug #1465317: Wily osx win: panic: osVersion reported an error: Could not determine series <osx> <packaging> <wily> <windows> <juju-core:Triaged> <juju-release-tools:Fix Released by sinzui> <https://launchpad.net/bugs/1465317>14:34
sinzuikatco: ericsnow Well, if that bug is a dupe then it isn't 100% correct. http://reports.vapour.ws/releases/3049/job/aws-upgrade-20-trusty-amd64/attempt/8 shows 1.20 can upgrade to 1.2514:34
ericsnowmay or may not be forward-ported14:34
katcoericsnow: what makes you say this is resolved?14:35
ericsnowkatco: fixed in an earlier version14:36
katcoericsnow: how do you know that? and why isn't this bug targeted to that version?14:36
* ericsnow only skimmed through, so only a quick estimation14:36
ericsnowkatco: sorry, bad example14:37
katcoericsnow: no worries, just trying to get up to speed14:37
ericsnowkatco: #1468815 is better14:37
mupBug #1468815: Upgrade fails moving syslog config files "invalid argument" <ci> <regression> <upgrade-juju> <juju-core:Triaged> <juju-core 1.24:Fix Released by ericsnowcurrently> <https://launchpad.net/bugs/1468815>14:37
katcoericsnow: k, same question... what makes you think it's resolved in 1.25-beta?14:38
ericsnowkatco: it *might* be resolved already14:38
katcoericsnow: based on what?14:38
ericsnowkatco: fix-released on 1.2414:39
katcoericsnow: so you're thinking 1.25-beta1 was cut after this fix was released?14:39
ericsnowkatco: rather that someone may have forward-ported and not updated the ticket14:40
ericsnowkatco: or that it just needs a forward-port14:40
katcoericsnow: couldn't we say that about any bug?14:41
ericsnowkatco: sure, as long as it's been fixed in an earlier release14:41
ericsnowkatco: another example: #144905414:42
mupBug #1449054: Intermittent panic: rescanned document <ci> <test-failure> <juju-core:Triaged> <juju-core 1.22:Fix Released by dimitern> <juju-core 1.23:Won't Fix by fwereade> <juju-core 1.24:Fix Released by fwereade> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1449054>14:42
katcoericsnow: hm. just unsure why someone would go through the trouble of forward-porting without updating the bug.14:42
ericsnowkatco: sometimes folks simply merge an earlier branch forward, picking up multiple fixes14:43
katcoericsnow: ah, this is the whole merge vs. cherrypick issue?14:43
ericsnowkatco: sometimes14:43
=== natefinch is now known as natefinch-afk
ericsnowkatco: anyway, at the least there are some bugs on that list that may just need forward-porting14:44
katcoericsnow: yep14:44
ericsnowkatco: I guess that was my original point lol14:44
katcoericsnow: thanks for walking me through your thought process14:44
ericsnowkatco: haha14:44
katcoericsnow: no seriously :) just wasn't understanding how you arrived at that conclusion14:45
ericsnowkatco: mostly I skimmed through the list and several looked like ones we'd already fixed :)14:45
rogpeppehi peeps, this PR was backed out earlier because of issues not directly related to the PR itself. This is a re-proposal: https://github.com/juju/juju/pull/327515:50
rogpeppecould someone please rubberstamp it please?15:50
dooferladdimitern: ping!16:03
dooferladdimitern, voidspace: https://plus.google.com/hangouts/_/canonical.com/networking?authuser=016:04
dimiterndooferlad, omw16:04
cmarsrogpeppe, looking16:07
rogpeppecmars: thanks16:07
rogpeppecmars: though i already have two reviews, just waiting for the juju blockage clouds to lift momentarily so i can land it16:08
mupBug #1495591 opened: TestRunCommand fails on windows <blocker> <ci> <test-failure> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1495591>16:16
voidspacedooferlad: omw16:18
voidspacedooferlad: thanks16:19
voidspacedooferlad: ah, I'm late16:19
mupBug #1495591 changed: TestRunCommand fails on windows <blocker> <ci> <test-failure> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1495591>16:19
mupBug #1463408 changed: TestRunCommand fails <ci> <intermittent-failure> <test-failure> <juju-core:Fix Released> <juju-core db-log:Fix Released> <https://launchpad.net/bugs/1463408>16:25
mupBug #1495591 opened: TestRunCommand fails on windows <blocker> <ci> <test-failure> <windows> <juju-core:Triaged by cmars> <https://launchpad.net/bugs/1495591>16:25
mupBug #1463408 opened: TestRunCommand fails <ci> <intermittent-failure> <test-failure> <juju-core:Fix Released> <juju-core db-log:Fix Released> <https://launchpad.net/bugs/1463408>16:28
mupBug #1463408 changed: TestRunCommand fails <ci> <intermittent-failure> <test-failure> <juju-core:Fix Released> <juju-core db-log:Fix Released> <https://launchpad.net/bugs/1463408>16:40
rogpeppehere's a mostly-cosmetic change to the apiserver internals. review appreciated: http://reviews.vapour.ws/r/2656/16:54
=== natefinch-afk is now known as natefinch
jamkatco: ping18:07
katcojam: pong18:07
jamkatco: hi. are you able to meet tomorrow sometime early-ish in your morning?18:08
katcojam: sure18:09
katcojam: calendar is up to date18:09
jam11 or 12 utc ?18:09
katcojam: 12 would work better, but can make either time18:10
katcojam: thx for taking the time to meet18:15
jamkatco: happy to18:16
natefinchthat feeling when you've changed a whole bunch of code and finally get it all compiling... and the tests all pass on the first try.18:26
natefinch<_<18:26
natefinch>_>18:26
natefinchnot sure if tests are passing because you did it right... or there weren't tests for this code.18:26
jamrick_h_: your early meeting tomorrow needs to be postponed. I have to go to my son's school right at that time.19:01
jamanastasiamac: rick_h_: ^ same time on Wed works for me. I can also easily go 1 hr later if that helps Rick19:02
katcoericsnow: natefinch: can i run a question by one/both of you about constraints?19:07
ericsnowkatco: sure19:07
katcoericsnow: moonstone19:07
rick_h_jam: all good will work with anastasiamac and see what can be done19:09
mgzericsnow: do you need any help with bug 1495542?19:26
mupBug #1495542: 1.20.x cannot upgrade to 1.26-alpha1 <blocker> <ci> <regression> <upgrade-juju> <juju-core:In Progress by ericsnowcurrently> <https://launchpad.net/bugs/1495542>19:26
ericsnowmgz: not sure yet19:27
ericsnowmgz: still making sense of the logs19:27
ericsnowmgz: machine-0.log shows a panic, but the cause isn't exactly clear19:27
ericsnowyet19:27
mgzericsnow: hm, as does the previous run, suggests it's not random19:30
=== Guest39525 is now known as anthonyjf
mgzericsnow: the end cause of the test being failed is that the `juju set` token didn't propogate through the relation between charms19:32
=== anthonyf is now known as Guest95842
=== Guest95842 is now known as anthonyjf
=== natefinch is now known as natefinch-afk
mupBug #1495681 opened: quickstart delployments broken in 1.24 <blocker> <ci> <quickstart> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1495681>20:05
mupBug #1495681 changed: quickstart delployments broken in 1.24 <blocker> <ci> <quickstart> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1495681>20:08
mupBug #1495681 opened: quickstart delployments broken in 1.24 <blocker> <ci> <quickstart> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1495681>20:14
mupBug #1495681 changed: quickstart delployments broken in 1.24 <blocker> <ci> <quickstart> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1495681>20:17
mupBug #1495681 opened: quickstart delployments broken in 1.24 <blocker> <ci> <quickstart> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1495681>20:20
perrito666wow, juju is not especially smart to report when it has issues with the state server20:48
wallyworldericsnow: i'll take the session closed bug off your hands; looking at your analysis (thank you) it looks like something tanzanite landed is the cause20:51
ericsnowwallyworld: \o/20:51
katcowallyworld: hey have a sec before the release standup?20:52
wallyworldkatco: still in my jammies, just woke up, give me a few20:52
katcowallyworld: np at all... w/e you have time (can use 1:1)20:52
wallyworldok20:52
anastasiamacah there is proof that wallyworld does indeed sleep sometimes :D20:53
wallyworldhaha20:54
wallyworldlike you can talk :-P20:54
anastasiamac:P20:54
perrito666you should be both sleeping20:54
anastasiamacperrito666: no sleep for me - school dropoff :)20:55
perrito666do you people not have school buses?20:56
perrito666or school kangaroos?20:56
mupBug #1495681 changed: quickstart delployments broken in 1.24 <blocker> <ci> <quickstart> <regression> <juju-core:Invalid> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1495681>20:56
anastasiamacperrito666: not form where we r and not for 3yo anyway..21:09
anastasiamacperrito666: school buses here otherwise r known as parents :D21:09
perrito666anastasiamac: well that sounds terribly inefficient21:09
anastasiamacperrito666: are u saying tha parents r not efficient?21:10
anastasiamac:D21:10
perrito666well I live around the corner to a school21:11
perrito666parents here seem to think that their children might break if they walk something more than 2m21:12
perrito666which causes a heavy traffic jam 3 times a day21:12
xwwt2alexisb: We are running late21:30
alexisbxwwt2, ack21:30
xwwt2alexisb: We are having a meeting running long with good info.  We should bag release meeting?21:37
xwwt2s/?/.21:37
alexisbxwwt2, we are meeting tha tis fine21:37
alexisbdo what you need at the sprint21:37
mupBug #1449054 changed: Intermittent panic: rescanned document <ci> <test-failure> <juju-core:Fix Released> <juju-core 1.22:Fix Released by dimitern> <juju-core 1.23:Won't Fix by fwereade> <juju-core 1.24:Fix Released by fwereade> <juju-core 1.25:Fix Released> <https://launchpad.net/bugs/1449054>22:20
mupBug #1449054 opened: Intermittent panic: rescanned document <ci> <test-failure> <juju-core:Fix Released> <juju-core 1.22:Fix Released by dimitern> <juju-core 1.23:Won't Fix by fwereade> <juju-core 1.24:Fix Released by fwereade> <juju-core 1.25:Fix Released> <https://launchpad.net/bugs/1449054>22:32
mupBug #1449054 changed: Intermittent panic: rescanned document <ci> <test-failure> <juju-core:Fix Released> <juju-core 1.22:Fix Released by dimitern> <juju-core 1.23:Won't Fix by fwereade> <juju-core 1.24:Fix Released by fwereade> <juju-core 1.25:Fix Released> <https://launchpad.net/bugs/1449054>22:35
wallyworldaxw: anastasiamac: perrito666: give me a minute23:15
anastasiamacwallyworld: k23:15
wallyworldanastasiamac: we in standup23:25

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