Re: ❌ FAIL: Test report for kernel 5.11.19 (stable-queue, beb6df0c)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, May 12, 2021 at 12:16 PM Veronika Kabatova <vkabatov@xxxxxxxxxx> wrote:
>
> On Wed, May 12, 2021 at 3:22 AM Sasha Levin <sashal@xxxxxxxxxx> wrote:
> >
> > On Tue, May 11, 2021 at 09:43:50PM -0000, CKI Project wrote:
> > >
> > >Hello,
> > >
> > >We ran automated tests on a recent commit from this kernel tree:
> > >
> > >       Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > >            Commit: beb6df0ce94f - thermal/core/fair share: Lock the thermal zone while looping over instances
> > >
> > >The results of these automated tests are provided below.
> > >
> > >    Overall result: FAILED (see details below)
> > >             Merge: OK
> > >           Compile: OK
> > >             Tests: FAILED
> > >
> > >All kernel binaries, config files, and logs are available for download here:
> > >
> > >  https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/05/11/300944713
> > >
> > >One or more kernel tests failed:
> > >
> > >    s390x:
> > >     ❌ Networking tunnel: geneve basic test
> > >
> > >    ppc64le:
> > >     ❌ LTP
> > >     ❌ Networking tunnel: geneve basic test
> > >
> > >    aarch64:
> > >     ❌ Networking tunnel: geneve basic test
> > >
> > >    x86_64:
> > >     ❌ Networking tunnel: geneve basic test
> >
> > CKI folks, looks like there was a gap between 5.11.16 and now, and idea
> > if the reported issue here is new in the 5.11.19 -rc, or something that
> > regressed earlier?
> >
>
> Hi Sasha,
>
> this is a bug we've previously reported here:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=210569
>
> This is an older bug we've been seeing for a while and thus the
> report should not have been sent. Apologies for that - we fixed
> some permission issues with reporting yesterday and it must
> have uncovered an underlying bug. This is the only list that hits
> the problem. We'll look into that reason right away.
>

The reporting bug is fixed now. However, there's ~10 pipelines still
running (they were triggered before the fix was in place) that will
likely hit the same networking bug. Let me know if I should cancel
those runs or if I should keep them running in case any new
failures are picked up.

> Veronika
>
> > --
> > Thanks,
> > Sasha
> >





[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux