[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190207191611.GB30122@roeck-us.net>
Date: Thu, 7 Feb 2019 11:16:11 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, shuah@...nel.org, patches@...nelci.org,
ben.hutchings@...ethink.co.uk, lkft-triage@...ts.linaro.org,
stable@...r.kernel.org
Subject: Re: [PATCH 4.4 00/34] 4.4.174-stable review
On Thu, Feb 07, 2019 at 04:47:08PM +0100, Greg Kroah-Hartman wrote:
> On Thu, Feb 07, 2019 at 06:20:43AM -0800, Guenter Roeck wrote:
> > On 2/7/19 3:41 AM, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.4.174 release.
> > > There are 34 patches in this series, all will be posted as a response
> > > to this one. If anyone has any issues with these being applied, please
> > > let me know.
> > >
> > > Responses should be made by Sat Feb 9 11:30:10 UTC 2019.
> > > Anything received after that time might be too late.
> > >
> >
> > Build results:
> > total: 171 pass: 170 fail: 1
> > Failed builds:
> > x86_64:allyesconfig
> > Qemu test results:
> > total: 291 pass: 291 fail: 0
>
> Oh, and thanks for the very fast turn-around time.
>
No problem; all automatic.
If there is only one branch to build, it is quite fast. A single branch
takes ~90 minutes to build and test. Of course, that means if you push
{3.18..4.20} together, it takes at 9+ hours for the builds and tests to
complete, plus the additional time for master, next, and 3.16 if those
branches change as well. Since, thanks to California's outrageous
electricity costs, builds only start between 11:00pm and 4:00am PST,
results are often only available around noon the next day.
Guenter
Powered by blists - more mailing lists