/srv/irclogs.ubuntu.com/2019/08/27/#juju.txt

babbageclunkthumper: take another look at https://github.com/juju/juju/pull/10562 plz?01:18
thumperbabbageclunk: ack01:45
thumperbabbageclunk: lgtm with one minor change01:50
thumperadding a clock to the unit agent manifold config01:50
thumperthere are three other uses of clock.WallClock in that file.01:50
babbageclunkthumper: ok wilco01:54
* thumper starts looking at some of these intermittent failures02:06
* thumper wonders if there is some nifty scripting we could do to scrape jobs to determine frequency of intermittent failures02:06
ec0sounds like you need a job status prometheus exporter02:10
babbageclunkthumper: I keep meaning to write something to do that but getting distracted03:48
thumperbabbageclunk: yeah, understood03:49
babbageclunkwould be super useful though03:49
wallyworldhpidcock: when thumper is done with you.... https://github.com/juju/juju/pull/1056303:54
thumpercrap...04:23
thumpermy fix didn't04:23
* thumper pokes some more04:40
hpidcockwallyworld: looks good, few comments that's all04:50
wallyworldty04:50
wallyworldhpidcock: because the v3 CLI is strictly opt in, there's no need to be too verbose about reminding users what the v2 syntax is04:54
hpidcockwallyworld: yeah, I understand that, but I imagine at some point v3 won't be opt in. Was just trying to highlight that we should provide feedback when something is deprecated.04:56
wallyworldi can add a note to the help text for "juju run"04:58
thumperI think I have it now05:00
thumperover 200 concurrent successes without a failure and during a stress run of the entire test suite05:00
* thumper pushes05:00
thumperwallyworld: https://github.com/juju/juju/pull/1056405:03
wallyworldok05:03
wallyworldthumper: lgtm05:15
thumperwallyworld: ta05:15
thumperlanding that branch, and EOD05:44
thumperlater peeps05:44
stickupkidjam, got a sec?09:35
stickupkidjam, scratch that, i've worked it out09:40
achilleasacan someone do a quick CR on https://github.com/juju/charm/pull/290?10:11
achilleasajam: ^^ is the fix for #184110510:12
mupBug #1841105: panic: runtime error: invalid memory address or nil pointer dereference <juju:In Progress by achilleasa> <https://launchpad.net/bugs/1841105>10:12
manadartachilleasa: Looking.11:00
manadartachilleasa: approved.11:03
achilleasamanadart: can you also please check https://github.com/juju/juju/pull/10565 (brings the charm.v6 changes to juju) and try the QA step?11:18
manadartachilleasa: Sure,11:28
hmlmanadart: review please: https://github.com/juju/juju/pull/1055512:35
manadarthml: Looking.12:44
jamguild in 912:51
manadarthml: What provider are you using to add subnets?14:21
hmlmanadart:  :-)  I used maas, but the call failed because the subnets were already created.  so i made sure that the correct facade versions were being used and the errors stayed the same.  i’ve since learned that aws might work there better.14:22
manadarthml: OK, yeah. I was using AWS.14:29
hmlmanadart: you had no issues bootstrapping a aws on a develop branch today?15:12
stickupkidrick_h, omitempty won't work for us, as the bundlechange api doesn't work the way other apis work15:14
rick_hstickupkid:  doh, otp atm but let's table it then. We don't need to solve it until 2.715:41
rick_hstickupkid:  and go with the release for the bug affecting the customer please15:41
stickupkidrick_h, ok sounds good15:41
rick_hstickupkid:  and we can look into what it'll take to have bundlechanges behave like a real boy api15:41
stickupkidrick_h, https://github.com/juju/python-libjuju/pull/349 release bump16:01
rick_hstickupkid:  k, +1'd16:03
stickupkidrick_h_, ty16:03
manadarthml: If you are interested, I have started to put together https://github.com/juju/juju/pull/10566. It will accrue context as I push the other pieces up.16:21
hmlmanadart:  cool - will start to look16:21
=== hml_ is now known as hml
thumpermorning20:54

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