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

ericsnowwallyworld: I think I figured it out (notes logged to the lp issue)00:11
wallyworldericsnow: sorry, still in meeting00:12
ericsnowwallyworld: the worker closes the channel when its loop finishes; so if the runner restarts the worker then it's using a closed channel00:12
ericsnowwallyworld: np :)00:12
ericsnowwallyworld: and I'm sorry you're stuck in meetings :/00:12
wallyworldericsnow: ah, good pickup. i now have 40 mins till next meeting :-)00:48
ericsnowwallyworld: yeah, I'm not aware of the precedent for dealing with that situation and simple solution isn't coming to mind01:13
ericsnowwallyworld: perhaps we should only close the channel when the worker's tomb is killed01:13
mupBug #1494542 opened: unit does not go to error state <juju-core:New> <https://launchpad.net/bugs/1494542>01:16
wallyworldericsnow: maybe, i need to look atthe code in detail, haven't had a chance yet01:19
ericsnowwallyworld: np, I've got to EOD so if you don't pick it up I will tomorrow01:20
=== natefinch-afk is now known as natefinch
natefinchwaigani: hey, merge my PR!  https://github.com/waigani/GoOracle/pull/1902:17
waiganinatefinch: yikes, I haven't looked at this in a while! thanks :)02:18
natefinchwaigani: :)  Figured as a coworker, I had the right to poke you, especially since it's just docs ;)02:18
waiganinatefinch: done02:20
natefinchwaigani: awesome :)02:20
natefinchI know how it is. I have a couple outstanding PRs on my projects I need to attend to.02:20
axwwallyworld: just managed to bootstrap :)  I manually added a public IP to machine-0, but it's not hard to do that in code03:27
wallyworldaxw: whoohoo03:27
wallyworldawesome03:27
axwwallyworld: I'll write up my feedback email now.03:27
wallyworldtyvm03:28
wallyworldbe gentle with them :-)03:28
axwwallyworld: :)03:28
natefinchgah, our inconsistent use of Id vs ID is sooo annoying03:38
axwwallyworld: sent a big wall of text. lunch time04:23
wallyworldaxw: np, ty, was just otp04:40
thumperwell this week has pretty much sucked05:29
thumperglad it's over05:29
thumpertime for wine05:29
* thumper hopes for better next week05:29
=== urulama__ is now known as urulama
frankbanTheMue: (not sure if message arrived) when you have time, could you please take a look at http://reviews.vapour.ws/r/2628/ ? note that this work is proposed for merging into a feature branch currently. thanks!07:36
TheMuefrankban: yep, will take a look07:38
frankbanTheMue: ty07:38
=== akhavr1 is now known as akhavr
TheMuefrankban: you've got a review08:05
frankbanTheMue: thanks!08:06
frobwaredimitern, TheMue: standup time09:03
dimiternfrobware, we're there09:04
TheMuefrankban: we're, retrospective and planning09:04
dimiternfrobware, ah, sorry - it's a different link today09:04
TheMueoops, frobware09:05
TheMuehttps://plus.google.com/hangouts/_/canonical.com/sapphire09:05
frobwareaha09:05
frankbanTheMue: could you also take a look at the followup branch in http://reviews.vapour.ws/r/2630/ (still proposed against the feature branch)?09:16
TheMuefrankban: currently in retrospective HO, but then, yes09:17
frankbanTheMue: ty!09:17
mupBug #1494661 opened: Old logs are not compressed or removed <juju-core:New> <https://launchpad.net/bugs/1494661>09:38
fwereadedimitern, reviewed http://reviews.vapour.ws/r/2593/ at last, you might have thoughts re some of my comments11:33
dimiternfwereade, sweet! thanks!11:35
perrito666morning all11:35
perrito666fwereade: could you re-look at http://reviews.vapour.ws/r/2592/11:37
perrito666pretty please?11:37
fwereadeperrito666, looking11:37
* perrito666 really wishes he wasn't freezing11:46
voidspacedimitern: frobware: TheMue: dooferlad: morning!12:10
TheMuevoidspace: heya, you missed a pretty long meeting today. ;)12:13
voidspaceTheMue: full team meeting?12:18
TheMuevoidspace: retro/planning12:18
voidspaceTheMue: ah! shame12:18
voidspaceTheMue: I should check the board12:18
voidspaceTheMue: it's just past 8am here, I still need coffee!12:18
TheMuevoidspace: no, too early for your time zone. you're still in the US?12:19
voidspaceTheMue: I'm back in Europe on Monday12:19
voidspaceTheMue: yep, still at Wayne's house12:20
voidspaceTheMue: he's now married and the big celebration is tomorrow12:20
TheMuevoidspace: relaxing after the wedding party :D12:20
TheMuevoidspace: oh, tomorrow, ic12:20
TheMuefrankban: you've got a review12:22
frankbanTheMue: ty!12:22
dimiternvoidspace, hey there :) welcome back!12:23
frankbanTheMue: great suggestion Errorf, I have been looking for something like that but did not find it for some reason12:26
TheMuefrankban: I would have called it Newf, so it's more easy to find. *bg*12:27
frankbanTheMue: yeah12:27
mupBug #1494726 opened: TestGetUsesCache different mime-type centos <centos> <ci> <test-failure> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1494726>12:44
mupBug #1494729 opened: Panic created by net/http.fileTransport.RoundTrip <ci> <panic> <test-failure> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1494729>12:44
frobwarevoidspace, hiya - let's catch up monday as I have a couple of meetings RSN12:47
frobwaredimitern, want to sync up?12:55
dimiternfrobware, I started to summarize my thoughts around the needed changes - how about I finish them and send you a mail with those?12:58
frobwaredimitern, sure12:58
voidspacefrobware: ok, no problem12:59
dimiternfrobware, cheers12:59
mattywfwereade, ping?13:01
fwereademattyw, pong13:01
mattywfwereade, do you have 10 minutes to receiving a whinge?13:02
fwereademattyw, certainly, just between reviews :)13:02
mupBug #1494734 opened: Panic in jujud/agent on ppc64el <juju-core:New> <https://launchpad.net/bugs/1494734>13:02
mupBug #1494734 changed: Panic in jujud/agent on ppc64el <juju-core:New> <https://launchpad.net/bugs/1494734>13:08
mupBug #1494734 opened: Panic in jujud/agent on ppc64el <juju-core:New> <https://launchpad.net/bugs/1494734>13:14
mupBug #1494743 opened: TestMachineAgentRunsCertificateUpdateWorkerForStateServer timeout <ci> <i386> <test-failure> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1494743>13:21
=== tvansteenburgh1 is now known as tvansteenburgh
frankbanTheMue: time for a quick third and last one along the same line? http://reviews.vapour.ws/r/2633/13:49
Odd_BlokeHello all.  I have a service comprised of three units (all on different machines).  If one of those machines disappears, should I expect to see one or both of cluster-{broken,departed} to be triggered on the other units?13:50
mupBug #1494749 opened: TestWorkerRetriesOnPublishError fails on wily <ci> <intermittent-failure> <lxc> <unit-tests> <wily> <juju-core:Triaged> <https://launchpad.net/bugs/1494749>13:51
mupBug #1494754 opened: TestActionsReceived failed on precise <ci> <intermittent-failure> <precise> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1494754>13:51
Odd_Bloke(tvansteenburgh: ^^^)13:51
tvansteenburghOdd_Bloke: yeah, i'm eagerly awaiting the answer :)13:52
pmatulisis this the only place where users can look in order to choose a tools version to upgrade to? https://streams.canonical.com/juju/tools/releases/13:56
ericsnowregarding #1494661, didn't we fix log rotation (including compressing/deleting) already?13:58
mupBug #1494661: Old logs are not compressed or removed <juju-core:New> <https://launchpad.net/bugs/1494661>13:58
bogdanteleagapmatulis: yes, those are the latest stable tools, there's also a devel folder with newer, but usually alpha or beta versions14:02
ericsnowfwereade: you have a few minutes (in a little while) to talk about how to fix #1493123?14:13
mupBug #1493123: Upgrade in progress reported, but panic happening behind scenes <landscape> <landscape-release-29> <upgrade-juju> <juju-core:In Progress by ericsnowcurrently>14:13
mup<juju-core 1.24:In Progress by ericsnowcurrently> <juju-core 1.25:In Progress by ericsnowcurrently> <https://launchpad.net/bugs/1493123>14:13
fwereadeericsnow, sure14:14
ericsnowfwereade: OTP, but I'll ping you soon :)14:14
ericsnowfwereade: you free?14:22
fwereadeericsnow, yeah14:23
mupBug #1494765 opened: TestWorkerRemovesDeadAddress fails on ppc64el <ci> <intermittent-failure> <ppc64el> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1494765>14:24
mupBug #1494774 opened: MetricSenderSuite fails on ppc64el panic <ci> <intermittent-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1494774>14:24
rogpeppemy juju is in a state where14:25
rogpeppe"juju bootstrap -e local" hangs forever14:25
rogpeppeafter "Bootstrapping Juju machine agent"14:25
rogpeppeanyone have an idea what might be going on?14:25
bogdanteleagatried --debug?14:26
rogpeppei can't even interrupt the bootstrap14:26
rogpeppeit's hung at "Interrupt signalled: waiting for bootstrap to exit"14:26
rogpeppebogdanteleaga: so i *would* try --debug if i could get it to stop14:27
bogdanteleagaC^Z and kill process? :)14:27
rogpeppeyeah, i think i'll sigquit it14:27
bogdanteleagamight have to clean up after it if you do that tho14:27
rogpeppebogdanteleaga: any idea what i might need to clean up?14:27
bogdanteleagaany machines/networks it created I'm thinking14:28
bogdanteleagaI usually just power off maas machines14:28
bogdanteleaganot sure about local14:28
rogpeppebogdanteleaga: lxc-ls shows one entry14:28
rogpeppejuju-trusty-lxc-template14:28
* rogpeppe runs lxc-destroy14:29
rogpeppebogdanteleaga: i've got an lxcbr0 network interface14:30
rogpeppebogdanteleaga: do you think i should remove that too?14:30
bogdanteleagarogpeppe, hmm, not sure, I'm really not familiar with lxc14:31
bogdanteleagarogpeppe, the only lxc machine I have seems to not create that14:31
pmatulisbogdanteleaga: alright thanks14:32
rogpeppeha, "destroy-environment -y local" still leaves me with an entry in environments/cache.yaml14:33
rogpeppewith an empty key14:33
bogdanteleagatry --force14:33
rogpeppebogdanteleaga: i did14:33
rogpeppebogdanteleaga: (sorry, i didn't mention that)14:33
* rogpeppe removes cache.yaml14:33
bogdanteleagarogpeppe, I never actually saw a cache.yaml before14:33
rogpeppebogdanteleaga: you only get it with the jes feature flag14:34
bogdanteleagarogpeppe, that makes sense :)14:34
katcoericsnow: natefinch: ready?14:36
natefinchyep14:36
rogpeppebogdanteleaga: for future reference: looking in ~/.juju/local/log/machine-0.log is dead useful :)14:40
bogdanteleagarogpeppe, I'll cherish the day I get to use local and not worry about boringly long deployment times14:41
rogpeppebogdanteleaga: :)14:42
rogpeppebogdanteleaga: filed https://bugs.launchpad.net/juju-core/+bug/149478714:46
mupBug #1494787: bootstrap cannot be interrupted if machine agent fails to start <juju-core:New> <https://launchpad.net/bugs/1494787>14:46
mupBug #1494782 opened: should *-broken *-departed hooks run when a unit goes AWOL? <juju-core:New> <https://launchpad.net/bugs/1494782>14:57
mupBug #1494787 opened: bootstrap cannot be interrupted if machine agent fails to start <juju-core:New> <https://launchpad.net/bugs/1494787>14:57
mupBug #1494774 changed: MetricSenderSuite fails on ppc64el panic <ci> <intermittent-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1494774>15:15
mupBug #1494798 opened: Juju fails to report it cannot create buckets <ci> <ec2-provider> <storage> <juju-core:Triaged> <https://launchpad.net/bugs/1494798>15:15
mupBug #1494798 changed: Juju fails to report it cannot create buckets <ci> <ec2-provider> <storage> <juju-core:Triaged> <https://launchpad.net/bugs/1494798>15:18
mupBug #1494774 opened: MetricSenderSuite fails on ppc64el panic <ci> <intermittent-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1494774>15:18
mupBug #1494774 changed: MetricSenderSuite fails on ppc64el panic <ci> <intermittent-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1494774>15:21
mupBug #1494798 opened: Juju fails to report it cannot create buckets <ci> <ec2-provider> <storage> <juju-core:Triaged> <https://launchpad.net/bugs/1494798>15:21
mupBug #1455625 opened: TestStateWatcherTwoEnvironments fails <ci> <test-failure> <wily> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1455625>15:27
mupBug #1455625 changed: TestStateWatcherTwoEnvironments fails <ci> <test-failure> <wily> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1455625>15:30
mupBug #1455625 opened: TestStateWatcherTwoEnvironments fails <ci> <test-failure> <wily> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1455625>15:39
katconatefinch: hey can you update bug 1486553 with the latest status?15:56
mupBug #1486553: i/o timeout errors can cause non-atomic service deploys <cisco> <landscape> <juju-core:Triaged> <juju-core 1.25:In Progress by natefinch> <https://launchpad.net/bugs/1486553>15:56
natefinchreview anyone for a critical fix?  katco, ericsnow, etc? http://reviews.vapour.ws/r/2636/16:09
natefinchbreaking for lunch16:09
=== natefinch is now known as natefinch-afk
ericsnownatefinch-afk: I'll take a look16:10
bdxhttps://bugs.launchpad.net/charms/+source/openstack-dashboard/+bug/149482916:35
mupBug #1494829: Support for custom panels <designate> <designate-dashboard> <django> <horizon> <murano> <murano-dashboard> <openstack> <openstack-dashboard (Juju Charms Collection):New> <https://launchpad.net/bugs/1494829>16:35
mupBug #1494831 opened: Windows instances on GCE will have the same hostname <juju-core:Incomplete> <https://launchpad.net/bugs/1494831>16:42
mupBug #1494831 changed: Windows instances on GCE will have the same hostname <juju-core:Incomplete> <https://launchpad.net/bugs/1494831>16:45
mupBug #1494831 opened: Windows instances on GCE will have the same hostname <juju-core:Incomplete> <https://launchpad.net/bugs/1494831>16:48
mupBug #1494848 opened: 1.24+ cannot upgrade in canonistack <canonistack> <openstack-provider> <streams> <upgrade-juju> <juju-core:Triaged> <https://launchpad.net/bugs/1494848>17:12
mupBug #1494848 changed: 1.24+ cannot upgrade in canonistack <canonistack> <openstack-provider> <streams> <upgrade-juju> <juju-core:Triaged> <https://launchpad.net/bugs/1494848>17:24
mupBug #1494848 opened: 1.24+ cannot upgrade in canonistack <canonistack> <openstack-provider> <streams> <upgrade-juju> <juju-core:Triaged> <https://launchpad.net/bugs/1494848>17:27
=== natefinch-afk is now known as natefinch
natefinchericsnow: lol @ comment about using a struct for the params... i have code doing exactly that on my machine, but getting this fix in first.17:39
ericsnownatefinch: np :)17:39
ericsnownatefinch: it's just less churn overall if you do it in this patch17:40
natefinchericsnow: yeah, but this patch needs to be in ASAP.  I was going to do it all together, but it turned out this fix was needed faster than we expected.17:40
ericsnownatefinch: k17:40
katconatefinch: +117:41
natefinchericsnow: making a test for it right now17:41
ericsnownatefinch: thanks17:41
natefinchkatco: gah, 1.25 is blocked.18:04
katconatefinch: hmm18:05
katcomgz: ping?18:07
mgzkatco: hey18:09
katcomgz: we'd like to land a fix for bug 148655318:09
mupBug #1486553: i/o timeout errors can cause non-atomic service deploys <cisco> <landscape> <juju-core:In Progress by natefinch> <juju-core 1.25:In Progress by natefinch> <https://launchpad.net/bugs/1486553>18:09
katcomgz: but master is blocked18:10
katcomgz: thoughts on jfdi?18:10
mgzyeah, please don't18:10
natefinchkatco: 1.2518:10
mgzlook at the history of OS-deployer job18:10
natefinchkatco: (I mean, master is also blocked, but the bug is for 1.25)18:10
katconatefinch: mgz: oops sorry, for 1.2518:10
mgzfine on 1.24 and feature branches18:10
mgzscrewed on 1.25 and master18:10
mgzit's already too hard to pin down cause because too much stuff was piled on18:11
katcomgz: this is a fairly hot bug18:11
natefinchkatco: if 1.25 is broken currently, getting my fix in won't help get it to customers18:11
mgzsure, but we can't release in the current state18:11
mgzso it's not like that fix on 1.25 will get anywhere18:11
natefinchmgz: I guess we're past the point of being able to revert whatever it is?18:12
mgznatefinch: master can be reverted back to some kind of sanity18:12
mupBug #1494864 opened: TestBlockChangeServiceUpdate fails on windows <blocker> <ci> <regression> <test-failure> <unit-tests> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1494864>18:12
mupBug #1494868 opened: TestAzureWindows fails on wily and centos <centos> <ci> <test-failure> <unit-tests> <wily> <juju-core:Triaged> <https://launchpad.net/bugs/1494868>18:12
katconatefinch: how hard would it be to get into 1.24?18:12
mupBug #1494870 opened: TestMeterStatusEvents fails on wily and vivid <ci> <race-condition> <test-failure> <unit-tests> <vivid> <wily> <juju-core:Triaged> <https://launchpad.net/bugs/1494870>18:12
mgzbut yeah, as no one is taking my suggestion on backing out broken changes we now have regressions without clear blame18:13
katcomgz: ty for the input... we won't land in 1.25 right now. natefinch, just learned this fix is needed in 1.24.6, so let's land there18:15
natefinchkatco: even better.18:15
natefinchmgz: http://cdn.meme.am/instances2/500x/1820980.jpg18:15
katcovery small review for a critical bug on 1.24.6: http://reviews.vapour.ws/r/2638/18:23
bogdanteleagamgz: are wily and centos tests running with another go version?18:23
mgzbogdanteleaga: wily uses go 1.518:24
mgzsinzui: what version of go is on centos?18:25
bogdanteleagabug 1494868 above is really interesting18:25
mupBug #1494868: TestAzureWindows fails on wily and centos <centos> <ci> <test-failure> <unit-tests> <wily> <juju-core:Triaged> <https://launchpad.net/bugs/1494868>18:25
bogdanteleagait should fail everywhere18:25
bogdanteleagabut it fails only on wily and centos18:25
bogdanteleagabecause the test doesn't get ran on other platforms18:25
mgzbogdanteleaga: that is interesting.18:27
sinzuimgz: bogdanteleaga looking. I thought the test log printed that for us18:27
mgzsinzui: I see the juju version but not the go version18:28
sinzuimgz: our python test runner doesn't do a go version like our bash version :(18:28
* sinzui visits the machine18:28
sinzuimgz: bogdanteleaga go version18:29
sinzuigo version go1.4.2 linux/amd6418:29
mgzbogdanteleaga: thae windows-public-clouds branch was retested and passed, which further persuades me it's not the cause of recent breakage18:29
mgzsinzui: ta!18:30
bogdanteleagahttp://reviews.vapour.ws/r/2640/18:31
katconatefinch: http://reviews.vapour.ws/r/2639/diff/# is the same as the one that was targetted to 1.25?18:32
bogdanteleagamgz: well, it can't be since you got the same failures on master18:32
bogdanteleagamgz: and, afaik that didn't get in master yet18:32
mgzbogdanteleaga: we got so many issues on master I was unpersuaded of anything18:32
bogdanteleaga:)18:32
voidspacefwereade: thanks for the review18:33
voidspacefwereade: I tried to make the changes without any changes to the external api - e.g. the allwatcher18:33
voidspacefwereade: where empty address was used to signal no address set yet18:33
voidspacefwereade: I think that's specifically been changed on master already though18:33
voidspacefwereade: so the same work on master looks better18:34
natefinchkatco: yep18:34
voidspacefwereade: a bunch of good suggestions though (especially the transaction testing)18:34
voidspacefwereade: I have left a couple of replies, working through the others18:34
katconatefinch: go for it18:34
katconatefinch: and i could use a review for: http://reviews.vapour.ws/r/2638/18:34
natefinchkatco: ok looking18:35
katcothat goes for anyone ^^ 22 line change18:35
katcocritical bug for 1.24.618:35
mgzbogdanteleaga: renderers.ToBase64 returns a string?18:36
bogdanteleagafwiw, you ought to get https://bugs.launchpad.net/juju-core/+bug/1493887 fixed on windows first18:36
mupBug #1493887: statusHistoryTestSuite teardown fails on windows <blocker> <ci> <regression> <test-failure> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1493887>18:36
bogdanteleagasince it might break other tests18:36
natefinchkatco: lgtm18:36
bogdanteleagaI had a mail about this kind of failure on the ml before18:36
katcocherylj: hey what's the status on bug 1494356 ?18:36
mgzbogdanteleaga: yeah, there's a bunch of things on master I'm afraid18:36
mupBug #1494356: OS-deployer job fails to complete <blocker> <ci> <regression> <juju-core:Triaged by cherylj> <juju-core 1.25:Triaged by cherylj> <https://launchpad.net/bugs/1494356>18:36
bogdanteleagamgz: it very well could return a string18:36
bogdanteleagamgz: I just wanted to use deepequals everywhere for consistency18:37
mgzI mean, does it? it's a function with a call value18:37
bogdanteleagamgz: now the tests runs on all platforms and it's good18:37
bogdanteleagamgz: yeah, think of it like a transformer18:37
mgzjust want to avoid the ugliness of a mismatch on []uint818:37
bogdanteleagamgz: that needs everything to move from jc.DeepEquals to str(x), gc.Equals, str(y)18:38
bogdanteleagamgz: because some functions in those suites give back strings and some give back byte arrays18:38
bogdanteleagamgz: can't really remember which do which right now18:38
mgz;_;18:39
mgzbogdanteleaga: lgtmed18:39
bogdanteleagamgz: wasn't the best idea in hindsight :)18:39
bogdanteleagamgz: 1.25 is blocked though, right?18:39
natefinchbogdanteleaga: what you need to do is write a jc.StringEquals that'll do the string conversion for you :)18:40
mgzkatco: I think she's hoping for more data on lxc specifics still, I'm going to rerun against 1.25 with that shortly18:40
katcomgz: ah ok18:40
mgzbogdanteleaga: yep18:40
bogdanteleaganatefinch: that sounds useful, yeah18:41
natefinchbogdanteleaga: it's 50% useful and 50% horrible.... since it produces a very squishy test that can pass when it really shouldn't.18:42
cheryljkatco: yeah, what mgz said18:42
cherylj:)18:42
katcocherylj: k ty :)18:42
bogdanteleaganatefinch: I'm actually wondering if contains would work if they're equals18:43
mgzcherylj: note that the test just passed on the windows-pulbic-clouds branch which is 1.25 as-of-a-few-revisinos-back18:43
* bogdanteleaga goes to the playground18:43
cheryljmgz: I'm wondering if the test is just taking a long time, as we've seen some of the containers come up in some of the test runs.18:44
mgzcherylj: that is certainly part of it.18:44
cheryljmgz: I'm running some manual testing in canonistack and it took over an hour to download the image to create the template container18:45
cheryljdon't know if it could be related or not18:45
bogdanteleaganatefinch: deepequals still doesn't test that they have the same type though18:45
mupBug #1494876 opened: TestFatalErrors fails on wily <ci> <test-failure> <unit-tests> <wily> <juju-core:Triaged> <https://launchpad.net/bugs/1494876>18:46
mgzbut compare the 1.24 runs. they're either done in 35-40 mins, or hit the *internal* deployer timeout18:46
mupBug #1494887 opened: uniterV1Suite.SetUpTest <ci> <test-failure> <unit-tests> <wily> <juju-core:Triaged> <https://launchpad.net/bugs/1494887>18:46
cheryljmgz: hmm, good point18:46
mgzthe master runs are *still deploying units* an hour in when our external job timeout hits18:46
cheryljouch18:47
mgzso like, at minimum it's a 50% perf regression due to either our box, the network, (but not as of today), or the code in master18:47
cheryljmgz: Is there any way to access the machines once the test completes?  I'm wondering if we need to examine the containers to see what's going on18:49
cheryljor are they immediately released?18:50
mgzcherylj: let me check the job, most of them have a flag we can set to not destroy-environment after18:50
mgzcherylj, sinzui: I am setting --keep-env on OS-deployer job18:53
sinzuimgz: I hope you remember to undo it before you sleep :)18:54
mgzalso setting failure-threshhold to 118:55
sinzuimgz: I've dont that. Once the job starts, you can restore the script., then wai 40 minutes for the job to get to your point of investifation18:55
mgzas this one ties up most of our maas we really can't be doing other things at the same time18:55
voidspacefwereade: hmmm... and yes, setting the preferred addresses on set rather than on read is better18:59
voidspacefwereade: only nuisance is we have two setters for addresses. Ah well, still better18:59
cheryljmgz: hopefully it won't take too long to see what's going on with the containers.19:04
mupBug #1494894 opened: TestWatchInterfaces fails on wily <ci> <test-failure> <unit-tests> <wily> <juju-core:Triaged> <https://launchpad.net/bugs/1494894>19:19
mgzkatco: can I persuade one of you to revert the last change on master before the weekend?19:23
mgzthe dep change broke like four things, I don't see a good reason to leave it in place19:23
katcomgz: sec meeting... was it cmars patch?19:27
cmarsmgz, commit hash please?19:28
natefinchkatco: I can pick that up ^^ if you want.  Pretty trivial... from Rogpeppe & frankban19:28
katconatefinch: yep +1... go for it19:28
mgzkatco, cmars: http://reviews.vapour.ws/r/2606/19:29
cmarsmgz, what tests fail? can I see a log?19:29
mgzbug 1494441 bug 1494864 two more unrelated windows test failures and who knows what else after the build succeeds19:30
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>19:30
mupBug #1494864: TestBlockChangeServiceUpdate fails on windows <blocker> <ci> <regression> <test-failure> <unit-tests> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1494864>19:30
cmarsmgz, ty19:30
natefinchcmars: can you rubber stamp the revert? http://reviews.vapour.ws/r/2641/19:31
natefinchit's just a PR created with the revert button in github19:31
cmarsnatefinch, i'm going to look at the test failures first19:31
mgzcmars: so, the ppc64 build failure is 'not your fault' but prevents us doing proper testing19:31
natefinchcmars: I've looked at the 1494441: ppc64el: cannot find package "encoding"  one19:32
mgzwe had a fix to ggcgo that for whatever reasons didn't get back into trusty-updates19:32
natefinchcmars: what he said ^  also, the windows one looks like a pretty standard "Someone doing file moves/deletes before they close the file" in windows19:34
perrito666mgz: still here?19:34
cmarsnatefinch, mgz done19:35
mgzperrito666: I am19:35
perrito666mgz: how much do you know about mong ca files and stuff?19:35
mgzcmars: I will file other bugs from the results we got, but can address and reland easily enough next week19:36
mgzperrito666: not much of the detail19:37
perrito666mmmpf, bad luck19:37
* perrito666 tries to setup mongo3 and it seems to want to authenticate with ssl certs19:37
perrito666aghh finally19:38
perrito666--sslWeakCertificateValidation19:38
perrito666and by weak they mean nil19:39
mgzperrito666: well, that sounds better than what I think we had before which is just a password-style key file19:40
mgzof some number of random bytes19:40
perrito666mgz: I am trying to get juju to run on a minimal mongo 319:40
perrito666we can implement certs later on19:40
perrito666but with that option it should be the same as we have now19:40
natefinchI really hate that JFDI requires __ JFDI__ because the underscores get hidden by markdown19:47
natefinchI screw it up every time19:47
natefinchWTF19:48
natefinchI guess having __JFDI__ in a previous comment is not good enough. sigh19:49
mupBug #1494912 opened: TestHookContextEnv fails on windows <blocker> <ci> <test-failure> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1494912>19:52
mgznatefinch: this isn't a jfdi, it's a fixes-149444119:52
natefinchmgz: it doesn't fix anything, it just backs out the change... I mean, I guess it sorta does, but I figured it might be better to leave the bug around for when the code actually gets fixed.19:55
perrito666mgz: since we are in it, can we have fixes be a bit more permissive?19:55
perrito666mgz: fixes does not remove the block, it just lets your merge pass19:56
perrito666I meant natefinch19:56
perrito666mgz: could we have it also take fix- fix_ and fixes_ ?19:56
mgzwe can still use the bug19:57
natefinchmgz: I guess I find the wording of "fixes" to be inaccurate in the case of just backing out a change... but maybe I'm being too pedantic.19:58
mgzthat bug is really about the ftb with gccgo, which backing out the change does address. I agree that that thinks can get complicated when using all the features of version control.19:59
mgzwell, this is fun.20:07
fwereadevoidspace, yeah, the two setters are a bit of a hassle20:13
katconatefinch: did your patch merge?20:19
mgzkatco: both seem to have.20:21
mupBug #1494913 opened: TestNoSpoolDirectory fails on windows <blocker> <ci> <test-failure> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1494913>20:22
mupBug #1494917 opened: TestEnvSetsPath fails on windows <blocker> <ci> <test-failure> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1494917>20:22
katcomgz: ty20:22
natefinchkatco: yep20:26
natefinchkatco: what do you think about making the rest of my changes for the add service stuff to 1.25 or master?  Or should I be trying to get the rest of it into 1.24 as well?20:32
natefinchgotta run for a while, will check in later20:40
=== natefinch is now known as natefinch-afk
katconatefinch: i'd say no20:40
natefinch-afkyeah, the other half is trickier, I'd prefer 1.25 or later20:40
mupBug #1494936 opened: imageSuite.TestDownloadEnvironmentPath <ci> <intermittent-failure> <panic> <unit-tests> <wily> <juju-core:Triaged> <https://launchpad.net/bugs/1494936>21:16
mupBug #1494938 opened: Panic DeploySuite.TestConfig on wily <ci> <intermittent-failure> <panic> <unit-tests> <wily> <juju-core:Triaged> <https://launchpad.net/bugs/1494938>21:16
mupBug #1494939 opened: Panic backupsSuite.TestAuthRequiresClientNotMachine on wily <ci> <intermittent-failure> <panic> <unit-tests> <wily> <juju-core:Triaged> <https://launchpad.net/bugs/1494939>21:16
mupBug #1494936 changed: imageSuite.TestDownloadEnvironmentPath <ci> <intermittent-failure> <panic> <unit-tests> <wily> <juju-core:Triaged> <https://launchpad.net/bugs/1494936>21:19
mupBug #1494938 changed: Panic DeploySuite.TestConfig on wily <ci> <intermittent-failure> <panic> <unit-tests> <wily> <juju-core:Triaged> <https://launchpad.net/bugs/1494938>21:19
mupBug #1494939 changed: Panic backupsSuite.TestAuthRequiresClientNotMachine on wily <ci> <intermittent-failure> <panic> <unit-tests> <wily> <juju-core:Triaged> <https://launchpad.net/bugs/1494939>21:19
mupBug #1494936 opened: imageSuite.TestDownloadEnvironmentPath <ci> <intermittent-failure> <panic> <unit-tests> <wily> <juju-core:Triaged> <https://launchpad.net/bugs/1494936>21:22
mupBug #1494938 opened: Panic DeploySuite.TestConfig on wily <ci> <intermittent-failure> <panic> <unit-tests> <wily> <juju-core:Triaged> <https://launchpad.net/bugs/1494938>21:22
mupBug #1494939 opened: Panic backupsSuite.TestAuthRequiresClientNotMachine on wily <ci> <intermittent-failure> <panic> <unit-tests> <wily> <juju-core:Triaged> <https://launchpad.net/bugs/1494939>21:22
mupBug # opened: 1494947, 1494948, 1494949, 149495121:31
mupBug # changed: 1494947, 1494948, 1494949, 149495121:34
mupBug # opened: 1494947, 1494948, 1494949, 149495121:37
mupBug # changed: 1494947, 1494948, 1494949, 149495121:43
mupBug # opened: 1494947, 1494948, 1494949, 149495121:46
benjif/quit21:54
ericsnowanyone still around that could give me a quick review?  http://reviews.vapour.ws/r/2644/22:06
katcoericsnow: tal22:16
katcoericsnow: so for now the channel never gets closed, but it doesn't matter b/c its lifecycle is the same as the process?22:18
katco*agent process22:18
ericsnowkatco: pretty much22:29
katcoericsnow: what is the harm in having a defer close?22:29
ericsnowkatco: also, william indicated that not closing the channel would be fine22:29
katcoericsnow: ah wait, that would close it as the function exited22:29
katcoericsnow: not as the workers died22:30
ericsnowkatco: yep :)22:30
katcoericsnow: +2, ship it. good work22:30
ericsnowkatco: thanks22:30
ericsnowblech, currently 7 blockers on master :(22:32
perrito666wtf happened22:33
perrito666hi btw22:33
perrito666:)22:33
katcoperrito666: o/22:35
katcoericsnow: wow22:35
katcoericsnow: i thought there was only 1 and nate had removed it22:35
mgzkatco: you got us back to our previous blockers :)22:36
katcomgz: face palm22:36
mgzwhich was why I was keen on the revert22:36
katcomgz: understood... ty for pushing us in the rigth direction22:36
mgztrying to unpick which were due to the dep update and which were due to maltese-falcon was causing me headaches22:37
katcofun fact: the rigth direction is an early Gaelic belief that an undiscovered direction existed. later, it was recoined as the "right" direction22:37
katcoor, alternatively, i just can't type.22:37
mgznow you've removed the dep update from the confusion22:38
katcogood to hear22:38

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