, no :)
<rogpeppe> dimitern: :)
<rogpeppe> dimitern: just it seem very quiet here atm
<dimitern> rogpeppe: LGTM, but I'm curious - why was that needed?
<rogpeppe> dimitern: just a test failure due to two times being different only in zone (we were using UTC, bson unmarshals as local) and i got fed up. i've wanted to make this change for ages :)
<dimitern> rogpeppe: quiet yes.. I'm tasked with making sure develop merges OK into staging though, so I haven't noticed :)
<perrito666> morning all
<zeestrat> Hey, when is 2.0.1 coming to the juju/stable PPA?
<dimitern> mgz: ping
<mgz> dimitern: yo
<dimitern> mgz: hey, I've been watching the last few CI runs on develop
<dimitern> mgz: any idea about the build errors?
<mgz> the last few?
<mgz> the earlier ones were from balloons changing the packaging branch
<mgz> but those should be gone with the latest builds?
<mgz> hm, something new
<dimitern> latest one still has a few: http://reports.vapour.ws/releases/4540
<mgz> also those results are misleading
<mgz> hardly anything actually ran
<mgz> there was talk about poking around with S3 on friday, I'll look and see what actually changed
<dimitern> ok
<dimitern> mgz: do you think we could merge develop into staging today, or we need a bless first?
<mgz> ideally we get a bless, but of the last 10 runs most have failed due to non-juju code reasons
<balloons> we do need a bless. I was hoping a PR would land so we'd get a testrun -- really nothing has landed?
<balloons> ohh, no, it landed.. I see, weird
<mgz> stuff has landed, we're stuck on the build/publish step
<mgz> of xenial ppc64 build at least is blocking things
<mgz> perhaps other stuff?
 * mgz goes to clean up ppc64el-slave
<mgz> which stilson are you today...
<mgz> hm, 05 isn't actually out of disk
<mgz> dimitern: I deleting a bunch of things from that machine and am trying a rerun of the ppc64 build job
<dimitern> mgz: +1
<mgz> that should unblock various things, obviously we have some config issues as well
<mgz> as the jobs that failed shouldn't run before publish I pr