=== pbek_ is now known as pbek
=== rharper` is now known as rharper
[15:48] <teward> are there any critical issues with arm64, armhf and ppc64el builders?  I had a few builds just 'fail' without any logs, or anything, so I can't debug those builds
[15:52] <cjwatson> teward: URLs please
[15:52] <teward> there'll be a load of them standby
[15:52] <cjwatson> But that usually means either network blip or crashed builder
[15:52] <cjwatson> Just one
[15:52] <cjwatson> I don't want to have to trawl through a hundred
[15:52] <teward> well, actually, not many... i have 3 is that OK?
[15:53] <cjwatson> three would be fine
[15:53] <teward> https://launchpad.net/~teward/+archive/ubuntu/nginx-devel-testing/+build/14376034 https://launchpad.net/~teward/+archive/ubuntu/nginx-devel-testing/+build/14376035 https://launchpad.net/~teward/+archive/ubuntu/nginx-devel-testing/+build/14376037
[15:53] <teward> they started, then just 'failed', no logs.
[15:53] <teward> i do note that everything's in a cleaning cycle again according to the build farm status page
[15:53] <teward> so not sure if that's a factor
[15:53] <cjwatson> hardly everything.  will sort in a bit.
[15:54] <cjwatson> 2018-02-20 15:37:47+0000 [QueryProtocol,client] Scanning bos02-ppc64el-007 failed with: Build returned unexpected status: 'BUILDERFAIL'
[15:54] <cjwatson> possibly just a network blip when the build was starting up.  please retry
[15:56] <teward> queued
[15:59] <cjwatson> seems fine now
[16:03] <teward> *shrugs*  It just gave me a small panic like a "Crap is everything broken now" kind of feel
[16:03] <teward> cjwatson: thanks
[19:01] <acheronuk> ppc64el builders don't look at well as they might? could they maybe be poked if that seems appropriate?
[19:05] <acheronuk> oh. waking up a little
[19:05] <cjwatson> done
[19:05] <acheronuk> ah. thanks.
[19:05] <acheronuk> :)