[00:50] <wallyworld> davecheney: looks like there was no release last week?
[00:53] <davecheney> wallyworld: working on it now
[00:53] <davecheney> it's an uphill battle
[00:53] <wallyworld> ok, good luck
[01:11] <davecheney> axw: BONJOUR!
[01:11] <axw> davecheney: hey :)
[01:12] <davecheney> isn't it a bit early in the year to see you in this channel ?
[01:12] <axw> nope, I start today
[01:12] <axw> just getting my SSO setup now
[01:13] <bigjools> davecheney: I'm not sure there's any consensus yet on the tls thing, did you have a preference?
[01:13] <bigjools> will prob have to wait for EU to start to get more attention
[01:14] <thumper> bigjools: how horrible is it for use to carry this patch against golang package?
[01:15] <thumper> bigjools: instead of forking individual packages?
[01:15] <bigjools> thumper: won't work on other platforms
[01:15] <thumper> what won't?
[01:15] <davecheney> bigjools: if you've been able to fork those packages
[01:15] <davecheney> then go with that
[01:15] <thumper> oh... like windows :)
[01:15] <bigjools> we have no control over golang on non-Ubuntu
[01:15] <davecheney> rog and I thought it would be more work
[01:15] <davecheney> good to hear it was only 3 packages
[01:16] <bigjools> well, I am a little concerned about forking net/http
[01:16] <wallyworld> davecheney: so you saying we fork the golang source?
[01:16] <thumper> axw: hello there, are you the new perth bod?
[01:16] <davecheney> wallyworld: make private copies of a few packages
[01:16] <thumper> bigjools: ack
[01:16] <axw> thumper: Hi. I surely am
[01:16] <thumper> axw: welcome
[01:16] <wallyworld> davecheney: won't that be a maintenance nightmare?
[01:16] <bigjools> since net/http is likely to get a lot of changes in core
[01:16] <davecheney> wallyworld: rock, meet hard place
[01:16] <davecheney> please see the discussion on the mailing list
[01:16] <bigjools> giving us a higher maintenance burden
[01:16] <thumper> wallyworld: hopefully not too hard
[01:16] <thumper> but yes
[01:16] <bigjools> g'day axw, welcome to the fray
[01:16] <axw> thumper: thanks! Looking forward to working with you guys
[01:17] <axw> bigjools: thanks and hello
[01:17] <wallyworld> davecheney: i read it, and still think it sucks to fork go
[01:17]  * thumper is currently writing a depressing email
[01:17] <thumper> wallyworld: we aren't forking all of go
[01:17] <thumper> wallyworld: just three packages
[01:17] <wallyworld> axw: g'day from another aussie
[01:17] <wallyworld> thumper: still, 3 is 3 too many
[01:18] <davecheney> wallyworld: please read the mailng list before commenting further
[01:18] <thumper> wallyworld: agreed, but in the perfect world, it would be fixed in core
[01:18] <davecheney> i don't think anyone is happy about this situatoin
[01:18] <wallyworld> davecheney: i have
[01:18] <axw> wallyworld: Hi :)
[01:18] <thumper> wallyworld: we all agree it is sub-optimal
[01:18] <bigjools> do we know why there's resistance to accepting in the core Go?
[01:18] <thumper> but the best option out of a collection of shitty options
[01:19] <wallyworld> axw: you follow cricket? if so, ignore bigjools. he is an aussie now but still yearns for the shitty place he left behind for a new life
[01:19] <davecheney> bigjools: no, please read my response on the mailinglist
[01:19] <bigjools> wallyworld: I was about to ask if you'd enjoyed that yesterday
[01:19] <davecheney> don't read too much into what agl wrote
[01:19] <axw> wallyworld: heh :)  sorry, can't say that I do
[01:19] <davecheney> it was a throw away line
[01:19] <wallyworld> bigjools: FO
[01:19] <bigjools> :)
[01:20] <bigjools> davecheney: so you think there's a chance?
[01:20] <davecheney> bigjools: yes
[01:20] <thumper> bigjools: even if so, won't come fast enough
[01:21] <davecheney> but it won't be available til dec at the soonest
[01:21] <bigjools> well if we know it's going to be in the next version, that's fine if it makes the next LTS, because the maintenance burden is not too bad
[01:23] <wallyworld> thumper: you available for a chat even though you're out and about?
[01:23] <davecheney> https://t.co/ycH9kpo7ZH
[01:24] <thumper> wallyworld: hangout wouldn't really work in this café
[01:24] <thumper> irc is fine
[01:24] <thumper> will be home in an hour (ish)
[01:25] <wallyworld> thumper: so, i've been reading martin's branches. looks like there's agreement they can be landed. what do you need from an lxc perspective?
[01:25] <thumper> wallyworld: let me send this email, then we can talk more
[01:26] <wallyworld> looks like they handle more the non container side of things
[01:26] <wallyworld> ok
[01:26]  * wallyworld has some food
[01:27] <thumper> email sent
[01:27] <thumper> wallyworld: I've not looked at mgz's latest assuming he put some up on Friday
[01:27] <thumper> I should do soon
[01:28] <thumper> from what we talked about, the planned changes should be sufficient for the local provider
[01:28] <wallyworld> ok. there's 2 branches there
[01:29] <wallyworld> and some empty methods on ec2 etc that need implementing
[01:29] <bigjools> davecheney: after 1.2 is released, how long will 1.1 be supported?
[01:29]  * thumper clicks
[01:30] <thumper> wallyworld: I was hoping someone would say to me about my tools branch: we should have tools.Tools not agent.Tools
[01:30] <thumper> but no...
[01:30] <thumper> perhaps I'll talk to fwreade about this again
[01:30] <thumper> ugh...
[01:30] <wallyworld> tools.Tools sounds better for sure
[01:30] <thumper> this table is mildly sticky
[01:31] <thumper> wallyworld: also tools package can be very targetted
[01:31] <thumper> in what it does
[01:31] <wallyworld> yes
[01:31] <davecheney> bigjools: yes
[01:31] <thumper> maybe, agent/tools ?
[01:31] <thumper> not sure
[01:31] <davecheney> 1.1 will not be supported
[01:31] <bigjools> davecheney: so there's no crossover period at all?
[01:32] <davecheney> well, not supported any more than 1.0 is supported
[01:32] <davecheney> bigjools: there is
[01:32] <davecheney> but the answer will always be, upgrade
[01:32] <bigjools> that's really hostile to distros
[01:32] <thumper> I'm fairly sure, but importing agent/tools in no way implies bringing in agent
[01:32] <thumper> davecheney: right?
[01:32] <davecheney> thumper: right what ?
[01:32] <thumper> the line above
[01:32] <wallyworld> thumper: if the tools sub package only relevant to agent?
[01:32] <wallyworld> is
[01:33] <thumper> wallyworld: it is only used by agents, and generated for the use of agents
[01:33] <wallyworld> so agent/tools perhaps
[01:33] <thumper> that is what I was thinking
[01:33] <davecheney> thumper: that is correct, importing a/b/c in no way implies you are importing a/b
[01:33] <thumper> wallyworld: then we could keep the agent.Conf in agent
[01:33] <thumper> davecheney: ta
[01:34] <davecheney> bigjools: i agree, i don't think it is something I am in a position to change
[01:34] <thumper> wallyworld: as agent/config was an attempt to show how horrible it is :)
[01:34] <wallyworld> yes
[01:34] <thumper> wallyworld: I don't really want to land that branch
[01:34] <davecheney> I have suggested maintaing a stable branch
[01:34] <davecheney> but the proposal was not accepted
[01:34] <bigjools> davecheney: wow :(
[01:34] <thumper> davecheney: for golang?
[01:34] <davecheney> thumper: yes
[01:34] <thumper> double wow
[01:35] <bigjools> this chimes perfectly with the lack of versioning in dependencies - just use trunk folks!
[01:35] <thumper> \o/ WINNING!
[01:35]  * bigjools wonders how Google handles this
[01:35] <thumper> where did I put that tiger blood
[01:36] <thumper> bigjools: I bet they have their own tool chain around it
[01:36] <davecheney> bigjools: they have all their source in one big perforce repo
[01:36] <wallyworld> davecheney: to those golang folks know anything about collaborative software development across multiple teams etc? seems not :-(
[01:36] <davecheney> it's called /google
[01:36] <thumper> a while arse guess is that they maintain their own go versions too
[01:36] <wallyworld> do
[01:36] <bigjools> I used to use Perforce years ago
[01:37] <davecheney> thumper: the development is on golang.org
[01:37] <davecheney> i think they may merge back to their /google mega repo
[01:38] <davecheney> but that is just to fit their process
[01:38] <davecheney> to the best of my knowledge there is no 'private' version of Go
[01:38] <davecheney> can I build a lp recipe from a tag ?
[01:39] <bigjools> good question
[01:39] <bigjools> probably
[01:39] <davecheney> bigjools: should I branch from the tag? it looks like lp recipes are happiest with branches
[01:39] <davecheney> ok, i'll do that then
[01:39] <davecheney> oh ffs
[01:39] <davecheney> that'll mean pushing to the bot
[01:39] <davecheney> that means I have to ask mgz to do it for me
[01:39] <davecheney> because, reasons
[01:39] <bigjools> the revision spec is defined in the recipe
[01:39] <bigjools> so you can set what you like
[01:40] <bigjools> why would you want a recipe for a fixed revision though?
[01:40] <thumper> davecheney: I *think* you can specify a revision spec in a recipe
[01:40] <thumper> davecheney: and if so, yes you can use a tag
[01:40] <davecheney> https://help.launchpad.net/Packaging/SourceBuilds/Recipes#Specifying_the_branches
[01:41] <thumper> davecheney: see the specifying revisions
[01:41] <thumper> merge packaging lp:~bzr/bzr/packaging revno:2355
[01:41] <thumper> lp:bzr tag:2.0 etc
[01:42] <davecheney> thumper: fuckin' hot sauce
[01:49] <bigjools> davecheney: why would you want a recipe for a fixed revision though?
[01:50] <davecheney> bigjools: because I'm still doing the releases without my big boy pants on
[01:51]  * bigjools tries to unsee and fails
[01:51] <davecheney> bigjools: right now the recipe builds the debs which I use to make the tools we push into s3
[01:52] <davecheney> we're also putting a tarball from the same tag onto the project page
[01:52] <bigjools> it sounds like you don't need a recipe, just a package
[01:52] <davecheney> which jamespage uses to produce the debs that go into P, Q, R and S
[01:52] <davecheney> bigjools: yes, we do need that
[01:56] <bigjools> davecheney: we use recipes to produce repeatable builds when versions get bumped.  If you're fixing the version with a tag, it doesn't make sense to me.
[01:56] <bigjools> unless you;re going to move the tag around ... :)
[01:57] <davecheney> bigjools: no, not planning on moving the tag
[01:57] <bigjools> I'd just use bzr builddeb or similar then
[02:12] <davecheney> shit, https://launchpadlibrarian.net/145546623/buildlog.txt.gz
[02:17] <bigjools> davecheney: it's not going to find the juju tag on your packaging branch is it
[02:18] <davecheney> oh fuk, right, i understand
[02:18] <bigjools> also
[02:18] <bigjools> shouldn't all those nests contain versions?
[02:18] <bigjools> otherwise it pulls tip
[02:19] <davecheney> bigjools: yes they should
[02:19] <davecheney> you are correct
[02:20] <davecheney> bigjools: that is why I want to move away from lp build recipes
[02:20] <bigjools> like I said, recipes are only really useful for repeated builds
[02:21] <bigjools> but if you don't use a recipe, you need to separately package all those nested dependencies.
[02:21] <bigjools> choices choices :)
[02:22] <davecheney> (and wallyworld wonders why this takes ages ... :)
[02:23] <wallyworld> automation!
[03:31] <davecheney> https://code.launchpad.net/~dave-cheney/juju-core/137-revert-temporary-removal-of-azure-provider/+merge/175994
[03:31] <davecheney> ping
[04:19]  * thumper has one more branch that stabs state.Tools through the heart
[04:25] <davecheney> le sigh
[04:25] <davecheney> the state is back to retrying > 1 time / second
[04:26] <davecheney> i'm tried of trying and failing to fix this bug
[04:28] <wallyworld> thumper: if you are looking for a shit way to finish your day, i have 3 mp's that need reviewing. or i can beg someone else in EU timezone
[04:29] <thumper> wallyworld: sure
[04:29] <wallyworld> thanks. i'll still need to beg for the 2nd +1 i suppose :-)
[04:30] <wallyworld> the simplestreams validation one is especially important
[04:33] <thumper> 66 files changed, 488 insertions(+), 417 deletions(-)
[04:33] <thumper> https://codereview.appspot.com/11561044/
[04:36] <davecheney> us-west-1 is slow, doo daa, doo daa
[04:38]  * wallyworld looks at thumper's branch before heading off for school pickup
[04:38] <thumper> wallyworld: it is pretty boring
[04:39] <wallyworld> hopefully easy to review then
[04:41] <davecheney> warning: do not read merge proposal while driving, may cause drowsyness
[04:43] <thumper> I'm especially happy with the testing function to check juju-core dependencies
[04:53] <thumper> wallyworld: the message is still valid
[04:53] <wallyworld> ok
[04:53] <thumper> wallyworld: it used to say that the interface was there to avoid an import loop
[04:54] <thumper> now it is to not bring in the dependency
[04:54] <wallyworld> fair enough
[04:56] <thumper> axw: how goes the new starter tasks?
[04:56] <axw> thumper: pretty much all done
[04:56] <axw> just waiting on hearing back from IS on getting my SSH key added
[04:59] <davecheney> anyone know anything about a sprint in August ?
[05:01] <bigjools> apparently there is one here
[05:01] <davecheney> apparently
[05:01] <bigjools> and you all get to learn about the lovely azure
[05:02]  * davecheney already has his account setup
[05:04]  * thumper goes to make dinner
[05:14] <davecheney> 1.11.3 is out!
[06:05] <bigjools> when the core asks a provider to open ports, does it differentiate between udp and tcp or does it expect both types to be opened?
[06:06] <davecheney> bigjools: the latter
[06:06] <bigjools> ta
[06:06] <davecheney> the open-port command does not permit you to specify the flavor
[06:12] <bigjools> it's required to specify on azure, so ... two calls needed.  yay.
[06:55]  * axw wonders how long before his brain stops automatically doing things the IBM way
[06:57] <axw> am I better off using the openstack or local provider for familiarising with juju code? local is undergoing quite a bit of change right now?
[07:00] <TheMue> axw: yes, local is in a too early stage
[07:01] <TheMue> axw: using ec2 is a robust and convenient way to get into it
[07:01] <TheMue> axw: good morning btw ;)
[07:01] <axw> TheMue: thanks. Good morning :)
[07:01] <axw> first day at Canonical - I'd like to accomplish something more than getting my accounts set up ;)
[07:02] <TheMue> axw: and hey, I've still got the IBM way of thinking in my brain, even after now more than one and a half years
[07:02] <axw> oh, you worked at IBM?
[07:02] <TheMue> axw: oh, no, but a long time with ibm technologies. first mainframe, later websphere stuff
[07:03] <axw> ah right :)
[07:03] <TheMue> axw: and in very conservative companies with large and unflexible it
[07:03] <axw> ;)
[07:11] <rogpeppe1> mornin' all
[07:14] <axw> rogpeppe1: good morning
[07:14] <rogpeppe1> axw: yo! welcome!
[07:14] <axw> thanks :)
[07:15] <rogpeppe1> axw: is this your first day?
[07:15] <axw> rogpeppe1: yes it is
[07:16] <TheMue> axw: where do you come from?
[07:16] <rogpeppe1> axw: feel free to ask about anything. i imagine you'll probably be busy doing all those initial things, but if you wanna take a look through the code, we're all online
[07:16] <axw> TheMue: I'm in Perth, Western Australia
[07:16] <rogpeppe1> axw: i guess your day is just about ended now, right?
[07:17] <axw> rogpeppe1: Thanks. Still a few hours left. I'm just getting set up with juju/openstack now
[07:17] <axw> done all the new starter things
[07:17] <rogpeppe1> axw: i've not done the openstack set up yet :-)
[07:18] <TheMue> axw: oh, the australian/new zealand group slowly outnumbers the european one
[07:18] <axw> rogpeppe1: oh, no, I'm just using canonistack
[07:18] <TheMue> axw: good reason to have the next meeting in australia :)
[07:18] <axw> TheMue: :)  there do seem to be quite a few people in A/NZ
[07:18] <rogpeppe1> axw: yeah, i haven't tried that yet. i probably should...
[07:19] <axw> rogpeppe1: what do you develop against then? EC2?
[07:19] <rogpeppe1> axw: yeah
[07:19] <axw> TheMue: just not Perth, it's dead boring
[07:20] <TheMue> axw: so we'll select Sydney, visiting Dave
[07:21] <axw> TheMue: Sounds good. I don't mind Sydney.
[07:23] <TheMue> axw: never been there, so far only europe, us and india. so it would be a new experience
[08:15] <axw> who knows about the openstack provider? seems there's a bug where it's expecting authentication to have occurred at bootstrap time
[08:17] <dimitern> guys, I need help landing this branch lp:~dimitern/juju-core/073-apiserver-pinger-on-ma-connection - i run the tests like 30 times since friday and it never fails on my machine, but it always fails on the bot - can someone please pull it and run all the tests to see if it can be reproduced?
[08:18] <dimitern> axw: can you give more details?
[08:19] <axw> dimitern: 1. I pulled tip of juju-core; 2. I init'd and configured environments.yaml to target canonistack; 3. juju bootstrap -v
[08:19] <axw> 2013-07-22 07:58:23 ERROR juju supercommand.go:235 command failed: cannot create bootstrap state file: cannot get endpoint URL without being authenticated
[08:19] <dimitern> axw: do you have your canonistack creds in the env?
[08:20] <axw> dimitern: yes
[08:20] <axw> dimitern: I can get around this by forcing authentication in goose/client code
[08:20] <dimitern> axw: set | grep OS_
[08:20] <dimitern> axw: you should see 5 lines
[08:21] <axw> dimitern: yes, they're all there
[08:21] <dimitern> axw: have you done "go install ." in cmd/juju ?
[08:21] <dimitern> after pulling
[08:21] <axw> dimitern: go get ./...
[08:22] <axw> dimitern: I don't have another juju installed
[08:22] <dimitern> axw: but do you have an existing working dir from before?
[08:22] <axw> ~/.juju ?
[08:22] <dimitern> axw: do go install there, just to be sure it runs the correct binary
[08:23] <dimitern> axw: no, the source checkout
[08:23] <axw> dimitern: I guarantee you it is :)  I modified the code to fix the problem
[08:23] <dimitern> axw: what was needed?
[08:23] <axw> goose/client.go: authenticatingClient.MakeServiceURL checks IsAuthenticated
[08:23] <axw> I changed it to call Authenticate if it's not
[08:23] <dimitern> axw: gmm let me see
[08:24] <axw> I'm just not sure if this is the appropriate place to do it. It's getting called during bootstrap
[08:25] <dimitern> axw: can you paste the exact log please?
[08:26] <dimitern> mgz: hey, can you help me with a branch i'm having trouble landing
[08:26] <axw> 2013-07-22 07:58:09 INFO juju provider.go:115 environs/openstack: opening environment "openstack"
[08:26] <axw> 2013-07-22 07:58:09 INFO juju provider.go:417 environs/openstack: bootstrapping environment "openstack"
[08:26] <axw> 2013-07-22 07:58:21 INFO juju tools.go:26 environs: reading tools with major version 1
[08:26] <axw> 2013-07-22 07:58:23 INFO juju tools.go:30 environs: falling back to public bucket
[08:26] <axw> 2013-07-22 07:58:23 INFO juju tools.go:53 environs: filtering tools by series: precise
[08:26] <axw> 2013-07-22 07:58:23 INFO juju tools.go:76 environs: picked newest version: 1.11.0
[08:26] <axw> 2013-07-22 07:58:23 ERROR juju supercommand.go:235 command failed: cannot create bootstrap state file: cannot get endpoint URL without being authenticated
[08:26] <dimitern> mgz: pull this and run all tests to see if they pass please: lp:~dimitern/juju-core/073-apiserver-pinger-on-ma-connection
[08:26] <dimitern> axw: please use paste.ubuntu.com next time :)
[08:26] <axw> sorry!
[08:27] <mgz> dimitern: SURE
[08:27] <dimitern> axw: hmm interesting
[08:27] <dimitern> mgz: cheers
[08:27] <mgz> er, caps
[08:27] <dimitern> :)
[08:27] <dimitern> axw: i'll look into it, might be indeed a bug
[08:28] <axw> okey dokey, thanks. I'll stick with my patch while I play.
[08:28] <dimitern> axw: which revision of goose you're on?
[08:29] <axw> dimitern: 99
[08:29] <mgz> dimitern: running tests now
[08:29] <axw> dimitern: entirely possible I'm out of date...
[08:30] <axw> hmm nope, seems to be the latest
[08:30] <dimitern> axw: it is the latest
[08:31] <axw> dimitern: would you like me to log a bug? or is this stuff too much in flux for that?
[08:33] <dimitern> axw: yes, please do this, so we can triage it and see whether it's a config issue or indeed a goose bug
[08:35] <dimitern> axw: against goose i think, not juju-core, as it seems
[08:35] <axw> ok
[08:43] <mgz> dimitern: either the test run hung after the charmload tests, or something else is very wrong...
[08:44] <mgz> how do I run with -gocheck.v and do all the tests again? >_<
[08:45] <dimitern> mgz: you cannot
[08:45] <dimitern> mgz: but, if you just go into .. wait a sec
[08:46] <dimitern> mgz: state/apiserver and run go test -gocheck.v
[08:46] <dimitern> mgz: alas, gocheck doesn't support running tests recursively
[09:02] <mgz> I'm failing to get cmd/juju tests to complete at all...
[09:02] <mgz> with trunk
[09:02] <mgz> I'll give up and just test the ones you care about in your branch
[09:02] <dimitern> mgz: ok
[09:04] <mgz> one failure
[09:04] <mgz> http://paste.ubuntu.com/5899884
[09:05] <dimitern> mgz: strange.. go version?
[09:05] <mgz> 1.0.2 from distro
[09:06] <dimitern> hmm.. that's probably what the bot is running, but this is wrong, should be 1.0.3 or even 1.1.1
[09:07] <mgz> 1.02 on the distro has the borked fixes from 1.0.3 so should be much the same
[09:07] <mgz> we did say we were going to switch wholesale to 1.1
[09:07] <dimitern> well, i can't make it break here
[09:07] <mgz> but haven't really pulled the trigger on that yet
[09:07] <dimitern> really frustrating..
[09:08] <dimitern> and the logic is sane, should pass
[09:08] <mgz> the bot has 1.0.3
[09:08] <mgz> at least that's what I get when I ssh in and run go version
[09:09] <mgz> if it helps, you can run that test yourself on my setup
[09:09] <dimitern> ideas how to debug this on the bot without stopping it?
[09:09] <mgz> if the bot failing on the same test as me?
[09:09] <dimitern> it is
[09:10] <dimitern> hmm.. i'll try to find another way to test the same thing
[09:10] <mgz> if so, ssh 10.55.60.158 and play around
[09:10] <dimitern> ok
[09:10] <dimitern> thanks btw
[09:18] <dimitern> mgz: if I can bug you a bit more :)
[09:18] <mgz> sure :)
[09:18] <dimitern> mgz: added some logging to the branch, so if you pull it now
[09:19] <dimitern> mgz: and then run go test -gocheck.vv -gocheck.f TestMachineLoginStartsPinger
[09:19] <dimitern> mgz: pasting the output, I should get better idea
[09:19] <mgz> ssh in and see yourself :)
[09:20] <dimitern> mgz: I wouldn't want to screw up the bot
[09:20] <mgz> it's not the bot
[09:20] <dimitern> mgz: aah, ok
[09:20] <mgz> it's my test server
[09:20] <dimitern> thanks
[09:20] <mgz> cd go/src/launchpad.net/juju-core
[09:20] <mgz> then run the last command
[09:21] <dimitern> mgz: when I do bzr pull there it says perm denied
[09:21] <mgz> I already pulled
[09:21] <dimitern> mgz: ah, ok
[09:21] <mgz> (you need forwarding for that to work)
[09:22] <dimitern> mgz: ha! it passes now
[09:22] <mgz> hm, failed once for me
[09:22] <mgz> run it a few more times
[09:22] <dimitern> mgz: weird.. so it's a timing issue then - adding two log statements seems to have fixed it
[09:23] <mgz> http://paste.ubuntu.com/5899917
[09:24] <dimitern> mgz: I can't see this - I run it like 5 times, all pass
[09:24] <mgz> logging probably made the race harder to hit
[09:24] <dimitern> http://paste.ubuntu.com/5899920/
[09:24] <mgz> it passed the last few times for me.... just failed again
[09:24] <dimitern> mgz: that's indeed disturbing
[09:25] <dimitern> but what i can say is that the pinger gets killed in both cases
[09:25] <dimitern> just some timeout is needed perhaps after that
[09:31] <dimitern> mgz: sorry, can you pull again please?
[09:37] <dimitern> i'm approving it with the last fix, fingers crossed it might pass
[09:39] <axw> is there a primer anywhere on the procedure for changesets? how to get it reviewed, etc.
[09:41] <dimitern> axw: basically, you create a merge proposal with lbox propose and it gets reviewed on rietveld, you need 2 LGTMs, then you should set the commit message on LP and mark it as approved, the bot will land it
[09:42] <axw> dimitern: thanks.
[09:42] <dimitern> axw: note: you'll need go 1.1.1 to compile launchpad.net/lbox/...
[09:43] <dimitern> ymmv
[09:46] <mgz> dimitern: done, sorry, was off in the clouds
[09:48] <dimitern> mgz: thanks, run it 10 times, passes, finally!
[09:48] <dimitern> tyvm
[09:58] <dimitern> rogpeppe1: ping
[09:59] <rogpeppe1> dimitern: poing
[09:59] <dimitern> rogpeppe1: it seems there's a problem with provisioner tests after the short/longwait stuff has landed
[09:59] <rogpeppe1> dimitern: ah
[10:00] <rogpeppe1> dimitern: is that why the bot is failing?
[10:00] <dimitern> rogpeppe1: http://paste.ubuntu.com/5900029/
[10:00] <dimitern> rogpeppe1: yeah, I've seen this on several other branches trying to land
[10:01] <dimitern> rogpeppe1: I might be wrong, but it seems like the most probable cause, can you look into it please?
[10:02] <rogpeppe1> dimitern: ah, i think i see where the problem might lie
[10:03] <dimitern> rogpeppe1: it seems in one place it was 200ms and was changed to shortwait
[10:03] <rogpeppe1> dimitern: http://paste.ubuntu.com/5900040/
[10:03] <rogpeppe1> dimitern: it assumes that a short wait is enough to check for no operations *and* to wait for the operation to be performed
[10:04] <dimitern> rogpeppe1: yeah
[10:04] <rogpeppe1> dimitern: it should probably loop polling Status
[10:04] <dimitern> rogpeppe1: it wasn't shortwait before
[10:04] <dimitern> rogpeppe1: lxc-broker_test.go in ensureNoChanges
[10:04] <dimitern> rogpeppe1: it was 200ms
[10:05] <rogpeppe1> dimitern: agreed. but ensureNoChanges should not also be ensureEnoughTimeForSomethingToHappen
[10:05] <axw> good night all
[10:05] <rogpeppe1> axw: g'night!
[10:05] <rogpeppe1> dimitern: it was only lucky that we weren't using a shorter timeout for ensureNoChanges
[10:05] <dimitern> axw: 'night
[10:06] <dimitern> rogpeppe1: seems likely yes
[10:06] <rogpeppe1> dimitern: i think this is useful stuff to find out - it will make our tests less flaky in the end
[10:07] <rogpeppe1> dimitern: i'd like to try running the tests with ShortWait=1 * time.Microsecond
[10:07] <rogpeppe1> dimitern: and make sure nothing breaks with that
[10:07] <dimitern> rogpeppe1: why? that seems extreme
[10:08] <rogpeppe1> dimitern: it's important that we don't *rely* on anything happening within the ShortWait time scale
[10:08] <rogpeppe1> dimitern: otherwise our tests will be flaky
[10:08] <rogpeppe1> dimitern: setting it to a very short timeout is one way of checking that
[10:08] <rogpeppe1> dimitern: obviously i wouldn't commit that change
[10:09] <dimitern> rogpeppe1: yeah, it seems likely a lot of tests will fail with 5 orders of magnitude shorter timeout
[10:09] <rogpeppe1> dimitern: who knows?
[10:10] <dimitern> rogpeppe1: trunk tests do not fail on my machine though.. but I already had an issue like that with my branch - the bot is slower
[10:10] <rogpeppe1> dimitern: it's a related kind of test to changing LongWait to 1 minute, which found a few issues
[10:10] <rogpeppe1> dimitern: exactly
[10:10] <rogpeppe1> dimitern: i bet that test would fail on your machine with a smaller ShortWait
[10:11] <rogpeppe1> dimitern: i just tried it and get exactly that error
[10:12] <rogpeppe1> dimitern: (only that one test fails in worker/provisioner, which is hopeful)
[10:13] <dimitern> rogpeppe1: really? with 1us
[10:13] <rogpeppe1> dimitern: yeah
[10:13] <dimitern> rogpeppe1: awesome
[10:13] <rogpeppe1> dimitern: i haven't tried any other packages yet tho
[10:14] <dimitern> rogpeppe1: ah..
[10:18] <rogpeppe1> dimitern: one test fails in state (but only one - i expected more)
[10:19] <dimitern> rogpeppe1: so 2 so far? did you run all of them?
[10:19] <rogpeppe1> dimitern: no, i thought i'd start with the likely candidates :-)
[10:20] <dimitern> rogpeppe1: ok
[10:35] <rogpeppe1> dimitern: i fixed the state test; other than that there are 4 tests in the whole suite that fail: http://paste.ubuntu.com/5900118/
[10:36] <rogpeppe1> dimitern: that's not too bad, i think
[10:36] <dimitern> rogpeppe1: very good
[10:36] <dimitern> rogpeppe1: and how about the provisioner?
[10:36] <rogpeppe1> dimitern: i fixed that one too
[10:37] <rogpeppe1> dimitern: the fslock one was just a ShortWait which should have been a LongWait
[10:37] <dimitern> rogpeppe1: awesome
[10:39] <dimitern> rogpeppe1: please propose this so things that are waiting can start landing
[10:39] <rogpeppe1> dimitern: i'm just fixing the remaining tests
[10:40] <rogpeppe1> dimitern: or perhaps i should propose that fix now...
[10:40] <rogpeppe1> dimitern: ok, will do
[10:40] <dimitern> rogpeppe1: tyvm
[10:44] <rogpeppe1> dimitern: https://codereview.appspot.com/11525045/
[10:46] <dimitern> rogpeppe1: reviewed
[10:46] <dimitern> mgz: can you take a look as well? ^^
[10:46] <mgz> sure
[10:53] <mgz> reviewed.
[10:54] <dimitern> rogpeppe1: good to go then
[11:01] <rogpeppe1> dimitern, mgz: thanks
[11:01] <rogpeppe1> it's marked as approved
[11:01] <dimitern> nice!
[11:01] <mgz> I'm a little worried the bot is unhappy right now...
[11:02] <dimitern> how so?
[11:02] <mgz> dave got a version bump reject twice it seems
[11:04] <dimitern> it works sometimes it seems
[11:04] <mgz> yeah, randomly failing tests are not fun
[11:04] <dimitern> if the stars align right, the timeouts/races do not cause trouble :)
[11:12] <allenap> rogpeppe1: Do you have time to talk to rvba and myself?
[11:12] <rogpeppe1> allenap: certainly
[11:12] <rogpeppe1> allenap: anytime
[11:12] <allenap> rogpeppe1: We'll invite you to a hangout. Should be quick.
[11:12] <rogpeppe1> allenap: cool. we've got a meeting at 12.30 BTW
[11:12] <allenap> rogpeppe1: We'll be done by then.
[11:13] <rvba> rogpeppe1: I've just invited you to our hangout.
[11:13] <rogpeppe1> rvba: could you paste a link? i haven't seen the invite yet.
[11:14] <rvba> rogpeppe1: https://plus.google.com/hangouts/_/cc7900440cd9b8960e9a2ded920992997465edd2?hl=en
[11:31] <dimitern> rogpeppe1: standup?
[11:31] <rogpeppe1> dimitern: ah yes, one mo
[11:32] <dimitern> wallyworld: ? ^^
[11:32] <wallyworld> i'm already there
[11:32] <wallyworld> waiting
[11:32] <mgz> you're a different there to us in that case
[11:32] <wallyworld> i used th one in the calendar
[11:33] <rogpeppe1> wallyworld: https://plus.google.com/hangouts/_/f497381ca4d154890227b3b35a85a985b894b471?authuser=1
[11:33] <mgz> so did I..
[11:33] <rogpeppe1> wallyworld: me too
[12:21] <wallyworld> https://codereview.appspot.com/11659043/
[12:21] <wallyworld> https://codereview.appspot.com/11655043/
[12:22]  * dimitern thinks codereview.appspot.com went to extreme lengths to make most of the generated numbers look very close at the end :)
[12:23] <dimitern> wallyworld: looking
[12:23] <wallyworld> dimitern: yeah. btw, those were for rodger and martin
[12:23] <mgz> he can always review as well! :)
[12:23] <dimitern> I have one of mine https://codereview.appspot.com/11463044
[12:23] <dimitern> wallyworld: ah, ok, won't touch them then :)
[12:23] <wallyworld> dimitern: thanks for offering!
[12:24] <wallyworld> dimitern: we were in a hangout so i forgot to prefix the pastes with some explanatory text
[12:25] <dimitern> wallyworld: np
[12:48] <dimitern> rogpeppe1, mgz: when done take a look ^^ please
[12:50] <rogpeppe1> dimitern: reviewed
[12:50] <dimitern> rogpeppe1: thanks
[13:06] <rvba> rogpeppe1: I see Dave Cheney has disabled the Azure provider to release a clean version of Juju… is it ok if we re-enable it now?
[13:06] <rogpeppe1> rvba: if you've changed things to use the new tls fork, i don't see why not
[13:06] <rvba> rogpeppe1: yep, that's currently being reviewed.
[13:07] <rvba> rogpeppe1: hang on, I updated the code and the Azure provider is now already re-enabled!
[13:07] <rogpeppe1> rvba: cool
[13:29] <dimitern> mgz: https://codereview.appspot.com/11463044 ?
[13:31] <rogpeppe1> wallyworld: posted a review
[13:31]  * rogpeppe1 goes for lunch
[13:32] <wallyworld> rogpeppe1: thanks, will look tomorrow
[13:58] <mgz> dimitern: lgtmed
[13:58] <dimitern> mgz: cheers
[14:12] <dimitern> rogpeppe1: ping
[14:15] <dimitern> rogpeppe1: i though you fixed the log pollution from the api?
[14:15] <dimitern> rogpeppe1: http://paste.ubuntu.com/5900721/ i'm getting this all the time
[14:16] <rogpeppe1> dimitern: those messages are printed only once, at init time
[14:16] <rogpeppe1> dimitern: at least... hmm, they should be
[14:16] <rogpeppe1> dimitern: perhaps they're being printed once per connection - i'll just check
[14:17] <dimitern> rogpeppe1: well I'm restarting all the time, so they might be printed once
[14:17] <dimitern> rogpeppe1: but should they?
[14:17] <rogpeppe1> dimitern: they're useful messages, yes
[14:17] <rogpeppe1> dimitern: i have an old branch somewhere that makes them less necessary
[14:18] <rogpeppe1> dimitern: but given that they only appear once, i don't think they're a great burden, and i do think they provide useful information ("why isn't my API call being made?" "ah, it's because it's being discarded because it has the wrong type signature")
[14:20] <dimitern> rogpeppe1: can we at least make them appear only at TRACE log level?
[14:20] <rogpeppe1> dimitern: Debug is probably more appropriate
[14:20] <rogpeppe1> dimitern: and i think that's enabled at test time, whereas i'm not sure trace is
[14:21] <dimitern> rogpeppe1: we should really have an easy way to set log level at run time for tests and production separately
[14:21] <rogpeppe1> dimitern: agreed
[14:22] <rogpeppe1> dimitern: BTW with my root-for-entity changes, i think we should be able to avoid the need for any of those messages to be printed.
[14:22] <rogpeppe1> dimitern: which might argue for them being left at the same log level, or even higher
[14:24] <dimitern> rogpeppe1: interesting idea
[14:37] <rvba> rogpeppe1: care to review that branch (it's really tiny)? https://codereview.appspot.com/11492044/
[14:38] <rogpeppe1> rvba: looking
[14:38] <rvba> Thanks.
[14:38] <rogpeppe1> rvba: i get a chunk mismatch error (occasional unavoidable rietveld glitch) - could you run lbox propose again please?
[14:42] <rvba> rogpeppe1: done.
[14:42] <rogpeppe1> rvba: thanks
[14:58] <hazmat> is fwereade on vacation ?
[14:59] <mgz> hazmat: yes, till thursday
[15:00] <ahasenack> does mongodb from precise work with juju-core, for the local provider story?
[15:00] <ahasenack> it looks like it doesn't support ssl
[15:00] <ahasenack> it's 1:2.0.4-1ubuntu2.1
[15:08] <dimitern> rogpeppe1, mgz: https://codereview.appspot.com/11666047/ - machiner uses api now
[15:11] <mgz> dimitern: looking
[15:19] <rogpeppe1> dimitern: reviewed
[15:19] <dimitern> rogpeppe1: thanks
[15:26] <rvba> rogpeppe1: btw, you'll note that my latest branch (to cope with gwacl's most recent changes) only touches test files.
[15:27] <rogpeppe1> rvba: cool. LGTM
[15:29] <rvba> rogpeppe1: ta
[15:31] <mgz> everyone hold off marking any mps as approved for a while
[15:31] <mgz> I'll give the okay when y'all can start landing again
[15:37] <dimitern> mgz: ok; thanks for the review btw
[15:42] <rogpeppe1> thumper: yo!
[15:42] <rogpeppe1> dimitern: fairly trivial CL: https://codereview.appspot.com/11560044
[15:47] <TheMue> rogpeppe1: lgtm
[15:47] <rogpeppe1> TheMue: ta
[15:48] <dimitern> rogpeppe1: will look a bit later, have to go out quickly
[15:48]  * dimitern bbiab
[15:48] <rogpeppe1> dimitern: np
[15:51] <mgz> okay, can mark mps for landing again now
[15:52] <mgz> everyone will want to update gwacl
[15:57] <rogpeppe1> any other takers for a small review (more Go- than juju-centric)? https://codereview.appspot.com/11560044
[16:02] <marcoceppi> Just wanted to drop by and let you guys know about this: https://bugs.launchpad.net/juju-core/+bug/1203795 It's blocking local provider on LTS
[16:02] <_mup_> Bug #1203795: mongodb with --ssl not available in precise <juju-core:Confirmed> <https://launchpad.net/bugs/1203795>
[16:03] <mgz> talk to jamespage :)
[16:04] <marcoceppi> mgz: well my first thought is to just upload the raring version of mongodb to ppa:juju/devel and call it a day
[16:14] <rogpeppe1> niemeyer: trivial change to mgo: https://codereview.appspot.com/11419045
[16:34] <rogpeppe1> another small CL (just copying some code from goamz) if anyone fancies a review: https://codereview.appspot.com/11680043
[16:35] <rogpeppe1> mgz: this is what i was referring to in a reply to you earlier
[16:35] <rogpeppe1> mgz: assuming this goes in, i'll go and refactor the attempt loop code to use AttemptStrategy now.
[16:36] <mgz> rogpeppe1: ta
[16:39] <niemeyer> rogpeppe1: What is the implements command?
[16:40] <rogpeppe1> niemeyer: it tells you which interfaces are implemented by which types.
[16:40] <niemeyer> rogpeppe1: Should it be fixed instead to behave as the compiler does?
[16:40] <rogpeppe1> niemeyer: that should probably be fixed indeed
[16:40] <rogpeppe1> niemeyer: but changing to use *file seems reasonable - i certainly found it quite surprising when i saw that that actually worked
[16:43] <niemeyer> rogpeppe1: It's just style, but sure
[16:43] <rogpeppe1> niemeyer: i think it might be the go/types package that's broken here. not entirely sure.
[16:44] <rogpeppe1> niemeyer: yeah, looks like it.
[16:44] <niemeyer> rogpeppe1: It's changed
[16:44] <rogpeppe1> niemeyer: ah, i should try go getting it again
[16:48] <rogpeppe1> niemeyer: hmm, yes, the implements command is now broken
[16:48] <rogpeppe1> niemeyer: against code.google.com/p/go.tools/go/types anyway, which i think is the correct path
[16:49] <rogpeppe1> niemeyer: thanks
[16:49] <niemeyer> rogpeppe1: Cool, glad the change makes it happier
[17:01] <rogpeppe1> niemeyer: yeah, go/types still isn't fixed in that respect.
[17:01] <rogpeppe1> niemeyer: BTW: https://github.com/dominikh/implements
[17:08] <dimitern> rogpeppe1: reviewed
[17:08] <dimitern> rogpeppe1: https://codereview.appspot.com/11560044/
[17:09] <rogpeppe1> dimitern: thanks
[17:31] <rogpeppe1> dimitern: i'd appreciate a review of https://codereview.appspot.com/11680043/ if you've a mo - it's just code moving
[17:31] <rogpeppe1> right, i need to go
[17:32] <rogpeppe1> g'night all!
[17:33] <dimitern> rogpeppe1: g`night; will look
[20:43]  * thumper just prepaid for an ubuntu edge phone
[20:47]  * thumper needs another +1 on https://codereview.appspot.com/11561044/
[20:47] <thumper> mramm: you available?
[20:47] <mramm> yep
[20:48] <mramm> need a couple min, just got off a long flight but basically available...
[20:49] <mramm> also, hotel network here sucks so we will have to see how it all works out.
[20:57] <mramm> but trying a google hangout now
[20:57] <mramm> https://plus.google.com/hangouts/_/6d40ef8bc434ba92987e924694fb92cffb9c7e7c?hl=en
[21:36] <wallyworld> thumper: you still otp?
[21:49] <arosales> any folks try hp cloud with the recent juju-core release?
[21:59] <wallyworld> arosales: i haven't. issues? it would be great if we had an account to test with :-)
[22:01] <arosales> jcastro and m_3 reporting it is not working atm
[22:01] <arosales> wallyworld, I am verifying
[22:01] <wallyworld> ok, let me know if i can help
[22:02] <wallyworld> arosales: btw, i'm about to land a tool to do image metadata validation. hopefully today. will let you and the guys know
[22:04] <arosales> wallyworld, thanks that would be great
[22:05] <arosales> wallyworld, do you know if the tools were updated on hpcloud to match 1.11.3? or is 1.11.0 tools sufficient?
[22:06] <wallyworld> arosales: you will need the 1.11.3 tools. i do not know if they were updated. listing the public bucket contents will show if they were
[22:07] <arosales> wallyworld, ok I will check.  currently bootstrapping on hp cloud I get:
[22:07] <arosales> http://pastebin.ubuntu.com/5902079/
[22:09] <wallyworld> arosales: so the 1.11.3 tools are missing. i'd like to see a --debug bootstrap to get more ides why it is failing
[22:09] <wallyworld> you could also try with --upload-tools
[22:09] <m_3> arosales: might be a bucket issue
[22:09] <arosales> wallyworld, ya I don't see any 1.11.3 tools on hp cloud
[22:10] <arosales> m_3, what error were you getting?
[22:10] <wallyworld> we should add that to th relesase process
[22:10] <m_3> 1.11.2 works fine in hp, but 1.11.3 gets some auth grumping
[22:10]  * m_3 looks
[22:10] <wallyworld> i can't off hand think of what may have changed
[22:10] <m_3> dev:~/talks/now $ juju bootstrap -e go-hp
[22:10] <wallyworld> to cause that
[22:10] <m_3> error: cannot create bootstrap state file: cannot get endpoint URL without being authenticated
[22:11] <arosales> wallyworld, http://pastebin.ubuntu.com/5902083/
[22:11] <wallyworld> ah, i know where the issue might be. can you do a bootstrap --debug ?
[22:11] <arosales> bootstrap --debug above ^
[22:12] <arosales> wallyworld, also any reason 1.11.3 tools are missing from hpcloud?
[22:13] <wallyworld> arosales: they just weren't copied there as part of the release process i'm guessing
[22:13] <wallyworld> so our release process needs to be updated
[22:14] <wallyworld> i'll try bootstrapping on canonistack to see if i get the same error
[22:14] <arosales> wallyworld, if you a pointer to the 1.11.3 tools I can upload to hp
[22:15] <wallyworld> arosales: http://juju-dist.s3.amazonaws.com/
[22:15] <wallyworld> or you can use sync-tools
[22:15] <wallyworld> juju help sync-tools
[22:16] <arosales> sync-tools upload to an arbitrary bucket?
[22:17] <thumper> wallyworld: nope, around now
[22:17] <thumper> although need to go let the dog in
[22:17] <wallyworld> thumper: ok, just talking to some folks about hp cloud issues
[22:17] <wallyworld> with 1.11.3
[22:19]  * arosales uploading the precise i386/amd64 tools to the hp bucket
[22:19] <thumper> wallyworld: ok, did you want to chat?
[22:20] <wallyworld> thumper: yeah, i had a meeting about the addressability issues with rodger and martin and asked martin to send an email which he did. i just wanted to touch base on that
[22:20] <thumper> ok, I need to read it
[22:20] <thumper> been looking at the ubuntu edge stuff
[22:20] <wallyworld> ok. i need to do that too
[22:20] <wallyworld> $32M is a big ask
[22:22] <wallyworld> arosales: fwiw, i just bootstrapped in canonistack with current trunk, which should not be too much different to 1.11.3
[22:22] <wallyworld> so hopefully using the current tools will work
[22:27]  * arosales retrying hpcloud with updated tools
[22:29] <arosales> wallyworld, still getting http://pastebin.ubuntu.com/5902120/ with updated precise tools
[22:30] <wallyworld> arosales: hmmm. i know where in the code it's happening. but without an account to debug with, it will be hard to find out why, since it works on canonistack
[22:32] <arosales> wallyworld, I can get you a sub on my account for testing
[22:33] <wallyworld> arosales: that would be f*cking amazing
[22:33] <arosales> wallyworld, I will pm you the details
[22:33] <wallyworld> thank you. now we can smoke test etc before release
[22:38] <wallyworld> thumper: i have an errand to take care of, will ping you in a bit
[22:39] <thumper> wallyworld: ack, talking with hazmat
[23:06] <arosales> wallyworld, fyi no saucy amd64 juju-tools on amazon
[23:07] <arosales> for 1.11.3 that is
[23:12] <wallyworld> arosales: i'm not sure what the saucy status is. dave cheney would know a bit more
[23:13] <arosales> wallyworld, you should have access to hp cloud, let me know if you see the auth error
[23:13] <wallyworld> arosales: thanks. logging in now
[23:13] <arosales> wallyworld, I uploaded all the tools that amazon had for HP
[23:30] <wallyworld> arosales: what region are you using?
[23:32] <arosales> az1
[23:33] <arosales> wallyworld, ^
[23:33] <wallyworld> ok, thanks
[23:35] <wallyworld> arosales: right, i have reproduced the error. now to debug
[23:36] <arosales> wallyworld, sometimes that is half the battle
[23:37] <arosales> wallyworld, thanks for taking a look
[23:37] <wallyworld> indeed. i need to sort out why it didn't show up on canonistack
[23:38]  * arosales not sure on the delta between canonistack and hp
[23:39] <thumper> wallyworld: I'm likely to just merge this with your ok :-) https://codereview.appspot.com/11561044/
[23:40]  * thumper waits a bit longer for another +1
[23:40] <thumper> would be funny to land with "trivial"
[23:40] <thumper> :)
[23:40] <wallyworld> thumper: do it!
[23:41] <wallyworld> thumper: will talk to you later - i'm sorting out a critical hp cloud issue with the latest release for the guys at OSCON
[23:51] <thumper> wallyworld: np, I need to go to the gym anyway
[23:51] <thumper> and that is a *need*
[23:51] <wallyworld> of course
[23:51] <thumper> also I have an email to compose re: addressability
[23:54] <wallyworld> arosales: so something is resetting the openstack client's credentials, just got to find out what and why
[23:55] <arosales> wallyworld, ok thanks for taking a look
[23:55]  * arosales is available for testing
[23:55] <wallyworld> np. will let you know when i find the next bit
[23:55] <arosales> I may have to step away for dinner with the family but I will log back in
[23:56] <wallyworld> ok