cheryljsinzui, katco, alexisb - here's the PR for reverting the rename of environments.yaml:  http://reviews.vapour.ws/r/3629/00:21
cheryljrb, not pr.  whatever :P00:22
thumpercherylj, sinzui: failure on machine-dep-engine appears to be bad-record-mac03:52
cheryljthumper: yeah, I saw that.03:53
cheryljIf other tests pass, I'd say merge away03:53
cheryljlooks like the maas tests (and a few others) are still running / queued03:54
thumperyeah... not final yet03:57
=== urulama__ is now known as urulama
voidspacedimitern: ping09:12
voidspacedimitern: do you know the root cause of the trusty deploy CI failure we're seeing09:13
voidspacedimitern: "dpkg-deb: error: --extract needs a target directory"09:13
voidspacedimitern: it looks like a build failure09:13
voidspacemgz: ping09:14
voidspacewe have two failures the same on xenial09:15
voidspacea lxd-deploy and aws-deploy-trusty09:16
dimiternvoidspace, hmm let me have a look09:17
voidspacedimitern: http://reports.vapour.ws/releases/353309:17
dimiternvoidspace, mgz, it looks like it failed to build xenial deb package, but the job still succeeded: http://data.vapour.ws/juju-ci/products/version-3533/build-binary-xenial-amd64/build-130/consoleText09:20
voidspacedebian/rules:26: recipe for target 'binary' failed09:22
voidspacedh_install: juju-core missing files: src/github.com/juju/juju/cmd/plugins/juju-backup/juju-backup09:22
voidspacedimitern: this doesn't fail for master though it seems09:22
voidspacecmd/plugins/juju-backup is also missing on master09:24
voidspacemaybe a CI rule has been updated for master09:24
dimiternvoidspace, it seems the debian/rules for master and other branches are different09:25
dimiternwhich tells me they fixed it for master, but apparently each branch uses its own rules09:26
voidspacedimitern: ok, cool09:29
voidspacedimitern: so it's their fault :-)09:29
voidspacemgz: ^^^09:29
voidspacedimitern: where did you check the debian rules?09:46
dimiternvoidspace, in the log - check for error 209:47
dimiternat the end of that "successful" job log I pasted earlier09:47
voidspacedimitern: thanks09:48
jamhey guys, sorry I missed the standup. I am around, just spaced the actual event.10:21
jamAnyone remember who setup reviewboard? I'm noticing that Tycho has submitted stuff to Github but it doesn't seem to end up in RB as well.10:21
voidspacejam: it was ericsnow who setup reviewboard10:22
voidspacewe're still talking FWIW10:22
perrito666Jam: i believe review board requires for the user to do the link with github account to work12:55
perrito666Btw did you see axw email regarding xdg?12:55
frobwaredimitern, voidspace, dooferlad: please could you take a look at my (mostly complete) bridge script that allows an explicit interface to be specified: http://reviews.vapour.ws/r/3630/13:22
frobwaredimitern, voidspace, dooferlad: if we're happy with the approach I'll take maas-spaces script to 1.25 and test accordingly.13:23
dimiternfrobware, sure, looking13:27
frobwaredimitern, what's the right answer for this? http://pastebin.ubuntu.com/14671696/13:33
dimiternfrobware, reviewed13:42
dimiternfrobware, re the paste - the only difference is no auto eth1 in initial, right?13:42
dimiternfrobware, a guess the answer should be "if it worked before the script shouldn't break it" :)13:43
frobwaredimitern, correct.13:44
dimiterns/script/script, running it/13:44
frobwaredimitern, I think we should mimic what we got, hence I just pushed an additional test to cover this case.13:44
dimiternfrobware, +113:45
frobwaredimitern, I haven't see that in the wild, but some time ago I put a check in to only add the 'auto' stanza if there was one before. That all happened in the _bridge() functions but in the main loop we skip over interfaces and this now gets missed, hence the additional test.13:46
frobwaredimitern, bridge-prefix is a default so it will always have a value even if bridge-name && interface-to-bridge are specified.13:48
dimiternfrobware, right - the more cases we cover in tests, the better I think13:48
dimiternfrobware, ah, well I missed that13:48
frobwaredimitern, yeah, the new functionality is a little at odds with the existing behaviour.13:48
dimiternfrobware, feel free to ignore the second issue then :)13:48
dimiternwow go 1.6b2 got smarter error messages :)13:56
dimitern../../state/watcher.go:2395: doc.MachineId undefined (type networkInterfaceDoc has no field or method MachineId, but does have MachineID)13:56
frobware 13:58
frobwarevoidspace, ping13:58
perrito666mgz: ping13:59
voidspacefrobware: is maas meeting on?14:03
dooferladfrobware, dimitern, voidspace: https://plus.google.com/hangouts/_/canonical.com/maas-juju-net14:03
voidspacedooferlad: just grabbing coffee14:03
voidspacebe there in 2mins14:03
perrito666does anyone know if we have specs to add relations to tabular format?14:24
voidspace destroy-environment --force is gone and destroy-controller has no force option but just hangs... :-(14:44
=== coreycb` is now known as coreycb
voidspacemgz: sinzui: ping14:45
sinzuihi voidspace14:45
voidspacesinzui: hey, hi14:45
voidspacesinzui: maas-spaces CI jobs are failing the xenial tests for us because they're looking for juju-backups14:46
voidspacesinzui: and it looks like this is configured in debian rules per CI task14:46
voidspacesinzui: as the same doesn't happen on master14:46
sinzuivoidspace: when you need to use the force in that situation, use kill-controller, (a safe force)14:46
voidspacesinzui: ah, thanks14:46
sinzuivoidspace: I fixed packaging last Friday to not look for a plugin14:47
voidspacesinzui: that worked14:47
sinzuivoidspace: but lt me see if xenial has a different rule14:47
voidspacesinzui: we have a fail on monday: http://reports.vapour.ws/releases/353314:48
voidspacesinzui: aws-deploy-trusty...xenial and lxd-deploy-xenial both failed for that reason14:48
sinzuivoidspace: the lxd-deploy-xenial issue was a temporary network failure14:49
voidspaceah, my apologies then14:50
voidspaceI'm fairly sure about the other one :-)14:50
sinzuivoidspace: we can see next test of the branch did have a good network http://reports.vapour.ws/releases/354214:52
voidspacesinzui: ah, awesome - I hadn't seen that14:52
voidspacesinzui: appreciated14:52
voidspacestill cursed though14:52
voidspacefrobware: dimitern: dooferlad: new CI run for maas-spaces http://reports.vapour.ws/releases/354214:53
voidspacefrobware: dimitern: dooferlad: those tests that failed now pass (rules fixed), but we have a wily unit test failure14:54
voidspaceI'm running wily and I don't think that test fails for me14:54
voidspacefrobware: dimitern: dooferlad: http://reports.vapour.ws/releases/3542/job/run-unit-tests-wily-amd64/attempt/121014:54
dimiternvoidspace, that looks like flakiness14:57
dimiternvoidspace, hmm maybe not - I can see it here on wily14:59
voidspacedimitern: cool, we'll see in the next test run then14:59
voidspaceit's running for me14:59
voidspacedimitern: so with my code that blocks logins until space discovery is complete15:00
voidspacedimitern: bootstrap completes - but shows that error15:00
voidspacedimitern: so bootstrap doesn't wait, it just appears to error out15:00
voidspaceso more work needed15:00
voidspacefrobware: ^^15:00
voidspacedimitern: that test passes for me on wily15:00
voidspacehmm, I may not be up to date though15:00
voidspacedimitern: right, I've pulled in the merge from master now15:01
voidspaceI wonder if that is the cause15:01
mupBug #1526072 changed: Juju-deployer 0.6.0 and juju-core 1.25 - Build doesn't time out and keeps running until aborted <oil> <juju-core:New> <juju-deployer:New> <https://launchpad.net/bugs/1526072>15:13
dimiternvoidspace, I've run cmd/jujud/agent tests a few times - it fails some times, but no more than usual15:13
voidspacedimitern: right, passes for me every time so far15:17
alexisbI am seeing random failures while running test locally due to mgo not cleaning up (on several branches)15:23
alexisbis there something I need to do locally to make sure things are getting cleaned up?15:23
perrito666Nope, the errors you see might be the cleanup errors after a panic from something else15:24
perrito666Tmp tends to fill out with mgo stuff though so you might want to flush that15:24
voidspacealexisb: there really shouldn't be!15:24
voidspaceI gotta go pick up the daughter from school, sorry15:24
alexisbok, just seems test on master have gotten really flaky15:25
alexisbaround cmd/jujud15:25
perrito666Alexisb which are failing?15:26
alexisbagent and unit15:26
alexisbfails consistently15:27
perrito666I did stumble upon agent failing lately15:27
dimiternalexisb, try GOMAXPROC=1 go test -check.v github.com/juju/juju/cmd/jujud/agent/... to see if it helps15:29
natefinchGOMAXPROCS is not the cause.  I run with GOMAXPROCS=8 all the time, and don't have many consistent failures.15:38
natefinchalexisb: what version of Go?  (run go version)15:40
dimiternvoidspace, dooferlad, frobware, care to review a -3080 line diff :) ? http://reviews.vapour.ws/r/3631/15:40
dimiternfrobware, voidspace, dooferlad, any of you still there?16:23
frobwaredimitern, otp16:25
dimiternjust pestering for a review btw16:25
dooferladdimitern: can take a look in a moment16:25
dimiterndooferlad, cheers16:26
frobwaredimitern, one question I have is the "risk" of landing your change in light of merging back to master. just curious...16:32
frobwaredimitern, I don't want to derail the opportunity to be back in master.16:32
alexisbnatefinch, I am running 1.516:33
frobwaredimitern, ooh. Now that I've actually looked at your PR it's all deletes.. \o/16:33
dimiternfrobware, yeah - for a change :)16:34
dooferladdimitern: +1 delete all the old things!16:37
frobwaredimitern, so my question still stands though: do you see any risk for CI tests, stopping a merge into master. It's likely that master may be blocked for a few days so that we can land.16:37
dimiternfrobware, I'm not sure about that PR causing CI tests to fail - not that I know of, and since it's dropping code which was not running for quite a while, I think we're safe16:39
frobwaredimitern, k16:39
frobwaredimitern, just trying to avoid another 24 cycle on getting maas-spaces into master16:40
natefinchalexisb: 1.4 is more reliable.... 1.5 has some known problems with juju still, last I heard16:41
frobwarealexisb, I have pre-built deb of go 1.4.3 if it helps. - it installs into /usr/local/go1.4.316:43
alexisbnatefinch, perrito666 this is the failure I am seeing consistently with latest master and golang 1.5:16:56
natefinchalexisb: yeah, pretty sure I was seeing the sockets thing with go 1.5 too16:57
perrito666yup, that is go 1.516:57
perrito666I have smae issues only in my go1.5 machine16:57
natefinchsort of :/16:58
alexisbany idea if it is addressed with 1.5.2+?16:58
natefinchalexisb: I don't think it's a Go bug, I think it's a juju bug, but I haven't looked super deep into it.16:58
alexisbnatefinch, ok16:58
cmarsashipika, were you seeing that sockets error as well? ^^ (https://pastebin.canonical.com/148393/)17:02
ashipikacmars: yes, i was17:03
ashipikacmars: in cmd/jujud/agent package17:03
ashipikacmars: and golang 1.5.317:04
perrito666how would you call both ends of a relation ?17:05
perrito666I am trying to add relations to tabular status and finding this problem17:06
ashipikacmars, alexisb: https://pastebin.canonical.com/148394/17:08
alexisbashipika, that is the same failure I am seeing17:10
alexisbtrying with go 1.4 now just to see if it is different17:10
natefinchericsnow: is your branch pushed in a good state for me to rebase?  I just got my branch all building, tests passing, etc.17:15
ericsnownatefinch: working on it17:15
ericsnownatefinch: should be good now17:21
natefinchericsnow: cool17:25
alexisbso it looks like go 1.4 is allowing the agent tests to pass but I am still seeing failures on master for the status test17:46
alexisbanyone else seeing failures on master for the status tests?17:46
mupBug #1538241 opened: 2.0-alpha2 stabilization <blocker> <juju-core:Triaged> <https://launchpad.net/bugs/1538241>18:13
perrito666natefinch: ?18:52
natefinchmachine was frozen when I came back and now its doing that "running in low graphics mode" crap18:53
perrito666natefinch: something is very wrong with some part of your computer18:53
perrito666did you ever replace the battery?18:53
natefinchyes I did18:53
natefinchbad when I can't even get to a command prompt18:57
natefinchahh Ctrl alt f1 works at least18:59
katcoericsnow: natefinch: finally finished revising the user-stories. i posted comments in the doc, but i'd like to review the diff with you two after i do lunch19:00
ericsnowkatco: k19:00
natefinchkatco - hopefully I can figure out my laptop problems before then19:01
katconatefinch: if not, do you have any other machine/phone you could attend on? i need you there19:01
katconatefinch: also, is this going to affect your ability to finish your card?19:02
natefinchI can attend on my tablet if needed.  yes it'll screw up getting the card done, but I'm hopeful I can fix it19:04
katconatefinch: k, keep me posted please.19:04
* katco lunches19:04
natefinchhmmm less hopeful now19:06
perrito666natefinch: need a hand?19:09
natefinchperrito666 yes19:11
perrito666natefinch: lets privmsg19:11
frobwarecherylj, ping; I'm around for 30 mins. anything I can do or help with regard to maas-spaces CI builds... ?19:17
natefinch_it would be really nice if linux would notice that all possible video drivers have been blacklisted and give me some kind of option to de-blacklist one of them19:38
natefinch_perrito666: thanks for the help... I figured it out.  I foolishly tried to enable the nvidia driver, but it evidently didn't actualy take until I rebooted after ubuntu froze... but when it did that, it blacklisted the nouveau driver...19:40
=== natefinch_ is now known as natefinch
perrito666but why would the nvidia kernel fail?19:41
natefinchperrito666: because I'm special like that19:41
perrito666dont worry, this is the year of linux on the desktop :p19:43
cheryljfrobware: I haven't looked at any of the failures, do you guys need me to?19:49
cherylj(sorry, was out for a walk before the rain starts)19:49
perrito666ok, something weird just happened20:27
perrito666I ran a whole test suite and didnt got spammed by mongo20:27
=== urulama is now known as urulama__
katconatefinch: meeting time20:34
natefinchkatco: oops, sorry, coming20:36
natefinchericsnow: did you say you had a charm that utilized resource-get?21:14
ericsnownatefinch: yeah, yours :)21:14
ericsnownatefinch: check it out in my branch in test-charms/.../starsay21:15
natefinchericsnow: ahh, I see it.  linux's default directory listing order always messes me up21:16
perrito666yeah, yeah, blame the OS21:18
natefinchperrito666: it's not my fault they decided to go top to bottom then left to right, rather than left to right, top to bottom21:19
mupBug #1538303 opened: 1.25.0: bootstrap failure - WARNING discarding API open error: EOF <oil> <juju-core:New> <https://launchpad.net/bugs/1538303>21:47
mupBug #1538303 changed: 1.25.0: bootstrap failure - WARNING discarding API open error: EOF <oil> <juju-core:New> <https://launchpad.net/bugs/1538303>21:50
mupBug #1538303 opened: 1.25.0: bootstrap failure - WARNING discarding API open error: EOF <oil> <juju-core:New> <https://launchpad.net/bugs/1538303>21:56
natefinchkatco, ericsnow: trying to debug why the unit resources aren't getting returned when I call show-service-resources.  I'm not sure resource-get is working correctly.21:59
mupBug #1538303 changed: 1.25.0: bootstrap failure - WARNING discarding API open error: EOF <oil> <juju-core:New> <https://launchpad.net/bugs/1538303>21:59
natefinchkatco, ericsnow: but I have to run for a while for dinner.21:59
ericsnownatefinch: k21:59
=== natefinch is now known as natefinch-afk
mupBug #1538303 opened: 1.25.0: bootstrap failure - WARNING discarding API open error: EOF <oil> <juju-core:New> <https://launchpad.net/bugs/1538303>22:02
ericsnowkatco: FYI, I have 6 patches up on RB now for the resource-get stuff22:43
katcoericsnow: awesome! in a meeting, i'll try and review tonight22:45
ericsnowkatco: note that tests bloat the line count substantially on a couple of those patches :)22:45
katcoericsnow: lol22:47
ericsnowkatco: I'm going to land them all in 1 PR once they all pass review22:47
katcoericsnow: that's clever. good idea22:48
ericsnowkatco: yeah, rbt post --parent <parent> was my friend here22:48
ericsnowkatco: so we'll revisit our iteration backlog after standup tomorrow?23:30
katcoericsnow: yes23:31
ericsnowkatco: sounds good23:31
katcoericsnow: sorry not sure i can get to the reviews tonight. need to start dinner and the family gets home soon23:31
ericsnowkatco: np23:31
ericsnowkatco: you wrote a decent chunk of it :)23:32
wallyworldperrito666: we will end standup, can't hear you23:41
perrito666wallyworld: yes, apparently my 3g network sucks at upload23:42
wallyworldperrito666: mongo3 will be next week's focus23:42
wallyworldafter we get the next alpha out23:42
perrito666wallyworld: my question was, regarding master23:42
perrito666my last branch, merged with master, when running the test suite23:42
perrito666it doesnt spam syslog23:43
perrito666that is new23:43
wallyworldperrito666: rsyslog is removed from juju core, you talking about mongo syslog spam?23:43
perrito666wallyworld: that is a problem from mongo not syslog23:44
perrito666it was at least :p23:44
perrito666you know, when running the full suite, there was a spam to all the terminals at one point23:44
wallyworldsure, but what i meant was, there will be no juju core syslog spam now23:44
perrito666I assumed that spam was being done by mongo, not juju23:45
wallyworldi thought it was core, but not sure now. anyway, mongo2 still being used for now23:45
perrito666wallyworld: k23:46
perrito666bbl, ill go try to resurrect internet23:46

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