Hello, Sorry for being late to the party. > From: Jason A. Donenfeld <Jason@xxxxxxxxx> > Sent: 27 May 2022 22:05 > > 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://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab > .com%2Fcip-project%2Fcip-testing%2Flinux-stable-rc-ci%2F- > %2Fpipelines%2F549589225&data=05%7C01%7CChris.Paterson2%40ren > esas.com%7C0de8f5ed337148db7bcf08da4024905d%7C53d82571da1947e49c > b4625a166a4a2a%7C0%7C0%7C637892823031829365%7CUnknown%7CTWFp > bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVC > I6Mn0%3D%7C3000%7C%7C%7C&sdata=P8snmZjBO52JAyScIA4rWmFe > woxUstyBGl3%2Fvvn%2BC%2B4%3D&reserved=0 > > 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. Exactly that, thank you Jason. We had some issues with some of the labs going offline at the end of last week. A bit sneaky because I was on leave. It resulted in a big backlog in jobs which meant it took more then 2 hours for them to go through and the GitLab runner gave up. I've re-run the "failed" jobs and now we have lots of green ticks. Sorry for all the noise! Kind regards, Chris > > Jason
