[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YpE88Nwh/FQMyVVL@zx2c4.com>
Date: Fri, 27 May 2022 23:04:48 +0200
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Pavel Machek <pavel@...x.de>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Chris.Paterson2@...esas.com, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, linux@...ck-us.net, shuah@...nel.org,
patches@...nelci.org, lkft-triage@...ts.linaro.org,
jonathanh@...dia.com, f.fainelli@...il.com,
sudipm.mukherjee@...il.com, slade@...dewatkins.com
Subject: Re: [PATCH 5.10 000/163] 5.10.119-rc1 review
Hi Pavel,
On Fri, May 27, 2022 at 04:14:21PM +0200, Pavel Machek wrote:
> It seems we hit some problems, but I'm not sure if they are kernel
> problems or test infrastructure problems. Perhaps Chris can help?
>
> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/549589225
I'm clicking on everything red, and all the actual boot logs and
execution logs show things passing. Seems like this might be a CI issue?
I'm certainly very interested to learn about potential regressions
though if you can point to anything specific.
If I had to guess, it looks to me like the "lava" job finishes with
"result: pass", but never tells the controller properly, so it times out
waiting for the reply. Seems like CI infrastructure issue.
Jason
Powered by blists - more mailing lists