[00:35] <michi_> robru: ping
[00:35] <robru> michi_: pong
[00:35] <michi_> Hi
[00:35] <michi_> https://requests.ci-train.ubuntu.com/#/ticket/1670
[00:35] <michi_> This failed autopkg test on vivid.
[00:36] <michi_> Nothing we can do about it.
[00:36] <michi_> Will this retry automatically, or do I need to kick the build?
[00:52] <michi_> robru: ?
[01:01] <robru> michi_: oh sorry
[01:01] <michi_> np :)
[01:01] <robru> michi_: it will retry forever until it passes
[01:01] <michi_> Cool.
[01:02] <michi_> Suggestion for improvement:
[01:02] <michi_> Why not add a link to the doc to the train page?
[01:02] <robru> michi_: if you rebuild you need to re approve
[01:02] <michi_> That way, I don't have to hunt around for the doc.
[01:02] <robru> michi_: to clarify, britney will re run but the autopkgtest won't
[01:03] <michi_> So, I don't need to do anything, right? It'll fix itself eventually.
[01:03] <robru> michi_: you need a core dev to retry the autopkgtest if you want that to run again without uploading a new package
[01:04] <michi_> Ah.
[01:04] <michi_> Where's the right place to ask?
[01:04] <robru> michi_: what is the failure? A failed autopkgtest won't retry. A non autopkgtest failure in britney will be re run every 15 minutes
[01:05] <michi_> Some package we depend on failed to install
[01:05] <robru> michi_: this channel is fine but it's a bad time of day, my usual guys are gone
[01:05] <michi_> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-vivid-ci-train-ppa-service-landing-016/vivid/i386/u/unity8/20160713_082711@/log.gz
[01:06] <robru> michi_: yeah that's in the autopkgtest you need a core dev
[01:06] <michi_> Is there a list of core devs somewhere?
[01:07] <robru> michi_: yes there is 😝
[01:07] <michi_> Pray tell, where? :)
[01:07] <robru> michi_: sorry I'm on mobile, Google the lp team there's a member list
[01:07] <michi_> OK, cool.
[01:08] <michi_> Thanks, found it.
[01:13] <robru> michi_: you're welcome
[11:00] <sil2100> Saviq: hey! So we proceed with the repowerd revert I guess?
[11:05] <cjwatson> Folk here may notice: we've just switched all ARM builds over to scalingstack.  arm64 will behave much the same way (except for not sometimes hitting the older Mustang builders), but armhf will now be built in 32-bit chroots on arm64 VMs.
[11:05] <cjwatson> With any luck the main thing you'll notice will be that armhf builds will generally be faster.
[11:06] <cjwatson> But if something goes wrong then it may be useful to know that the configuration change was made at 10:59 UTC today.
[11:18] <Saviq> sil2100, I'd say so, yes
[11:18] <sil2100> cjwatson: \o/
[11:24] <cjwatson> Also this means building armhf on 4.2 kernels rather than 3.2.
[17:19] <Trevinho> Publish failed: Unexpected upload at destination.