=== chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [15:35] pitti, I'm curious why juju-core hasn't had an adt run after uploading to yakkety. It was pushed yesterday. Is there a longer delay, or is something else holding it? [15:38] balloons: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#juju-core [15:39] balloons: it's FTBFSing on powerpc; tests only run once it built everywhere and is installable [15:39] dh_auto_build: go install -v -p 1 -x -v github.com/juju/juju/... returned exit code 2 [15:39] doesn't look like a retry will help? [15:41] pitti, ouch.. It's weird that the xenial runs are happening now, though perhaps they won't show. That build error is do to a bug 1612713 [15:41] bug 1612713 in golang-juju-loggo (Ubuntu) "Please merge debian version of golang-juju-loggo-dev" [Wishlist,Triaged] https://launchpad.net/bugs/1612713 [15:41] we worked around it though -- the package should build fine; curious why ppc isn't [15:42] and sorry, I clearly missed the obvious build failure [15:43] pitti, however, you can see xenial has the same issue with ppc failed to build: https://launchpad.net/ubuntu/+source/juju-core/2.0~beta15-0ubuntu1.16.04.1. However, adt tests are running [15:44] http://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#juju-core doesn't complain about lack of powerpc indeed [15:45] balloons: right, not waiting until it built looks like a bug in the britney config (or code) for stables [15:49] pitti, so it's interesting we build for i386 and ppc as we don't target those [15:51] * pitti -> dinner, cu tomorrow [15:53] cheers pitti, ty!