/srv/irclogs.ubuntu.com/2014/09/22/#juju-dev.txt

bradmwallyworld_: fwiw juju 1.20.8 proposed works the same for me as 1.21-alpha1 did, for the disable-network-management thing is concerned.00:15
bradmwallyworld_: as in, I can get a juju bootstrap working00:16
wallyworld_bradm: that's good then  :-) thank for letting me know00:16
bradmI'm having some weirdness with the rest of the deploy, but we haven't really gotten this going before, so I'm not sure what the issue is00:18
wallyworld_ok, if you can pin it down to a specific issue, maybe we can help00:30
bradmwallyworld_: I'm leaning towards it being an issue with our preseed in maas, but thanks, will let you know if I think I'm seeing juju issues.00:36
wallyworld_ok00:36
menn0waigani: review for http://reviews.vapour.ws/r/70/ done00:44
waiganimenn0: thanks00:49
=== thumper-afk is now known as thumper
menn0waigani: so should I pick up another document to do the env UUID conversion for?01:48
menn0waigani: I guess I should wait for your services branch to land as it has some useful helpers01:48
waiganimenn0: I've replied to your comments but not published them, should have the next pr up soon. Should I publish my comments now anyway?01:49
davecheneywaigani: wait til you have responded to them with code01:49
davecheneyotherwise you'll confuse other01:49
menn0waigani: what davecheney said01:49
menn0waigani: in the meantime I'll pick out the next one01:50
menn0and start figuring out what needs to happen01:50
davecheneythumper: ready when you are01:57
thumperdavecheney: ok01:57
menn0thumper: : I'm getting a panic in environInfoUserTag when running juju status against an env bootstrapped with trunk on Friday02:17
thumpermenn0: otp, with you soonish02:17
menn0thumper: k02:18
menn0waigani: once we've done the env UUID work for units and machines we should then do the statuses collection. The "global keys" used there need a env UUID prefix.02:23
waiganimenn0: how do I update rbt?02:23
menn0waigani: rbt post -r <review number>02:23
menn0waigani: rbt post -u will work too, but only if you haven't rebased02:24
waiganithought it was smart enough to remember, I just made a new pr accidentally02:24
menn0waigani: nope02:24
waiganimenn0: http://reviews.vapour.ws/r/7002:25
menn0waigani: looking02:25
menn0waigani: didn't hit publish?02:26
waiganiwhat?02:26
waiganioh ffs...02:26
waiganinow I get an 500 server error02:27
menn0waigani: just do it from the web interface02:27
menn0if you've uploaded a new diff there will be a publish button02:27
waiganiyep I hit it and I get a 500 err02:27
menn0you could have also passed -p to rbt post to have it publish immediately02:27
menn0waigani: awesome02:28
menn0waigani: that's not something I have seen before02:28
menn0waigani: I've got my 1:1 now anyway02:28
waiganiericsnow: coded the easter egg just for me ;)02:28
waiganiERROR: Could not reach the Review Board server at https://reviews.vapour.ws/02:28
waiganimenn0: it's uptodate on github02:29
menn0waigani: can you get to the site at all?02:29
waiganimenn0: yes02:29
menn0odd02:29
waiganimenn0: https://github.com/juju/juju/pull/80202:30
waiganimenn0: did you get my replies to your comments?02:30
menn0yep02:31
menn0waigani: actually I can see an updated diff on RB now02:31
waiganiis the right one? I still get the publish button and 500 every time I click it?!?02:31
waiganiokay, looks like the right diff is up. So what is with this publish button then?02:33
menn0well it seems to have some of the changes I brought up02:33
menn0waigani: what happens if you refresh the page?02:33
menn0waigani: does the button go away?02:33
waiganimenn0: nop02:33
menn0strange02:33
waiganiI'm in perpetual draft - a draft that everyone can see...02:34
menn0waigani: hey there's still lots of cases where DocId should be getting used instead of called idForEnv02:34
waiganimenn0: okay, I'll do another sweep02:34
menn0waigani: an idea: try removing the review request you accidentally added (mark it as Discarded)02:34
thumpermenn0: there now,02:34
menn0runtime.panic(0xd79660, 0x1bc2aa8)02:38
menn0/usr/lib/go/src/pkg/runtime/panic.c:266 +0xb602:38
menn0github.com/juju/juju/juju.environInfoUserTag(0x0, 0x0, 0xc2101664c0, 0xc210145ba0, 0x9, ...)02:38
menn0/home/menno/go/src/github.com/juju/juju/juju/api.go:230 +0x2a02:38
menn0github.com/juju/juju/juju.funcĀ·003(0xc210165480, 0x0, 0x0, 0x0, 0x0)02:38
menn0/home/menno/go/src/github.com/juju/juju/juju/api.go:168 +0xc402:38
menn0github.com/juju/utils/parallel.funcĀ·005()02:38
menn0/home/menno/go/src/github.com/juju/utils/parallel/try.go:135 +0x4102:38
menn0created by github.com/juju/utils/parallel.(*Try).loop02:38
menn0/home/menno/go/src/github.com/juju/utils/parallel/try.go:86 +0x9f02:38
menn0that's for thumper :)02:39
waiganimenn0: I did change all the DocIDs, but files were not saved so didn't get added02:39
menn0waigani: cool. in 1:102:39
waiganithumper: are we doing standup?03:09
waigani1:1 or whatever it's called03:09
thumperwaigani: yes, just otp with menn0 and finishing up03:09
waiganimenn0: otp03:54
menn0waigani: kk03:54
* thumper goes to put the coffee machine on03:55
menn0waigani: http://reviews.vapour.ws/r/70/04:21
waiganimenn0: how do I look at the original diff you commented on?04:29
menn0waigani: There's a slider at the top of the diff viewer which lets you control the diff that's shown04:30
waiganithanks04:30
menn0waigani: you can also click on the title from the Reviews UI04:30
menn0waigani: (the page which just lists the review comments together)04:30
thumperwaigani: review done04:55
waiganithumper: thanks04:55
thumperwallyworld_: could I get you to review axw's branch: http://reviews.vapour.ws/r/62/diff/#05:03
thumperwallyworld_: I'm not comfortable with the tools storage05:03
wallyworld_sure05:03
thumperand I think I may miss something05:04
wallyworld_np05:04
thumpercheers05:04
thumperI did the other one :)05:04
wallyworld_\o/05:04
axwthanks05:04
wallyworld_thumper: last day today, off tomorrow to central queensland05:04
thumperwallyworld_: have a nice holiday pre-sprint05:04
thumperwallyworld_: and I'll see in in Belgium05:05
wallyworld_thumper: will do, scary bit is a gotta get straight on a plane when we get back so i gotta pack for the sprint this afternoon05:05
thumperhaha05:05
wallyworld_it's a 5 hour drive back to brisbane, then to airport, hope there's no delays05:06
thumper:)05:08
wallyworld_axw: i just looked at http://reviews.vapour.ws/r/72/ - was that bug raised earlier really a critical regression then?05:20
axwwhich bug?05:20
wallyworld_in the topic - 137160505:20
wallyworld_i marked it as Invalid05:20
axwah, missed it05:20
axwlooking05:20
wallyworld_as i thought that HP Cloud should have a had a keystone product-stream endpoint05:20
wallyworld_well, i'm sure it did, but may i misremember05:21
wallyworld_if i'm wrong, we'll need to reopen05:21
axwwallyworld_: even if it's meant to be there on HP, it won't be in all OpenStack installations05:22
axwso yes, it's a real bug/regression05:22
wallyworld_axw: ok, i'll reopen05:22
wallyworld_for some reason i thought it would only kick in for CPCs05:22
wallyworld_axw: in upgradejuju_test, why is there a change to  append /tools to the tools-metadata-url? this seems like an error05:28
wallyworld_the url should just be the base url05:28
wallyworld_hmmm, maybe not05:29
axwwallyworld_: pretty sure it didn't work without it. just a moment, will need to rewind05:29
wallyworld_axw: igmore me, i think it is needed05:30
wallyworld_but surprising that the original code didn't have it05:30
wallyworld_maybe there was code to append /tools if it wasn't there at one point05:30
axwwallyworld_: I think in the old code, that tools-metadata-url was just being skipped over and it was using provider storage05:30
axwnotice I took out the MustUpload... calls05:31
wallyworld_haven't got to that bit yet05:31
axwline #316, just below05:31
wallyworld_axw: just came across the deletion of the assertMirrors test - for our CPCs, like AWS, HP Cloud etc, provider storage will still be used for mirroring the tools local to the cloud05:39
wallyworld_so we will still need a test of some sort for that05:39
axwwallyworld_: I'll write a new more targeted test05:43
wallyworld_axw: awesome, ty05:43
axwjust for sync.StorageToolsUploader05:43
wallyworld_axw: also, can you double check that there's still tests which check that tools can be downloaded from a local mirror? there will be simplestreams ones, but i can't recall if there are provider ones for wc2 or openstack05:45
wallyworld_great that the retries bool is gone05:45
axwwallyworld_: I don't recall seeing any tests of that sort in the providers05:46
wallyworld_ok, i don't recall off hand what's there05:46
wallyworld_i just wated to be sure we weren't reducing test coverage of the mirrors stuff05:46
axwwallyworld_: pretty sure I didn't remove any mirror reading tests, I'll double check tho05:47
wallyworld_ok, ta05:47
wallyworld_it's got a fairly high risk of breaking something if we get it wrong05:48
wallyworld_since mirrors are used for aws etc05:48
waiganithumper, menn0: http://reviews.vapour.ws/r/70/05:53
thumperwallyworld_, menn0: http://reviews.vapour.ws/r/74/diff/05:53
thumperwaigani: I'm being dragged away, will look in the morning05:53
thumperwallyworld_: this is a critical bug fix05:54
thumperwallyworld_: I broke it last week05:54
waiganithumper: okay05:54
wallyworld_thumper: i get a 40405:54
thumperreally?05:54
wallyworld_ah, not anymore05:54
waiganithumper, menn0: I've made all requested changes - no push back. I'll run all the tests tonight05:54
wallyworld_maybe i was too quick05:54
thumperwallyworld_: gah... who do I choose for a review?05:55
thumperreviewer05:55
wallyworld_for the 74?05:55
thumperdone05:55
thumperI hadn't published the review05:55
thumpergeez05:55
* thumper comes back later05:55
=== thumper is now known as thumper-eod
menn0waigani: that PR is looking good. make sure you test an actual upgrade from 1.20 to your latest to make sure the upgrade step actually does what you expect06:07
waiganimenn0: good advice - I'm currently running make test - so far so good06:07
menn0also I've just found one more problem... sorry. see the review06:07
waiganimenn0: fixed. I've hit some failing tests. So I'll push up the fix with the next round.06:11
=== uru_ is now known as urulama
TheMuemorning07:32
jammorning TheMue07:38
jamfwereade: I have a mongo question when you're around07:38
wallyworldaxw: if you had time to look at http://reviews.vapour.ws/r/73/ that would be great, i have to pop out but will be back later07:57
axwwallyworld: sure07:58
wallyworldty07:58
fwereadejam, oops, sorry08:01
fwereadejam, (I'm here)08:03
voidspacemorning all08:07
TheMuevoidspace: heya, all preparations for your trip done?08:12
voidspaceTheMue: my visa arrived last week08:16
voidspaceTheMue: so just the packing to do :-)08:16
voidspaceTheMue: PyCon UK this weekend was fun too - and I got to practise my talk08:16
voidspaceTheMue: although the one for PyCon India needs to be 50% longer - so still some work to do08:16
TheMuevoidspace: sorry, had phone, insurance company because of my daughters :D08:34
TheMuevoidspace: India is fantastic, I enjoyed my -- too short -- time there08:34
voidspaceTheMue: it did occur to me that "treat your servers as cattle" is not the right metaphor for an Indian audience...08:36
voidspacejam: I spent some time at PyCon UK with Wes Mason from online services08:39
voidspacejam: he's the replacement for Sidnei on that team - and he's a mongo expert08:40
voidspace(he hates it...)08:40
voidspacejam: he's willing (beuno permitting) to give me or us some time looking at replicasets at some point08:40
TheMuevoidspace: what does he hate? mongo?08:42
voidspaceTheMue: yes :-)08:42
TheMuevoidspace: oh08:43
voidspaceTheMue: but he knows a lot about it08:43
jamvoidspace: sounds good08:43
wesleymasonvoidspace: TheMue: jam: there is a certain correlation between my experience and levels hate08:46
voidspacewesleymason: I assumed that was the case...08:46
jamwesleymason: where else is it being used? I thought U1 was using Cassandra, not Mongo08:46
wesleymasonjam: push are using it for queues, but my experience is from previous workplace08:48
jamwesleymason: maybe I can ask you my mongo question. If you do: "servicesCollection.Find(bson.D{}).All(&sdocs)" is there any particular order that the results would be in?09:13
jam(in mongo, they seem to always come back in alphabetical sorted, in Tokumx I'm seeing them come back in the order they were inserted, I just wanted to confirm that the test is wrong)09:14
wesleymasonjam: unless specified it's called "natural order", which is 99% of the time insertion order, but that can be different depending on factors, for example if data were restored from a backup it could be sorted by datetime encoded inside the _id ObjectId09:17
jamfwereade: ^^ if you have an answer you're welcome to respond09:17
jamwesleymason: well, I'm seeing "insert(wordpress), insert(mysql), Find() => mysql, wordpress" for Mongo and wordpress,mysql for Tokumx09:17
jamnow, the test claims: // Check the returned service, order is defined by sorted keys.09:18
jambut I don't see any sorting anywhere09:18
wesleymasonjam: have you tried the find on the mongo repl just to make sure there's nothing happening in the driver?09:19
jamwesleymason: well, same driver, I believe09:19
fwereadejam, I think if we care about order we should explicitly Sort()09:19
jamfwereade: I don't think we care for State.AllServices() do we ?09:20
fwereadejam, IMO, no09:20
jamI think the test happened to get a sorted order and thought it was guaranteed09:20
jamand we should be Sorting in the test09:20
fwereadejam, agree09:20
wesleymason^ this, and if it's really important sort on a key other than _id, as that can be recreated and not always guaranteed to have the original datetime09:20
jamwesleymason: so it would appear that my data was backwards. Toku is returning in sorted order, Mongo was returning in insertion order. Anyway, fixing the test09:26
wesleymasonjam: that makes MUCH more sense :D09:28
jamwesleymason: yeah, I think Toku's "fractal index" and mvcc means that it ends up sorting on insert09:29
jamhttp://reviews.vapour.ws/r/76/diff09:54
jamthumper-eod: or wwitzel3 ^^09:55
jamor fwereade^09:55
fwereadejam, LGTM09:56
axwwallyworld: not really sure why the bot is barfing on my branch. I think it must be running really close to the line on /tmp usage, and I tipped it over with the changes to how tools are build09:58
axwbuilt*09:58
axwgotta make dinner, will take another look later09:58
jamaxw: your branch addresses bug #https://bugs.launchpad.net/juju-core/+bug/137160509:59
jam?09:59
mupBug #1371605: HP Bootstrap fails: no endpoints known for service type: product-streams <bootstrap> <ci> <hp-cloud> <regression> <streams> <juju-core:In Progress by axwalk> <https://launchpad.net/bugs/1371605>09:59
axwjam: yes, amonst other things. if I can't land it soon I'll pull out the fix10:16
axwcan I get a review on http://reviews.vapour.ws/r/77/ please someone? fixes CI blocker10:28
=== allenap_ is now known as allenap
jamTheMue: voidspace: I'm going to be late to standup, and dimiter is out today, so probably you two can just chat with eachother about what's going on and have a short standup, since I've talked with you both10:40
voidspacejam: TheMue: cool10:40
TheMuejam, voidspace: yep, sounds fine to me10:44
TheMuevoidspace: I'm hanging out now ;)10:47
voidspaceTheMue: omw10:47
=== fabrice is now known as fabrice|lunch
wallyworldaxw: lgtm10:54
voidspacemgz: ping10:56
axwwallyworld: thanks11:07
wallyworldnp11:07
mgzvoidspace: yo11:33
voidspacemgz: sorry, I thought the bot wasn't working11:41
voidspacemgz: but we were actually blocked on a critical bug I hadn't noticed11:41
=== fabrice|lunch is now known as fabrice
mgzvoidspace: I'm just trying to see if I can open trunk11:45
mgzbut andrew's change hasn't made it through the testing yet11:46
hazmatjam, ping12:30
natefinchfwereade, perrito666: we should talk about charm sync.  I have a little time right now, but will likely get interrupted in 20-ish minutes... but I know it gets late fast on the other side of the pond, so want to talk whenever is good for you, William.13:03
perrito666hey hi natefinch13:04
perrito666hi fwereade13:04
fwereadeperrito666, natefinch: hey guys13:04
fwereadenatefinch, how long will your interruption be, do you think?13:05
fwereadenatefinch, it's only 3pm for me, but in 90mins I will be going into meeting mode for the rest of the day13:05
perrito666fwereade: ouch, I hope "rest of the day" doesn't mean until midnight13:06
natefinchfwereade: probably 20-ish minutes of disruption.  I think we can at least get a good start now if you like13:06
fwereadenatefinch, perrito666: ok, sgtm, would you start a hangout and I'll be there in <5?13:06
natefinchhttps://plus.google.com/hangouts/_/canonical.com/moonstone?authuser=113:07
axwwallyworld: I have nfi what your email says, because my pgp key is invalid :)13:35
wallyworldaxw: just letting you know the tools stream branch has landed in trunk13:35
axwokey dokey13:35
hazmatquite a few yummy things landed in trunk13:36
hazmataxw, so the provider storage removal is complete?13:36
axwhazmat: *very* close to, but not quite13:36
hazmatwallyworld, the --to on ensure-availability should also bring support for manual providers?13:36
axwbackups still relies on it13:36
axwhazmat: (re --to): eventually it should, but currently "ssh:" is all handled CLI-side13:37
hazmataxw, fair enough.. sounds like its enough though that a  non storage providing provider could be made13:37
hazmataxw, well --to an existing machine shouldn't need the ssh.. its a pointer to an env machine13:38
axwhazmat: after my next branch, you could provide a dummy Storage() method on Environ and 99.9% of Juju would work13:38
hazmatdon't really need to --to=ssh:13:38
hazmataxw, awesome13:38
wallyworldhazmat: ensure-availability --to nominally uses mass names, like is done with bootstrap13:38
wallyworldbootstrap --to13:38
hazmatbummer13:39
wallyworldhazmat: the placement directive just gets passed through as is to the provisioner13:39
hazmatwallyworld, if it took env machine ids, then it would work there as well.. i thought people could already specify maas-name via --constraints on ensure-avail13:39
wallyworldthat's what the landscape guys wanted13:39
axwthat would involve promoting machines from non-state-server, which is something we don't do atm13:40
wallyworldyep13:40
hazmatbtw.. found a nice cli based git gui.. tig13:40
hazmathttp://jonas.nitro.dk/tig/13:40
wallyworld"nice" and "git" often don't go together13:40
hazmatwallyworld, its working for me, i needed a better browsing interface for keeping up.. and this one does the trick for me. tig --first-parent to browse merges and a custom external command to do proper diff (per juju workflow) on merge commits.13:42
hazmatbut yeah.. git tooling is relatively esoteric compared to bzr13:42
wallyworldyep13:43
hazmatbut i'll take the speed anyday ;-)13:43
wallyworldbzr is not reaaly slow nowadays13:43
hazmataxw, so basically altering machine jobs post creation and updating stateServers 'e' doc for votingids stuff13:43
hazmatwallyworld, for net ops.. git is still significantly faster for me13:44
wallyworldfairynuff13:44
hazmatkatco, re format=oneline, great stuff.. but i wonder if the name shouldn't just be line.. cause its not like oneline of output.. and its shorter.13:45
axwhazmat: I forget what exactly we don't handle. it won't work at all on Azure, for example, because state servers are bound to the same cloud service13:45
wallyworldhazmat: conceptually we can change a machine's jobs, but the plumbing is not quite there yet, needs a bit of work13:45
hazmataxw, oh.. that problem child ;-)13:46
katcohazmat: i was leaning on feedback from the spec. that is fine with me as long as everyone agrees.13:46
axw:)13:46
katcohazmat: i'm going to focus on landing the tabular and summary formatters, and then we can circle back on the "oneline". can you leave some feedback on the spec, and maybe ping marco et. al.?13:48
hazmatkatco, sure13:48
katcohazmat: ty, sir. good suggestion.13:48
voidspacejam: so you can ask if the -short flag is on. So CI tests could skip if short is on.13:53
voidspacejam: making the default developer invocation to use short, and CI to stay unchanged13:53
katcowhat's the eta of the trunk landing being cleared now that the blocker is fixed?14:00
ericsnownatefinch, wwitzel3, perrito666: standup?14:01
perrito666aghh amazon not having enough machines again14:02
wwitzel3natefinch: ping14:03
=== ev__ is now known as ev
=== fabrice is now known as fabrice|kanban
mgzupdate for everyone on trunk landiness status:15:07
mgzblocking bug has been fixed by andrew, but CI got stuck on a job over the weekend and it catching up on several revisions now15:08
mgzso, need to wait a little bit still for the change to go through verification and the get bug marked fixed so things can land again15:08
natefinchmgz: thanks15:10
=== fabrice|kanban is now known as fabrice
=== fabrice is now known as fabrice|family
hazmatis there a provider interface?15:49
hazmatah.. environs/interface.go EnvironProvider15:50
natefinchhazmat: would love to hear your thoughts on the process of writing a provider.  And definitely if you need any help with a DO provider, I'd be happy to offer whatever help I can (given that I haven;t writt+16:09
* katco is off to get her glasses adjusted. bbiab.16:09
natefinchwritten a provider, that may not be much ;)16:09
hazmatnatefinch, i need to convince DO to bake cloudinit into their packages atm. currently doing the email thing with them on it16:09
hazmats/packages/images16:10
natefinchhazmat: oh interesting, didn't realize that was missing16:10
hazmatnatefinch, they added userdata support to get coreos going.. and its the exact same interface as ec2.. we just need them to rebake their ubuntu images with cloudinit installed16:10
natefinchhazmat: sorta surprised we let people deploy "ubuntu" without cloudinit16:11
hazmatnatefinch, we don't generally control that16:14
jrwren_why don't they just use cloudimg?16:14
hazmatits not a cpc cloud, so we don't build the images16:14
hazmatno.. most non cpc clouds don't16:14
hazmatthe only public clouds using cloudimg are those that we push the image directly to their cloud images16:15
natefinchhazmat: I guess I figured cloudinit was one of those things we require for an image to be called "ubuntu"16:17
hazmatnatefinch, its not on desktop or ubuntu core16:17
hazmatie. its not even on most of the images we distribute16:17
hazmatgetting userdata/cloudinit support is generally one of the harder aspects of juju enablement for clouds that don't have direct support for it16:18
lazyPowerif anyone has time, we have a user that's discovered brokenness in our homebrew recipe build of juju: https://bugs.launchpad.net/juju-core/+bug/137255016:39
mupBug #1372550: juju metadata missing from brew juju 1.20.7 <papercut> <juju-core:New> <https://launchpad.net/bugs/1372550>16:39
jamhey hazmat /wave16:49
jamsinzui or mgz: the bot still thinks bug #1371605 is blocking trunk16:50
mupBug #1371605: HP Bootstrap fails: no endpoints known for service type: product-streams <bootstrap> <ci> <hp-cloud> <regression> <streams> <juju-core:Fix Committed by axwalk> <https://launchpad.net/bugs/1371605>16:50
* sinzui checks if test passed16:50
sinzuijam, the commit is queued to test16:51
jamsinzui: for 5 hrs ?16:51
sinzuijam 1. CI was stuck testing a single test over the weekend. 2. 1.20 always tests before devel16:52
hazmatjam, hey wanted to sync up on toku16:52
hazmatand also some discoveries in mongo trunk16:52
sinzuijam, I unblocked the stuck test 4 hours ago. I see 1.20 finishing its tests now16:52
jamhazmat: sure. I'm in a meeting, but I'm done in about 5 min.16:52
jamsinzui: so what is the process for unblocking trunk, it doesn't just check what the current blockers are, it checks them at the end of a test run?17:01
sinzuijam, I checks that the bug is marked Fix Released. We mark our bug fixed released when we see the test pass17:02
sinzuijam, this address the problem where a commit is made that does NOT fix the test17:02
mgzjam: it is somewhat painfully slow when it's a fix done at the start of a working day for us17:03
jammgz: I had hoped it was a bit more automated than requiring you guys to jump on it.17:03
sinzuimgz, jam., AWS is painfully show today. The slow tests are all trying to provision instances in AWS17:04
jamvacation/sickness means the dev team could be blocked for >24hrs17:04
mgzwell, the testing is automated, just getting a revision through review, landing, then ci tests takes several hours at best17:04
mgzand today has been much slower as curtis explained17:04
mgz(partly my fault, I wanted to land a 1.20 change to see if that was blocked as well, which is now taking queue priority when it shouldn't really)17:05
jamI guess we always have the JFDI hammer if we find you guys aren't responding.17:05
mgzjam: there's no reason that bugs can't be marked fixed by anyone17:06
jammarking it Fixed Released vs Fix Committed seems a bit of a stretch, but sure, if that is the actual flag17:07
jamI was told it was: https://bugs.launchpad.net/juju-core/+bugs?field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=CRITICAL&field.tag=ci+regression+&field.tags_combinator=ALL17:07
mgzit's just whether the policy of waiting for a CI run to verify a blocking bug is fixed to do that marking is helpful17:07
mgzjam: yeah, that got changed, which I hadn't gathered initially either17:08
mgzI think blocking all of trunk to do an ammendment to a landed change is generally a bad idea17:08
mgzresponse to blockers should be identify the broken change, back that out, reopen the bug/pr that landed it for the followup fix17:09
sinzuijam, sorry, I changed the rules a little over a week ago as an item from my meeting with alexisb , wallyworld , natefinch , and others. I failed to send an email explaining why we added Fix Committed as a blocking condition17:10
sinzuimgz, I will add ...revert the ci test if it was discovered to be changed, or fix the test if it is discovered to be wrong17:10
sinzuimgz, jam. 1.21-alpha2 started testing17:11
=== uru_ is now known as urulama
hazmatjam, still around.. my meeting went a bit late?18:03
hazmat..18:03
=== fabrice|family is now known as fabrice
=== abentley_ is now known as abentley
=== ChanServ changed the topic of #juju-dev to: https://juju.ubuntu.com | On-call reviewer: see calendar | Open critical bugs: None
waiganithumper-eod: it's bod20:38
waiganithumper-eod: did you get my email about parseTag - what id should it return?20:39
wallyworldsinzui: i see you've created a 1.20.9 milestone. can i target the apt pinning and tools streams bugs at that? are you going to release the 1.20.8 built last week and then build a subsequent 1.20.9?21:18
sinzuiwallyworld, don't hesitate to target to it21:18
sinzuiwallyworld, Even if 1.20.8 is reviled, we will still move on to 1.20.921:19
wallyworldok, will do21:19
sinzuiwallyworld, I don't think anyone will block 1.20.8. We are being polite and letting some say no21:19
wallyworldsinzui: ok, i'm off today till the sprint, andrew will backport the tools stream change. was my email about streams behaviour correct?21:19
sinzuiyes please, but wallyworld the promise for "moving" the dirs was this year, not this month21:20
wallyworldsinzui: the solution in my latest email doesn't require new dirs21:21
sinzuiwallyworld, we/my team can always make the index.json point to a locations we need21:21
wallyworldthe streams are encoded in the existing json files21:21
wallyworldsame dirs21:21
sinzuiwallyworld, rock, I just wanted to be clear that your plan for :released: :proposed: as stanzas in index.json was loved by many21:21
wallyworldsinzui: i hope it is because that's what i've implemented :-) seems to work well, and only requires you to generate the files, not any changes to the dirs as such21:22
wallyworldsinzui: one point - the mirrors file also has the :released:, :proposed: etc in it21:23
sinzuiwallyworld, oh! thank you for telling me. I had not noticed21:24
wallyworldsinzui: i hope that is ok, i think it makes sense21:24
sinzuiwallyworld, looks like I have a choice of many...21:24
sinzuibut now I recall Ben wanted just cpc-mirrors.json, so it will have all the stream names and index will point to it in each stanza21:25
wallyworldsinzui: so in that case, i think te implementation i did is correct - a single mirrors json file, containing different stanzas for each stream21:26
wallyworldsinzui: if you need tweaks, you can ask andrew; he's available till mid next week21:27
sinzuiwallyworld, thank you. I hope not to need anything more than time on my side of things21:27
wallyworldi hope so too21:28
wallyworldthe work is in trunk, should be backported over the next day or so21:28
wallyworld1.20.9 now has 3 bugs assigned21:28
wallyworldright, i have to go and drive for 6 hours to my first destination, see you in brussels21:29
katcowallyworld: wait till the last minute why don'tcha! ;)21:30
katcowallyworld: tc, have fun, and i'll see you in brussels!21:31
wallyworldkatco: i just wanted to make sure everything was sorted out :-)21:31
katcowallyworld: hehe21:31
wallyworldkatco: will do, see you then, have fun without me :-)21:31
katcowallyworld: hehe tc21:31
=== urulama is now known as urulama-afk
rick_h_thumper-eod: ping whe you've got time22:34
=== thumper-eod is now known as thumper
thumperrick_h_: otp right now22:35
rick_h_thumper: rgr when you have time22:38
waiganimenn0, thumper: http://reviews.vapour.ws/r/70/22:57
waiganidavechen1y: standup?23:01
thumperrick_h_: free now23:35
rick_h_thumper: rgr23:37
rick_h_thumper: calling ya23:37
menn0thumper, davechen1y, waigani: it looks like us non-manager types can't edit that spreadsheet23:43
waiganithumper: ^23:43
davechen1ymenn0: sad trombone23:53
menn0davechen1y, waigani: I'm just doing it in my own sheet which I'll send to thumper23:54
thumpermenn0: sounds good23:54

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