/srv/irclogs.ubuntu.com/2015/03/18/#juju-dev.txt

thumperfark00:00
thumperI thought this was a small branch00:00
thumper$ git diff master | wc -l00:00
thumper97300:00
thumper 15 files changed, 467 insertions(+), 174 deletions(-)00:00
thumperhmm... menno is reviewer00:00
thumperno worries then00:00
* thumper goes to write more tests :)00:01
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
=== kadams54 is now known as kadams54-away
menn0thumper: screw you hippie :)00:39
* thumper bows00:40
thumperoh fuck00:41
thumperhmm...00:41
* thumper found an interesting bug^Wfeature00:42
thumperFINE01:01
thumperIF THAT IS THE WAY IT'S GOING TO BE...01:01
* thumper beats the code into submission01:01
jw4fwereade: if you get a chance in the morning could you review http://reviews.vapour.ws/r/1181/ ?01:19
jw4fwereade: I've updated with good feedback from perrito666 and dimitern01:20
thumpermenn0: got a few minutes to discuss a testing approach?01:34
* thumper grumbles01:43
thumperdavecheney: can I pass around an unbound method as a func to call on a target?01:44
* thumper recalls the following01:46
thumpertype foo struct {}01:46
thumperfunc (f *foo) method(param string) error {...}01:47
thumperfoo.method -> func (*foo, string) error01:47
thumper...01:47
thumperthat'll work01:47
menn0thumper: back now. standup hangout?01:48
thumperyea01:48
mupBug #1433384 was opened: utopic unit-test failure: TrackerSuite.TestWaitMinionBecomeMinion <ci> <i386> <regression> <test-failure> <utopic> <juju-core:Triaged> <https://launchpad.net/bugs/1433384>01:54
mupBug #1433384 changed: utopic unit-test failure: TrackerSuite.TestWaitMinionBecomeMinion <ci> <i386> <regression> <test-failure> <utopic> <juju-core:Triaged> <https://launchpad.net/bugs/1433384>02:07
mupBug #1433384 was opened: utopic unit-test failure: TrackerSuite.TestWaitMinionBecomeMinion <ci> <i386> <regression> <test-failure> <utopic> <juju-core:Triaged> <https://launchpad.net/bugs/1433384>02:13
thumpermenn0: what do you think about having the function api.OpenWithLoginV1 exported publicly?02:17
thumpermenn0: that way we can call it from the apiserver package02:17
menn0thumper: it's a little ugly but it doesn't bug me that much02:19
* thumper nods02:19
menn0thumper: perhaps it should be OpenWithVersion02:19
thumperbut that implies it takes an arg02:20
thumperbut it doesn't02:20
menn0thumper: would that make sense? then there'd be just one call to let people get at any version.02:20
thumperhmm...02:21
thumperperhaps02:21
menn0thumper: but could it take an arg02:21
menn0?02:21
thumperyes02:21
thumperwe could switch on the version02:21
thumperand error on unknown02:21
menn0thumper: why do you really need to export it from apiserver?02:21
thumperit is an api client function right now02:21
thumperand I want to use it in the apiserver package02:22
* thumper hunts for some books of equal height02:22
menn0thumper: right I see.02:22
* thumper is trying standing up02:22
thumperBeginning GIMP is the same thickness as Generative Programming02:23
* thumper is winning02:23
menn0:)02:23
thumperhmm... that's better02:23
thumperkeyboard was a little low before02:23
menn0thumper: just thought some more about it02:24
thumperyus...02:24
menn0thumper: and it seems ok02:24
thumperwhich bit?02:25
menn0thumper: esp if there's a docstring saying that it's mainly for testing02:25
thumperexporting one that takes a version02:25
* thumper nods02:25
thumperwill do02:25
menn0thumper: either is ok02:25
thumperand I'll have it take a version number02:25
thumperI think it is a little more flexible02:25
menn0thumper: but i prefer the version taking form02:25
thumperack02:25
* thumper takes a deep breath and ignores a little mess02:26
* thumper makes a note to clean it up next02:26
thumpermenn0: I'm not sure I'm going to get all this done before 6 today02:30
thumpermenn0: as I have a parent-teacher interview at 402:30
thumperand a class at 502:30
thumperbut I'll finish it off tongiht02:30
thumpermenn0: I don't expect you to review it today (maybe tomorrow) :)02:31
menn0thumper: np02:32
axwwallyworld: http://reviews.vapour.ws/r/1193/03:48
wallyworldok03:48
menn0anyone able to review this? http://reviews.vapour.ws/r/1192/03:49
menn0it's a fix for a problem I introduced that is preventing compilation on i38603:50
wallyworldaxw: i've done the go-amz mods ti support volumes, writing tests. had to update v4-unstable branch with latest v3 changes, conflicts due to stupid paths in imports. that shits me no end with Go03:50
wallyworldmenn0: looking03:50
thumpermenn0: class is at 6 not 503:50
thumperso I'm about to push this branch up03:50
menn0thumper: ok, bring it on03:50
thumper 20 files changed, 588 insertions(+), 192 deletions(-)03:51
* menn0 warms up his review issue fingers03:51
wallyworldmenn0: i just left a suggestion, not that important03:54
menn0wallyworld: good idea. i'll do that.03:54
thumperhmm...03:57
thumperwhy is reviewboard not picking that up03:57
thumpermenn0: https://github.com/juju/juju/pull/186803:57
menn0thumper: cool. i'll do that next.03:58
menn0looks like CI is blocked at the moment04:06
menn0bug 143338404:06
mupBug #1433384: utopic unit-test failure: TrackerSuite.TestWaitMinionBecomeMinion <ci> <i386> <regression> <test-failure> <utopic> <juju-core:Triaged> <https://launchpad.net/bugs/1433384>04:06
menn0thumper: your PR didn't make it to RB?04:07
* thumper shrugs04:08
thumperNFI04:08
menn0thumper: i'll review on GH04:10
thumperthis standing desk thing has my shoulders aching04:13
thumperless hunching and more hanging I guess04:13
rick_h_thumper: time to go to walking desk :)04:19
ericsnowthumper: FYI, that RB problem is a bug in my hook code where it cannot handle unicode properly (yay 7 year old Python version)04:20
ericsnowthumper: from time to time Github sends unicode in the request (or we have some in our code somewhere)04:20
ericsnowthumper: once the vivid stuff settles down I'm planning on fixing it04:21
wallyworldaxw: reviewed, sorry about delay, pool man was here04:29
axwwallyworld: nps, thanks04:29
thumperericsnow: ah... I was wondering what it was04:34
ericsnowthumper: yeah, it's the most common reason why the hook fails04:35
thumperok, handy to know04:35
thumperI'm going to head off to my boxing class now04:35
thumpertime to hit things hard04:35
menn0thumper: review done04:35
ericsnowthumper: the other is when a branch get's rebased against an incompatible base revision to the original04:35
thumpermenn0: awesome thanks04:35
thumpermenn0: I was wondering about the restricted root ordering04:35
thumperit seemed weird to do work that you were going to throw away04:35
thumperbut I'll look for the method first04:36
thumperfor consistency04:36
thumperwith the other methods04:36
ericsnowmenn0: thanks for pointing out filepath.EvalSymlinks04:36
ericsnowmenn0: I've updated the patch04:36
menn0thumper: yeah it does looks weird but I did put some thought into it for upgradingRoot04:36
thumperlaters peeps04:36
thumpermenn0: ack, will address tomorrow04:36
menn0ericsnow: no problems04:36
ericsnowthumper: o/04:36
menn0ericsnow: i've got to finish up in a sec so i might not be able to get back to your PR until tomorrow04:37
ericsnowmenn0: no worries04:37
ericsnowmenn0: thanks for the reviews04:38
ericsnowmenn0: we kept you busy today04:38
ericsnowmenn0: I'll probably have someone else wrap up the review so I that we can maybe release 1.23b1 tomorrow04:39
jw4menn0: thanks for the review, and the kind words :)04:39
menn0ericsnow: np04:40
menn0jw4: np04:40
menn0ericsnow: i just managed to sneak another review in04:44
menn0ericsnow: one problem, but otherwise ship it04:44
ericsnow\o/04:44
ericsnowmenn0: a pity review :)04:44
wwitzel3ericsnow: what are you still doing here?04:58
ericsnowwwitzel3: just checking on reviews before going to bed :)05:07
axwwallyworld: I've proposed another couple of branches. I'll now look at the last bits required to populate filesystem info for filesystems-on-volumes06:14
axwcan't land anything atm, as trunk is blocked06:14
wallyworldaxw: ok, i'm still plowing through writing tests for the go-amz work, have to go to soccer soon, may look after i get back. i expect tmorrow we'll have EBS volume source working06:17
axwwallyworld: awesome :)06:18
wallyworldaxw: oh, and that will include attach, detach06:18
axwgreat06:18
axwwallyworld: I haven't removed VolumeParams.Attachment yet, will defer that for now06:18
axwbut it's still necessary to have separate attach/detach anyway06:19
wallyworldaxw: sure, np, yep06:19
wallyworldand it's not much extra work to do it up front06:19
dimiternwallyworld, hey there, do you know if thumper's on leave?06:35
wallyworlddimitern: he was here before, but it's past his EOD now06:48
dimiternwallyworld, yeah, I was wondering about that i386 issue, but I've seen menn0 proposed a fix for it.. and now we have another blocker06:49
wallyworldi saw the i386 fix (reviewed it) but hadn't seen the other blocker06:49
dimitern#1433384 - some leadership fallout it seems06:51
mupBug #1433384: utopic unit-test failure: TrackerSuite.TestWaitMinionBecomeMinion <ci> <i386> <regression> <test-failure> <utopic> <juju-core:Triaged> <https://launchpad.net/bugs/1433384>06:51
=== urulama|afk is now known as urulama
dimiternfwereade, hey08:36
fwereadedimitern, heyhey08:37
dimiternfwereade, I wonder if you can clarify the logic around worker/leadership/tracker_test.go - the durations chosen08:37
dimiternfwereade, seems like refreshes() picks a halfRefreshes in the order or a few nanoseconds, which leads to frequent failures in TestWaitMinionBecomeMinion08:38
dimiternfwereade, that's related to the current blocker for 1.23 - bug 143338408:39
mupBug #1433384: utopic unit-test failure: TrackerSuite.TestWaitMinionBecomeMinion <ci> <i386> <regression> <test-failure> <utopic> <juju-core:Triaged> <https://launchpad.net/bugs/1433384>08:39
fwereadedimitern, hmm, did I screw up the logic? it ought to always pick (2n+1)/2 * coretesting.ShortWait for integer N08:40
dimiternfwereade, hmm so that looks like it needs to yield a duration around 1.5 - 2.5 x shortWait08:42
fwereadedimitern, yeah, it shouldn't ever return anything less than half shortWait08:42
fwereadedimitern, and looking at the code I can't immediately see how it's not doing that08:43
dimiternfwereade, depending on N ofc; the trouble is if you run the worker/leadership tests a few times - that same test (and only it so far I can see) fails - it happens to me about 50% of the time08:43
dimiternfwereade, hmm, actually it's a lot less than 50%08:45
dimiternfwereade, can you try running this on 1.23 in worker/leadership?: time go test -c && for i in `seq 50`; do ./leadership.test & sleep 0.01; done08:45
fwereadedimitern, yeah, it looks like I *can*induce failures, but I'm not seeing the one you mentioned above08:46
dimiternfwereade, but is the ultimate failure the same - got unexpected readiness: true ?08:47
mattywmorning all08:47
dimiternmattyw, o/08:47
fwereadedimitern, afraid not -- I'm seeing occasional failures to unblock the release goroutine in TestFailGainLeadership08:47
fwereademattyw, o/08:48
fwereadedimitern, and they're not guaranteed to trigger, whether running with seq 50 or seq 50008:49
dimiternfwereade, :) ok, there goes my one clue of the cause of the failure08:50
dimiternfwereade, I'll experiment on i386 to see if it makes a difference08:51
fwereadedimitern, hmm, seq 5000 seems to be stressing it a bit more, I managed to get 21 failures -- but *all* of them are in unblockRelease :/08:55
dimiternfwereade, are you using go 1.2.1 from the archive?08:55
fwereadedimitern, hmm, looks like I'm on 1.2 actually08:56
fwereadedimitern, (I think the unblockRelease *is* an issue actually -- we ought to have a generous timeout there instead of the default: case)08:57
dimiternfwereade, right, sounds fair08:57
fwereadedimitern, yeah, with coretesting.LongWait in unblockRelease I can do seq 5000 without failures09:00
dimiternfwereade, nice! well, if I have success with that other test on i386 I can propose a fix for both09:04
fwereadedimitern, cool, thanks09:08
dimiternfwereade, it gets weirder.. on a i386 machine even with seq 5000 I couldn't reproduce the TestWaitMinionBecomeMinion failure09:32
fwereadedimitern, blargh09:33
dimiternfwereade, I had ~25 failures and all of them related to unblockRelease09:33
* fwereade out, laura's school, bbs09:55
dooferladdimitern, voidspace, TheMue: hangout?10:02
voidspacedooferlad: yes10:02
dimiterndooferlad, sorry, omw10:02
natefinchI need to be able to alias juju destroy-enviroment to juju destroy-environment10:41
natefinch...or learn to type/spell10:41
mattywnatefinch, juju burn-more-fossil-fuels?11:27
mattywnatefinch, would you mind taking another look at http://reviews.vapour.ws/r/1005/? I'm going to fix the test up - but I'll do it in a follow up11:36
mupBug #1433566 was opened: Precise unit test failure discoverySuite.TestDiscoverInitSystemScript  <ci> <precise> <regression> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1433566>12:29
voidspacevirt-manager changes the owner of iso images you use to create kvm images from!12:36
dimiternvoidspace, yeah, because they're in added to the libvirt storage pool12:37
voidspacedimitern: the iso image?12:37
voidspacethat seems unfriendly12:37
dimiternvoidspace, indeed12:37
voidspacedimitern: I can now create a storage pool - but can't read the iso image. Which is odd. I think it's because the iso image is behind a symlink12:38
voidspacewell, copying elsewhere worked - for whatever reason12:39
dimiternvoidspace, :) go figure12:39
voidspacedimitern: I think the type of access it uses doesn't like symlinks12:41
voidspaceblock level12:41
dimiternvoidspace, why are there symlinks in there?12:42
voidspacedimitern: I moved the directory and left a symlink in the old location12:43
voidspacedimitern: ~/Downloads12:43
voidspacedimitern: it's where the iso image is12:43
voidspacedimitern: for the storage volumes I used bind mount to move them12:44
voidspacedimitern: which may or may not be necessary - but works12:44
voidspacedimitern: I just needed to set the right owner/group on the files as well12:44
dimiternvoidspace, hmm bind mounts should work better than symlinks12:46
dimiternvoidspace, can't you specify default owner/perms at mount time of the bind?12:47
voidspacedimitern: the bind mount is working fine12:49
voidspacedimitern: the ~/Downloads symlink is also fine normally12:49
voidspacedimitern: it's just that because it's a symlink virt-manager can't get block level access to iso images there12:50
voidspacedimitern: I should have specified the full path instead of via the symlink - just habit12:50
dimiternvoidspace, ah, I got you12:50
dimiternfwereade, are you around?12:50
mupBug #1433577 was opened: Vivid unit tests need to pass <ci> <test-failure> <vivid> <juju-core:Triaged> <https://launchpad.net/bugs/1433577>12:59
mupBug #1433577 changed: Vivid unit tests need to pass <ci> <test-failure> <vivid> <juju-core:Triaged> <https://launchpad.net/bugs/1433577>13:05
mupBug #1433577 was opened: Vivid unit tests need to pass <ci> <test-failure> <vivid> <juju-core:Triaged> <https://launchpad.net/bugs/1433577>13:11
natefinchmattyw: that severity is different than the severity you were using before... is that right?13:35
mattywnatefinch, it's changed a little bit, the logic had changed with it though yes13:53
mattywnatefinch, I think this order makes more sense13:53
ericsnowdimitern: FYI, bug 1433577 looks like the same issue as bug 1433384, but on vivid13:57
mupBug #1433577: Vivid unit tests need to pass <ci> <test-failure> <vivid> <juju-core:Triaged> <https://launchpad.net/bugs/1433577>13:57
mupBug #1433384: unit-test failure: TrackerSuite.TestWaitMinionBecomeMinion <ci> <i386> <regression> <test-failure> <utopic> <juju-core:In Progress by fwereade> <https://launchpad.net/bugs/1433384>13:57
dimiternericsnow, well part of it is13:58
ericsnowdimitern: right13:58
dimiternericsnow, fwereade is already on #1433384 btw14:00
mupBug #1433384: unit-test failure: TrackerSuite.TestWaitMinionBecomeMinion <ci> <i386> <regression> <test-failure> <utopic> <juju-core:In Progress by fwereade> <https://launchpad.net/bugs/1433384>14:00
ericsnowdimitern: ah, great14:00
dimiternericsnow, I wanted to check something with you re systemd support14:01
ericsnowdimitern: sure14:02
dimiternericsnow, looking at https://github.com/juju/juju/blob/master/container/lxc/clonetemplate.go#L129-L17214:02
ericsnowdimitern: yep14:03
dimiternericsnow, and the corresponding test - https://github.com/juju/juju/blob/master/container/lxc/lxc_test.go#L811-L84114:03
dimiternericsnow, do you think this will work for systemd? I mean for upstart it does (it's live tested), but I wasn't sure if you can have multiple commands in ExecStart (provided all of them have abs. paths)14:04
ericsnowdimitern: systemd only allows a single command for ExecStart (or any Exec*)14:06
ericsnowdimitern: however, the systemd code in juju turns a multi-line ExecStart into a separate shell script that ExecStart then calls14:06
dimiternericsnow, so it will work?14:08
ericsnowdimitern: it should work fine; I'll look more closely at it in a minute14:09
perrito666ericsnow: wwitzel3 ?14:09
dimiternericsnow, thanks!14:09
mupBug #1433615 was opened: Manual provider fails to bootstrap: failed to check provisioned status ... /: Is a directory <bootstrap> <ci> <manual-provider> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1433615>14:29
alexisbnatefinch, ericsnow, fwereade, dimitern thank you all for tackling critical bugs for 1.23 quickly14:45
ericsnowalexisb: blame my feeling of guilt :)14:46
alexisbericsnow, given the number of features we landed in 1.23 we will be seeing a fair amount of guild :)14:47
alexisbwe will just need to tackle the bugs quickly and get things hardened and stable, ready for the release14:48
dimiternericsnow, :) guilt usually works for me as well14:48
dimiternalexisb, thanks!14:49
ericsnowfwereade: you free to meet briefly?15:06
fwereadeericsnow, oops, sorry, with you in 215:07
ericsnowfwereade: no worries15:07
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
=== kadams54 is now known as kadams54-away
fwereademgz, sinzui: FATAL: Unable to delete script file /tmp/hudson7105716500738528055.sh ?16:02
natefinchgah, why the heck is machine 0 running without the environmanager job when it first boots up? :/16:02
natefinchoops, nevermind... figured out what I was doing wrong :)16:04
=== kadams54-away is now known as kadams54
natefinchman I hate it when people type assert stuff and then if the type assert fails... don't tell me what type it actually was in the error - https://github.com/juju/juju/blob/master/apiserver/watcher.go#L9016:41
jw4natefinch: at least log the type right?16:49
jw4natefinch: not sure if it's a potential security issue to reveal the type in the error?16:50
* jw4 out for a couple hours16:51
fwereadedimitern, can you clarify http://reviews.vapour.ws/r/1165/diff/3/?file=42926#file42926line396 ?17:22
fwereadedimitern, that's a comment I added (in what I thought was the right place) to address my remembering someone had once asked why we did that, and that it wasn't immediately clear from context17:23
fwereadedimitern, if I explained it nearer the top of the method it'd be further away from the code it's explaining and likely to rot even faster than most comments17:24
natefinchfwereade: I hate that this code doesn't differentiate between "not found" and "wrong type" :/  https://github.com/juju/juju/blob/master/apiserver/watcher.go#L9017:48
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
fwereadenatefinch, I think the error is reasonable for both cases, but yes, when debugging you'd probably want to know more18:00
fwereadeabentley, if you're around I appear to have broken the bot with http://juju-ci.vapour.ws:8080/job/github-merge-juju/2552/18:01
abentleyfwereade: looking...18:09
abentleyfwereade: do you have an idea what the cause is here?  I don't understand why it can't delete the script.  I can (try to) delete the script, but I imagine the same thing will happen with the next run.18:14
fwereadeabentley, I have no idea, I'm afraid18:14
abentleyfwereade: AFAICT, the script is being deleted by jenkins, and it has 0644 with ownership jenkins:jenkins, and /tmp (the parent directory) is 077718:16
abentleyfwereade: I might as well try18:17
abentleyfwereade: I've deleted the script and triggered a rebuild.18:17
abentleyfwereade: It seems to be getting further: http://juju-ci.vapour.ws:8080/job/github-merge-juju/2553/console18:19
fwereadeabentley, cool, thanks18:19
voidspacedimitern: ping18:29
voidspacedimitern: you shouldn't be here even if you are :-)18:29
voidspacedimitern: but just in case...18:29
voidspacedimitern: running upgrade with loggging shows that the life field is correctly set to "dead" for a destroyed container IP address18:30
voidspacedimitern: so I'm proposing the logging branch (just two logging lines)18:30
voidspacedimitern: and moving onto the worker18:30
=== arosales_ is now known as arosales
natefinchyou know it's bad when I can't even tell WTF is going on with a full traceback.19:11
natefinchthis watcher code is a twisted mess19:11
perrito666natefinch: there are worse, beware of what you wish19:21
perrito666I have been around watcher when changin state, need a hand?19:21
natefinchperrito666: yeah... just trying to debug why this watcher is causing an error19:23
natefinchperrito666: brb19:24
perrito666heh, seems my help causes people to flee :p19:24
natefinchperrito666: back19:28
natefinchperrito666: let's jump in moonstone19:28
=== kadams54 is now known as kadams54-away
natefinchwwitzel3: you around?19:38
=== kadams54 is now known as kadams54-away
wwitzel3natefinch: yep20:04
natefinchwwitzel3: was the watcher working for you?  I keep getting a problem where the state server says it's trying to find a watcher with an empty id... but I can't figure out why, because the watcher code is all so twisty20:06
wwitzel3wwitzel3: nope. that is the same error I left it at last night, I'm working on that no, trying to get it fixed.20:07
wwitzel3natefinch:20:07
wwitzel3natefinch: the setup runs, the handle runs (which is our usual throw away the first run stuff), then I get that unknown watcher id20:08
natefinchwwitzel3: ok, cool (sorta).  I made a branch with more logging on my github called nate-ww3-ha-to20:09
natefinchit also has some of the work to actually do stuff inside the watcher when it triggers... but yeah, I haven't been able to figure out the unknown watcher ID thing either20:10
perrito666juju local behaves much like the ring from lotr, when you most need it it leaves you stranded20:10
natefinchwwitzel3: I know that it's because it's somehow getting an empty id in newNotifyWatcher, but can't figure out why20:10
wwitzel3natefinch: right, and the Next attempt throws the error20:10
niedbalskiabentley, ping20:11
niedbalskiabentley, are you able to target https://bugs.launchpad.net/juju-core/+bug/1423936 to 1.22 ?20:11
mupBug #1423936: Juju backup fails when journal files are present <backup-restore> <cts> <juju-core:Triaged by niedbalski> <https://launchpad.net/bugs/1423936>20:11
abentleyniedbalski: I can.20:15
alexisbo perrito666 look a backup and restore bug, your favorite20:16
wwitzel3lol20:16
perrito666alexisb: it is my favorite20:16
perrito666because natefinch has a patch for it20:16
perrito666:p20:16
alexisblooks like niedbalski has fixed it for you though20:17
perrito666and by natefinch I meant niedbalski20:17
natefinchhaha I was going to say... news to me20:17
alexisbheh exactly20:17
perrito666natefinch: you should have seen your face20:17
wwitzel3natefinch frequently codes up patches and just keeps them in his back pocket, JIC20:17
perrito666lol20:17
alexisbabentley, that bug will need to be discussed in the release call, so that xwwt and team can decide how/when the point release will go out20:19
abentleyalexisb: ACK.  With 1.23 in beta, 1.22 may soon be obsolete anyway.20:21
alexisbabentley, we will be pushing it to trusty20:21
niedbalskiabentley, thanks20:31
abentleyniedbalski: np20:36
ericsnowdimitern: FYI, I wrote a patch to test systemd in containers/lxc: http://reviews.vapour.ws/r/1203/20:48
bogdanteleagais there any way to debug go build hanging completely?21:35
thumperbogdanteleaga: umm... best person to suggest stuff would be davecheney I think21:38
thumperwallyworld: you up?21:41
wallyworldthumper: yeah, in meeting, talk soon21:41
thumperack21:41
mupBug #1433615 changed: Manual provider fails to bootstrap: failed to check provisioned status ... /: Is a directory <bootstrap> <ci> <manual-provider> <regression> <juju-core:In Progress by ericsnowcurrently> <https://launchpad.net/bugs/1433615>22:01
wallyworldthumper: zup22:03
thumperwallyworld: quick hangout?22:07
wallyworldsure22:07
=== urulama is now known as urulama__
ericsnowbbl (running some errands)22:24
mupBug #1433384 changed: unit-test failure: TrackerSuite.TestWaitMinionBecomeMinion <ci> <i386> <regression> <test-failure> <utopic> <juju-core 1.23:Fix Committed by fwereade> <https://launchpad.net/bugs/1433384>22:46
mupBug #1433384 was opened: unit-test failure: TrackerSuite.TestWaitMinionBecomeMinion <ci> <i386> <regression> <test-failure> <utopic> <juju-core 1.23:Fix Committed by fwereade> <https://launchpad.net/bugs/1433384>22:55
mupBug #1433384 changed: unit-test failure: TrackerSuite.TestWaitMinionBecomeMinion <ci> <i386> <regression> <test-failure> <utopic> <juju-core 1.23:Fix Committed by fwereade> <https://launchpad.net/bugs/1433384>23:01
ericsnowwallyworld: FYI, those failing tests on precise just passed: http://juju-ci.vapour.ws:8080/job/run-unit-tests-precise-amd64/2538/console23:06
wallyworldericsnow: awesome. i'm still waiting for the manual provider tests to pass also23:06
ericsnowwallyworld: when you have a minute could you take another look at http://reviews.vapour.ws/r/1164/?23:33
ericsnowwallyworld: I haven't done much manual testing on it yet (due to more pressing concerns)23:33
wallyworldericsnow: looking23:38
ericsnowwallyworld: ta23:38

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