/srv/irclogs.ubuntu.com/2018/04/11/#juju-dev.txt

* thumper shudders as he builds 1.25 for some testing02:00
thumperbabbageclunk: next one https://github.com/juju/juju/pull/857304:51
thumperwallyworld: or you could... ^^04:51
* thumper goes to make a coffee04:51
babbageclunkyeah, share the love!04:51
* wallyworld gets coffee and then looks04:51
wallyworldbabbageclunk: actually, wanna chat briefly?04:51
wallyworldi hear you've living the dream04:52
babbageclunkwallyworld: yes please!04:55
babbageclunkin standup?04:55
babbageclunkso lonely05:00
babbageclunkwallyworld: actually I dropped out because it screws up the timing in the test05:03
anastasiamacwallyworld: thumper: PTAL   https://github.com/juju/juju/pull/857406:06
babbageclunkthumper: ok it gets weirder - it's not the manifolds, because they're never called (jujuconnsuite runs a minimal set of workers, but it doesn't run a dep engine). So it's actually something that gets imported by the worker/raft package (or worker/raft/rafttest)06:13
babbageclunkon the way to working it out now.06:13
anastasiamacthumper: also https://github.com/juju/juju/pull/8575 for deprecation on the flag06:14
thumperbabbageclunk: that's weird06:16
thumperanastasiamac: check failed for first PR06:17
anastasiamacthumper: yes, looking06:17
anastasiamacthumper: but doubt it's me - i changed only tests, and that should not have effected featuretets pkg at all.. mayb intermittent...06:18
wallyworldbabbageclunk: oh sorry, missed ping06:19
thumperwallyworld: I also updated presence PR06:19
wallyworldlooking. stupid quassel doesn't beep at me anymore06:20
thumperwallyworld: my quassel is struggling to beep too06:22
wallyworldyeah, so i miss a lot of pings :-(06:22
wallyworldespecially when i'm knee deep in code etc06:22
thumperwhy aren't you neck deep?06:22
thumperwhat is wrong with you?06:22
thumperwallyworld: I haven't squished commits yet so you can review the changes more easily06:23
thumperwallyworld: I'll squish before getting the bot to merge06:23
wallyworldty06:23
wallyworldi need to start doing that too06:24
thumperI'm done for the day06:24
wallyworldthumper: lgtm but from diff it appears there could be some newlines between methods in interface missing06:25
thumperwallyworld: I've not got newlines between every call06:25
thumperas I've grouped them06:25
thumperdo we really need newlines?06:26
wallyworldi think that's the expected way to do it06:26
wallyworldIIANM06:27
wallyworldYMMV06:27
thumperFFS06:27
thumperfine06:27
thumperwallyworld: some blank lines just for you06:29
wallyworld\o/ ty, still lgtm, land that sucker06:29
thumperyou didn't approve06:30
thumperoh, I see you did earlier06:30
thumperthanks06:30
wallyworldnp06:30
* thumper squishes and pushes06:31
thumperoh no!!!06:31
thumperI had a mouthful of coffee left in my cup06:31
thumperand it is now cold06:31
thumper:(06:31
=== frankban|afk is now known as frankban
manadartjam: As mentioned.09:16
manadartPR for supplying image metadata url and stream to containers: https://github.com/juju/juju/pull/857809:16
=== salmankhan1 is now known as salmankhan
jammanadart: reviewed10:16
manadartjam: Ta.10:19
jammanadart: I think I figured out why you can't use TearDownTest with gomock11:19
jamthe gc.C that is passed into TearDownTest is not the same object as the one passed into SetUpTest11:20
jammanadart: and you probably can't assume it is the same as the one during the test itself. :(11:20
jammanadart: I'm not positive about it. but if I just put a "c.Fail" in TearDownTest then I at least get "test fixture has paniced"11:23
jamwhich would at least 'fail' the test11:23
jammanadart: I *definitely* see that the object passed into SetUpTest is not the same object as passed into the Test itself.11:24
jammanadart: interestingly, if the test itself fails an assertion *during* the test, then it will report whatever the SetUpTest object got as failure messages11:25
jambut it can't fail on its own during TearDown. I'm a bit surprised at that, but it is what I'm seeing :(11:25
manadartjam: That explains the behaviour I saw when testing it. If I panic'd the test I could see some of the satisfied/unsatisfied calls reporting, but not when running finish in teardown.11:25
manadartjam: One option might be to write a TestReporter implementation, instantiate as a member of the suite in SetupTest, pass it to MockController. Then in TeardownTest we always know what we are getting and can Finish.11:28
jammanadart: well potentially a TestReporter that is a thunk, and then you call "SetThunk" in each place. but I don't think it would really give the behavior you want11:29
jammanadart: specifically, failures in assertions will get "Fixture has paniced()" rather than just treating it as a failed test.11:29
manadartjam: Yes I thought "oh, but wait" after I typed that :)11:30
jamballoons: can you hear me?12:33
=== freyes__ is now known as freyes
=== frankban is now known as frankban|afk
=== iatrou_ is now known as iatrou
=== icey_ is now known as icey
=== vern_ is now known as vern
babbageclunkthumper or wallyworld: could you please review this? https://github.com/juju/juju/pull/8571 Sorted out that weird failure.22:10
thumperbabbageclunk: ack22:10
thumperbabbageclunk: what was it?22:10
wallyworldsure soon, otp for a bit22:10
babbageclunkthanks!22:10
thumperbabbageclunk: what is your response to jam's question?22:11
babbageclunkIt was the import thing - importing the FSM from rafttest meant that some test fixture stuff came in too, and something in that lot did (something I'm not sure what) at package init time that meant that the hook commands ran slower.22:12
babbageclunkWould have been easier to find if golang allowed unused imports I think.22:12
babbageclunkthumper: not sure - need to think about it more carefully.22:12
thumperbabbageclunk: so the fix was what?22:13
babbageclunkmove the FSM out of rafttest into worker/raft.22:13
hmlshort review anyone?  https://github.com/juju/juju/pull/858222:16
hmlballoons: ^^22:16
hml:-)22:16
balloons:-) awesome heather!22:18
veeberswallyworld, thumper tiny addition to the charmrepo.v3 change22:19
veebershttps://github.com/juju/charmrepo/pull/12522:19
* wallyworld still otp :-(22:19
veebersack22:19
veebershml: lgtm22:24
hmlveebers: ty22:28
babbageclunkveebers: build's failing on yours?22:38
hmlwpk: why is timing a big issue here?  with the interfaces.py?22:38
hmlwpk: ifdown used to be before the interfaces.py was called22:40
veebersbabbageclunk: ah as per comment, test failure as charmstore.v5 still deps on charmrepo.v2 and thus fails. I could add charmrepo.v2 to charmrepo.v3 deps but that's mucky :-) Once this lands I'll propose a PR for charmstore.v5 (my branch will currently be the only thing depping on charmrepo.v3 right now)22:42
wpkhml: the main concern is to wait with anything that's hard to revert for as long as possible, we've seen weird failure modes and IMHO it's impossible to avoid them all, but we could do as much as we can to 1. avoid them 2. make the machine boot if we f.up22:42
babbageclunkveebers: oh sorry - didn't see that!22:43
veebershah I may have made it after you looked at the PR ^_^22:44
hmlwpk, veebers, balloons: will look at changing interfaces.py instead in the AM22:46
babbageclunkthat's my story and I'm sticking to it.22:47
wallyworldbabbageclunk: anastasiamac: standup?23:16
anastasiamacm standing m standing \o/23:18

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