also likely CI driver code that sets $JUJU_HOME. Not that it can't be done but not at the flip of a switch.
<rogpeppe> jog: fair enough
<rogpeppe> jog: anyway, i hope the intermittent issue should have gone away now
<rogpeppe> jog: and deleting the cookie file should cause the CI to succeed OK
<rogpeppe> jog: well, at least to fix *that* issue :)
<rogpeppe> jog: you could always set JUJU_COOKIEFILE=$(tempfile)
<jog> that's that type of change I'm thinking of making in the short term
<jog> also are you going to make that a Warning?
<rogpeppe> jog: the reason i'm not sure about that is that i'm not sure of the best API for persistent-cookiejar. It seems kind of wrong to not give the caller any info about the fact that loading the cookie jar has failed, but the alternative is returning both a valid cookiejar *and* an error which also seems wrong
<rogpeppe> jog: for the time being, i might leave it as an error but if it causes further CI issues, i'll change it
<rogpeppe> jog: after all, if it hadn't been an error, we wouldn't have discovered this potential test cross-talk issue
<rogpeppe> jog: so it's not all bad :)
<mup> Bug #1511543 opened: Unhelpful error message when trying from a location with a full disk <juju-core:Triaged> <https://launchpad.net/bugs/1511543>
<axw> rogpeppe: gocov can merge profiles
<axw> rogpeppe: not aware of any others
#juju-dev 2015-10-30
<mup> Bug #1511589 opened: maas provider, hwclock out of sync means juju will not work <kanban-cross-team> <landscape> <maas-provider> <juju-core:New> <MAAS:New> <https://launchpad.net/bugs/1511589>
<rogpeppe> axw: how would i use gocov to merge coverage profiles? it's not clear from the README
<axw> rogpeppe: sorry, IIANM you can "gocov convert profile [profile...]". but it's going to give you gocov JSON output, if it's not clear
<rogpeppe> axw: so my aim here was to try and see the combined test coverage of juju/api when running the juju/apiserver/client and juju/api tests
<rogpeppe> axw: and i like the nice red-green line-by-line HTML output of the usu