davecheneythumper: why does var b []byte != var b = []byte{} ?00:06
thumperone is nil, one is not00:06
davecheneyright, but was that the question ?00:07
thumperI think that either they should be equal, or be visually different00:07
thumperthe question is why they have the same representation00:07
thumper<thumper> a nil string slice is output as []string(nil), but a nil byte slice is shown as []byte{}00:07
thumperempty string slice is []string{}, empty byte slice is []byte{}00:08
thumpernil slice != empty slice00:08
thumperso they shouldn't have the same representation00:08
thumpermade debugging very confusing00:08
davecheneyprobably just how fmt decides to print them00:08
davecheneythumper: if you're looking for someoone to blame00:08
davecheneyblame gocheck00:08
thumperdavecheney: see the play things above00:09
thumperthey don't use gocheck00:09
thumperif anything, I'll blame the "fmt" library00:09
thumperhence, go bug?00:09
davecheneycertainly an inconsistency00:10
davecheneyid' still like to blame gocheck for this00:11
davecheneybecause the chance of chaning it in the go runtime are approximatly 000:11
thumperyou can't just blame a different library because core won't change00:12
thumperthat's dumb00:12
davecheneyyup, i'm dumb00:12
thumpersurely it could be filed as a bug00:12
thumperand fixed during the next *we'll break things* type release00:12
thumperto make things more consistent00:13
thumperlunch time...00:34
davecheneyaxw: ping00:49
_mup_Bug #1218329: Update default environment.yaml for Azure to use Precise for default-series <juju-core:Triaged> <https://launchpad.net/bugs/1218329>01:26
davecheneydo we need to hold off 1.13.3 for this bug ?01:27
wallyworlddavecheney: i think we should, but that's IMHO01:27
davecheneywallyworld: ack01:28
wallyworlddavecheney: it's a trivial patch, so we can do it today once confirmation of the stream is done01:29
axwdavecheney: would you prefer if I hold off merging manual provisioning?01:32
davecheneyaxw: what are the changes it'll bugger up azure01:34
davecheneyif it's > 5%, then yes01:34
axwdavecheney:  I would say 0%, but my thinking may be biased01:35
davecheneyyour call01:36
davecheneyi;m worried about all the stuff in review01:37
axwdavecheney: worried why?01:37
axwworred that we need them in for 1.14?01:38
davecheneythree cards there that I wanted to see land01:38
davecheneyMP, azure stuff, and the bug fix for version formatting01:38
davecheneythere is nearly as much stuff in review as has landed01:38
axwdavecheney: I can and will get MP in right now. I'm confident it's not going break anything else01:39
davecheneyaxw: sgtm01:39
axwdunno anything about the others I'm afraid01:39
davecheneyaxw: for manually provisioning, this requires a working environment01:50
davecheneyie, you cannot manually provision a bootstrap node01:50
axwdavecheney: correct01:50
davecheneyaxw: if my bootstrap node is in amazon, can I manually provision a machine in my local lan ?01:51
axwdavecheney: yes, if it can route to the bootstrap node01:51
davecheneythis sounds icky01:51
davecheneyi'd like to not mention this in the release notes01:51
davecheneyor we'll get bollocked by jorge again01:51
axwdavecheney: fair enough, it is a bit raw01:51
davecheneyalternatively, if you want to write war and peace01:52
davecheneygo for it01:52
axwnah leave it out for now01:52
davecheneybut I vote for putting a card in leankit to properly document it01:52
davecheneyand leaving it for 1.15.001:52
davecheneyaxw: https://bugs.launchpad.net/juju-core/+bug/121832901:59
_mup_Bug #1218329: Update default environment.yaml for Azure to use Precise for default-series <juju-core:Triaged> <https://launchpad.net/bugs/1218329>01:59
davecheneydo you have an environemnt to test this change >?01:59
axwdavecheney: yep I'll give it a whirl02:00
axwazure called me up yesterday morning about the account I created ... that was slightly weird02:01
davecheneyaxw: yeah, they'll call you a few times02:02
davecheneyi told the guy i was only using it for a test and had no interest in paying for their service02:03
davecheneyhe soundded confused02:03
davecheneyand was still confused when he called me a week later and asked the same thing02:03
axwdavecheney: so far, not so good... looks like the SSH keys aren't setup properly02:12
axwalso - I couldn't use released, had to use daily02:12
davecheneyaxw: ok, play with it a bit more, otherwise move the ticket to 1.15.002:12
davecheneyonce we have a 1.14 series we can backport fixes02:13
davecheneybut waiting on a working precise image could take longer than we have02:13
davecheneyso screw it02:13
davecheneywe can do a point release into 1.1402:13
* davecheney waves to robbiew 02:31
jcastrodavecheney: hang out with us!02:31
davecheneyjcastro: but it's my special time with ubu hulk02:31
jcastrooh dang02:31
robbiewdavecheney: on my way...got distracted with other work stuff02:31
jcastrook, after?02:31
davecheneyjcastro: sure thing02:32
jcastrowe're just hanging out02:32
davecheneyjcastro: shiiit, what is this, a party ?02:32
jcastrodidn't know it was Thor <-> Hulk bonding time02:32
jcastrodavecheney: nah, did a live juju upgrade on discourse so we had to do it post-work and late02:33
davecheneyjcastro: DC characters need love too02:33
jcastroand we had some feedback, but whatever, nothing that can't wait02:33
jcastrofrom now on you are SOLMON GRUNDY02:33
robbiewjcastro: wtf you doing up?02:34
jcastrorobbiew: upgrading services with less than a minute downtime? :)02:34
jcastronext time we're doing cascading upgrades ....02:34
jcastronot to brag or anything02:34
* jcastro brags because he's backed by marcoceppi.02:35
davecheneyThis party is over...03:16
davecheneyBut you can start a new one.03:16
davecheneysome party03:17
jcastrodavecheney: let's party tomorrow?03:24
wallyworldaxw: ping04:04
axwwallyworld: hoy04:04
wallyworldi just saw your mp for genersting tools metadata and have a question or two04:04
wallyworld1. i'd like the functionality to generate the json separated out into a separate method, as i need to use it in another context04:05
wallyworldi want to pass a list of ToolsMetdata and get back the index and product json04:05
wallyworldi need this for tests04:05
axwok- I can move it to environs/tools?04:05
wallyworldalso, the Boilerplate() method can be updated to use this also04:06
wallyworldinstead of go templates04:06
wallyworldi think environs/tools sounds ok04:06
wallyworld2. i'm not sure why you are writing to a storage and not just to disk04:06
wallyworldwe don't need to generate the metadata into a public bucket04:07
wallyworldwe need to read tools from somewhere (currently all we have is the public bucket), but the metadata needs to go either to disk locally or uploaded somewhere04:07
axwwould people not want to host it in their private swift storage or whatever?04:08
wallyworldso for now, just have the command take a dest dir (default to .juju like for imagte metadata)04:08
wallyworldyes, private storage perhaps, but not public04:08
wallyworldso you could use a storage abstraction as yuo have done04:09
axwyeah I was thinking "public" as in shared within a private org04:09
axwnot the official public one04:09
wallyworldah ok04:09
axwbut anyway04:09
axwit can go to disk and they can do that04:09
wallyworldwell, the storage abstraction used works04:09
wallyworldbut use the env.Storage()04:10
wallyworldnot env.PublicStorage() to write to04:10
axwokey dokey04:10
wallyworldit would be great to land this today if we could as i have stuff queued up behind it - i have tests where i need to generate tools metadata and then read it back04:11
axwwill get onto it now04:11
wallyworldthanks :-) it doesn't have to be perfect straight up cause we won't advertise it, it will mainly be for us internally04:12
wallyworldaxw: with the metadata generation, if the new method could be such that i get the json back as a string for index and product, that would be good. then there would be another new method to write those strings to files04:13
wallyworldor a reader or whatever04:14
axwwallyworld: nps, easy enough04:14
wallyworldi just need to hold the data in memory for a http proxy class to use04:14
axwwallyworld: I think I just found a problem... paths should be relative to the base URL right? i.e. "juju-1.12.0-precise-amd64.tgz", and not "tools/juju-1.12.0-precise-amd64.tgz"?04:51
axwsince the base URL includes /tools/04:51
wallyworldyes, paths should be relative to the base url04:52
wallyworldi envisiage tarballs will be in releases/04:52
wallyworldie http://juju.canonical.com/tools/releases04:52
wallyworldand metadata in http://juju.canonical.com/tools/streams/v104:53
* wallyworld has to go do school pickup05:03
axwwallyworld: updated. I haven't yet added tests to environs/tools. Haven't yet updated boilerplate. It's still using storage, I will change that now.05:03
wallyworldaxw: ok, thanks, bbiab05:03
* thumper slogs through fixing shit05:23
thumpermorning fwereade05:38
thumperfwereade: around 7:30am?05:38
fwereadethumper, heyhey05:38
fwereadethumper, yeah05:38
thumpergot time for a quick chat before I EOD?05:39
thumperand EOW05:39
thumperand EOM05:39
thumperfwereade: https://plus.google.com/hangouts/_/ebc7ddf59bb207399b6ce7ab7ccd391a4fd9fede?hl=en05:40
thumpernight all06:02
rogpeppemornin' all06:34
wallyworldaxw: hi, i made some more comments. i hope they make sense06:41
=== tasdomas_afk is now known as tasdomas
axwwallyworld: thanks, I'll have a look in a sec06:45
wallyworldaxw: np. i have to take the dog for a quick walk before he bites me, i'll check back in soon06:45
axwno worries06:45
axwwallyworld: `There's little point using an env to read the tools - the tools are readily07:17
axwaccessible directly from "https://juju-dist.s3.amazonaws.com/" (see synctools)`07:17
axwenvirons/sync does use the env's storage?07:18
fwereadeaxw, it's done in sync-tools -- there's a storage interface that talks to juju-dist directly over http07:26
axwfwereade: thanks07:26
fwereadeaxw, and also allows for reading in from a dir, which I think wallyworld mentioned, but I barely skimmed that CL I'm afraid07:26
wallyworldaxw: sync uses the env storage to write to the private bucket, so the tools are available for that env07:50
axwwallyworld: yeah I just missed the whole bit about newFileStorageReader/ec2.NewHTTPStorageReader07:55
wallyworldaxw: is anything unclear with my (brief) comments?07:56
axwwallyworld: nope, makes sense07:56
axwjust updating and testing now07:56
wallyworldcool, thanks07:56
wallyworldthe main business logic is to (somehow) get a list of tools and generate metadata07:57
wallyworldthis will be used by sync tools and tests, plus the generate command for devs/prototyping07:57
axwI've moved the fileStorageReader to environs/filestorage07:57
axwwill use that and the ec2 thing inside toolsmetadata07:57
axwand update sync accordingly07:58
wallyworldok. i'm wondering is we want a "wget" reader also, one that takes a http url if you know what i mean07:58
wallyworldmaybe not07:59
wallyworldlet's wait till we need it07:59
wallyworldi'm hoping medium term when we have the proper tools repository that we won't need the reader abstraction08:00
wallyworldsince we can access the official tools and metadata directly using wget08:00
wallyworldand not via a s3 bucket08:00
axwyeah, no need to list then08:00
axwwallyworld: you want me to move ItemCollection.UnmarshalJSON to json.go? so, I should move all the structures there?08:01
wallyworldso when we do that, we should be able to have an abstraction that takes a url, either file:// or http:// to get the tools etc08:01
axwin environs/simplestreams08:01
wallyworldaxw: i 'd like all the json related stuff out separate08:01
wallyworldso as not to obscure the core simplestreams lofic08:02
wallyworldwe did something similar in goose08:02
wallyworldsee goose.nova package08:02
rogpeppefwereade: ping08:50
fwereaderogpeppe, pong08:50
rogpeppefwereade: i've been looking at the config stuff, and wondering about firewallmode==default08:51
rogpeppefwereade: the idea is that a given environment can choose its own default, right?08:51
fwereaderogpeppe, I *think* so, yes08:51
rogpeppefwereade: i can't see how that can happen currently08:51
fwereaderogpeppe, doesn't surprise me at all08:51
rogpeppefwereade: the code *looks* as if it's trying to go in that direction08:52
rogpeppefwereade: but swerves at the last moment08:52
fwereaderogpeppe, haha08:52
fwereaderogpeppe, if that's not what it's for, your guess is as good as mine08:52
rogpeppefwereade: in particular, in config.New:08:52
rogpeppe// Default firewall mode is instance.08:52
rogpeppeif c.FirewallMode() == FwDefault {08:52
rogpeppec.m["firewall-mode"] = string(FwInstance)08:52
fwereaderogpeppe, I think TheMue may have been involved there08:52
rogpeppefwereade: so AFAICS no provider will ever see FwDefault08:53
fwereaderogpeppe, he might remember08:53
fwereaderogpeppe, I think you're right08:53
rogpeppefwereade: i'm sorely tempted to lose the whole idea08:53
rogpeppefwereade: and just let a given provider ignore the firewall mode if it can't deal with it08:54
* fwereade shrugs, and doubts that's any worse than what we currently have08:54
fwereaderogpeppe, the whole firewalling story is madness anyway IMO08:55
rogpeppefwereade: BTW i'm testing a branch which cleans up the config prior to moving forward with environment attr storage, which changes config.New to this: http://paste.ubuntu.com/6043287/08:55
fwereaderogpeppe, it's probably not too many steps from sanity, but plotting those steps makes me confused08:56
rogpeppefwereade: i'm hoping/assuming you will wholeheartedly approve08:56
axwwallyworld: there's a bunch of tests I'm not going to be able to complete today. if you wanted this stuff landed to unblock you, I can do so and follow up with tests on Monday08:57
wallyworldaxw: it's ok, i can wait. i'm currently modifying another upstream branch08:57
axwwallyworld: okey dokey08:57
fwereaderogpeppe, that looks pretty sexy to me :)08:57
wallyworldwe can get the next release out first anyway08:57
rogpeppefwereade: the next step is to pass a config.Defaulting flag to EnvironProvider.Prepare and EnvironProvider.Open08:58
wallyworldaxw: maybe push what you have and i'll take a look over the w/e08:58
rogpeppefwereade: to enable providers to be similarly strict about env vars08:58
fwereaderogpeppe, nice08:58
axwwallyworld: done08:59
wallyworldthanks :-)08:59
wallyworldwill look a bit later08:59
axwwallyworld: just missing tests on environs/filestorage (never were any explicit ones), and the new marshalling stuff in environs/tools08:59
fwereadewallyworld, btw, I'm having some persistent difficulty mapping simplestreams cloud info <-> juju concepts -- would you be free for a chat about it after the standup?09:00
wallyworldwe are also blocked on IS getting the tools repository set up09:00
axwwallyworld: I generated metadata for all the tools in S3 earlier, if you want the JSON files for anything...09:01
wallyworldfwereade: sure. i'll be up to my 5th drink by then, should be fun :-)09:01
wallyworldaxw: sure, send them my way, thanks :-)09:02
fwereadewallyworld, it'll probably help ;p09:03
wallyworldfo :-)09:03
rogpeppeeveryone should try the go coverage tool to check test coverage - it's awesome!09:54
rogpeppefor example, see this output: http://paste.ubuntu.com/6043486/ (save the text as html and open it in your browser)09:55
fwereadewallyworld, btw, when you're around, I was wondering if you knew what "crsn" was meant to stand for :)09:56
wallyworldfwereade: cloud region short name09:56
fwereaderogpeppe, nice and shiny, indeed10:01
fwereaderogpeppe, I have seen far worse coverage output ;p10:02
rogpeppefwereade: BTW, speaking of test coverage, do you know what happened to the tests for RelationUnitsWatcher ?10:02
rogpeppefwereade: there appear to be none at all10:02
fwereaderogpeppe, I'm not that surprised, it's basically an implementation detail of RelationScopeWatcher10:04
rogpeppefwereade: it is used directly by the uniter though10:04
rogpeppefwereade: and none of its code is covered by the state tests (verified with the shiny new coverage tool)10:06
rogpeppefwereade: i suspect the test coverage loss was an inadvertent consequence of https://code.launchpad.net/~fwereade/juju-core/state-relationunit-move/+merge/14474710:08
fwereaderogpeppe, sorry, meeting pushed that conversation out of my mind10:44
rogpeppefwereade: np10:44
fwereaderogpeppe, looks like you're right, and I suck10:49
rogpeppefwereade: happens to all of us :-)10:49
fwereaderogpeppe, indeed, but thanks for catching it10:49
fwereaderogpeppe, I suspect I zoned briefly out of the distinction between Watch and WatchScope and, boom, splat10:50
rogpeppefwereade: i'm wondering if we could do something with the coverage tool to automatically detect loss of test coverage10:51
rogpeppefwereade: something to keep in mind anyway10:51
fwereaderogpeppe, that would be very nice, yeah10:52
fwereaderogpeppe, tech-debt bug?10:52
rogpeppefwereade: https://bugs.launchpad.net/bugs/121836210:52
_mup_Bug #1218362: state.RelationUnitWatcher is not tested <tech-debt> <juju-core:Triaged> <https://launchpad.net/bugs/1218362>10:52
fwereaderogpeppe, ah, I meant for the coverage tool10:53
rogpeppefwereade: oh, i see10:53
rogpeppefwereade: yeah, i'll do that10:53
rogpeppefwereade: https://bugs.launchpad.net/juju-core/+bug/121883410:56
_mup_Bug #1218834: There's no way to easily detect loss of test coverage <tech-debt> <juju-core:New> <https://launchpad.net/bugs/1218834>10:56
fwereaderogpeppe, standup11:33
rogpeppefwereade: "There is a problem with connecting to this video call. Try again in a few minutes"11:34
natefinchevilnickveitch: it occurs to me that your document says to sync docs with the reality of 1.12 ... does that mean we shouldn't document stuff that is later than 1.12?  For example, windows support is not in 1.1212:27
mgznatefinch: if we release 1.14, presumabley we'd update that to read '1.14'12:27
evilnickveitchnatefinch, i think in this case we can document it and work out what notes and info we need to provide later. at some point in the future we will have different versions of the docs which will make this easier12:28
mgzhaving a doc 'feature' branch for dev stuff that will be in next stable seems sane12:28
mgzthen we just merge that to doc trunk when we do the release12:28
evilnickveitchmgz, indeed12:28
evilnickveitchwe need a good base to start from - i think we need to be at a point where we are not adding loads of stuff to the stable docs before we start doing that12:29
natefinchmgz, fwereade, rogpeppe: just had a thought - should we refrain from creating a "local" environment section in environment.yaml on Windows, since it can't possibly work there?  Or maybe create it commented out, with a comment that it doesn't work on Windows.12:48
natefinchTheMue: ^^^ since you're writing docs on the local provider - might be good to mention it doesn't work on Windows :)12:50
TheMuenatefinch: oh, yes, good hint, and it won't work on a mac12:54
natefinchTheMue: yep12:54
TheMuenatefinch: only in a vmware image running linux ;)12:55
fwereade_natefinch, good idea, thank you13:39
fwereade_hmm, my smoothie has fermented13:43
TheMuefwereade_: iirks13:50
marcoceppiHow often does the store update personal branches?13:57
marcoceppinvm, gui cache issue13:58
rogpeppefwereade_, mgz, natefinch, jam, TheMue: trivial CL, enabling some tests that were not hooked in: https://codereview.appspot.com/13428043/14:29
fwereade_rogpeppe, I'll do that if you'll do https://codereview.appspot.com/13401045 :)14:30
fwereade_rogpeppe, LGTM14:31
rogpeppefwereade_: likewise14:31
fwereade_rogpeppe, cheers14:32
mgznice backscratching :)14:32
TheMuerogpeppe: LGTM from my side too14:33
rogpeppemgz: always good when you have an itch14:33
=== tasdomas is now known as tasdomas_afk
mrammfwereade_: you around?15:01
fwereade_mramm, yeah, what can i do for you?15:02
mrammI am wondering if we can setup a "what does 2.0 mean" meeting for the beginning of next week15:02
fwereade_mramm, sure, that sounds good15:03
fwereade_mramm, a bit after standup on monday perhaps?15:03
mrammI'm thinking about timelines, and thinking that we may want to manage the scope of a 2.0 release a bit more15:03
mrammyea, that works for me15:04
fwereade_mramm, that was put with admirable delicacy btw15:04
mrammI will want to include Gary in that conversation15:05
hazmatfwereade_, ping15:08
fwereade_hazmat, pong15:12
hazmatfwereade_, trying to debug the slowness that's been reported on the list15:15
hazmatdo you have a minute to discuss on g+?15:16
fwereade_hazmat, thank you kindly :)15:16
fwereade_hazmat, in a moment I think15:16
mgzhazmat: a fair bit of it can just go from status, when it doesn't need to do anything other than query state (over the api)15:20
hazmatmgz, right, i could make a fast status impl right now just using the allwatcher, not quite the same data. one of the issues in their status output is the amount of garbage they've got  in terms of machines15:21
hazmatthat are missing, pending, etc.15:21
hazmatand helping them garbage collect15:21
mgzright, there's always an issue inside the reported issue :)15:22
hazmatmgz, status in the api is all nesc for correctness for deployer15:22
hazmatsince watch api is eventually consistent15:22
hazmati took a look at the sprint unfortunately the status code has several embedded panics15:22
hazmathmm.. bootstrapping on ec2 takes a very long time15:57
hazmatfor the command to complete15:57
=== TheRealMue is now known as TheMue
hazmatis juju trunk supposed to build?18:01
hazmatprovider/ec2/ec2.go:131: inst.Instance.IPAddress undefined (type *ec2.Instance has no field or method IPAddress)18:01
rogpeppehazmat: i think you need to do go get -u launchpad.net/goamz/ec218:09
hazmatrogpeppe, thanks18:10
rogpeppefwereade_, natefinch, TheMue, anyone else: , here's a large but trivial CL, just moving test code around: https://codereview.appspot.com/13348049/18:11
rogpeppehazmat: for the record, there's no a file in the juju-core root (dependencies.tsv) that declares the revision numbers of dependencies18:22
rogpeppes/no a/now a/18:27
hazmathmm ec2 Storage().RemovaAll() takes 50s  of 1m3s for destroy-environment18:30
rogpeppehazmat: hmm, how many tools were uploaded?18:37
hazmatrogpeppe, 118:38
rogpeppehazmat: that's really odd18:39
hazmatrogpeppe, it was an empty environment, nothing deployed18:39
rogpeppehazmat: i mean, i know s3 is slow, but...18:39
hazmatrogpeppe, do we even need to remove them?18:41
hazmatrogpeppe, i mean minus provider-state, its basically just cache18:41
rogpeppehazmat: it tries to remove all trace of an environment when it's destroyed18:41
hazmatexcept security groups18:41
rogpeppehazmat: unfotunately that's not possible18:42
rogpeppehazmat: (i tried)18:42
hazmatrogpeppe,  right.. but its not clear that we're adding significant value destroying the bucket vs the time it takes18:42
rogpeppehazmat: i've never seen it take anywhere near that long18:42
rogpeppehazmat: does this happen every time for you?18:43
hazmatrogpeppe, atm yes, i'm still instrumenting, but about to switch out for a meeting18:44
hazmatrogpeppe, bootstrap also takes quite a while18:46
rogpeppehazmat: with --upload-tools ?18:46
hazmatrogpeppe, no18:46
rogpeppehazmat: hmm, it's not bad for me if i'm not uploading tools18:48
hazmatrogpeppe, 2m9s for me18:48
hazmatrogpeppe, define not bad?18:48
rogpeppehazmat: 26s for me18:50
hazmatrogpeppe, which provider?18:50
rogpeppehazmat: ec218:50
hazmatrogpeppe, hmm.. region?18:51
rogpeppehazmat: us-east, i think18:51
rogpeppehazmat: yeah18:51
hazmati'm working against us-west-2 (us-east is literally my backyard)18:52
rogpeppehazmat: part of the slowness is timeouts for eventual consistency. it looks like if you haven't uploaded any tools, we time out, because the bucket doesn't exist and we poll just in case it was only created a moment ago18:54
rogpeppehazmat: that's 5s of my time18:54
rogpeppehazmat: there's another 10s gap where i'm not sure what it's doing18:54
hazmatgotta run for a meeting..18:54
rogpeppehazmat: k18:54
hazmatrogpeppe, it does look like the destroy time was an abberation, i'm getting closer to 30s averages now.18:55
rogpeppehazmat: ok. but that's still a bit rubbish18:55
rogpeppehazmat: i'd like to add trace messages that print all traffic to and from servers18:56
rogpeppehazmat: so we can see just what's going on18:56
hazmatrogpeppe, here's my instrumentation on destroy fwiw http://pastebin.ubuntu.com/6045232/18:56
rogpeppehazmat: looks like there might be 15s worth of eventual-consistency waiting in there18:57
rogpeppehazmat: or maybe 20s18:58
hazmatrogpeppe, should destroy-env care about eventual consistency?18:58
rogpeppehazmat: the difficulty is writing live tests that pass consistently18:59
rogpeppehazmat: if we've just created some storage, then try to delete it, the operation often fails18:59
rogpeppehazmat: unless we try for a while18:59
rogpeppehazmat: i frickin' hate it18:59
hazmatright, but that's a test responsibility not a user experience18:59
rogpeppehazmat: well, we're testing that the operations work19:00
hazmatrunning away19:00
hazmatto meeting ;-)19:00
rogpeppehazmat: :-)19:00
natefinchha, wow, it took me forever to figure out why some of my code kept saying "LICENSE" was not a file, when I clearly saw it right in the filesystem.  Finally realized the file was actually named LICENCE ... you crazy brits :)19:25
* natefinch just finally proposed his Windows changes for juju client, including the installer... now if only everyone else wasn't gone for the weekend :)19:45
=== BradCrittenden is now known as bac
rogpeppenatefinch: i'll swap you a review: https://codereview.appspot.com/1335504420:46
rogpeppenatefinch: :-)20:46
rogpeppenatefinch: although i fear mine is probably a lot more work than yours to review...20:47
TheMueso, guys, i'll stepping out, having a nice weekend20:50
evilnickveitchTheMue, thanks for your efforts!20:53
TheMueevilnickveitch: np, anytime again20:54
natefinchrogpeppe: I'm at eod, but will look monday morning20:59
rogpeppenatefinch: np20:59
rogpeppenatefinch: i'm away next week BTW20:59
natefinchoh yeah.  have fun!20:59
rogpeppenatefinch: what's your CL, BTW?21:00
natefinchrogpeppe: https://codereview.appspot.com/13079045/21:00
rogpeppenatefinch: ta21:00
rogpeppenatefinch: have a great weekend21:00
rogpeppenatefinch: and a good week too!21:00
natefinchrogpeppe:  you too21:00
rogpepperight, that's me for the week22:49
rogpeppeg'night anyone that's still around :)22:49

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