From: Veronika Kabatova <vkabatov@redhat.com>
To: Sasha Levin <sashal@kernel.org>
Cc: CKI Project <cki-project@redhat.com>,
skt-results-master@redhat.com,
Linux Stable maillist <stable@vger.kernel.org>,
Jianlin Shi <jishi@redhat.com>, Jianwen Ji <jiji@redhat.com>,
Hangbin Liu <haliu@redhat.com>,
Memory Management <mm-qe@redhat.com>,
Jan Stancek <jstancek@redhat.com>, Xiong Zhou <xzhou@redhat.com>
Subject: Re: ❌ FAIL: Test report for kernel 5.11.19 (stable-queue, beb6df0c)
Date: Wed, 12 May 2021 12:16:48 +0200 [thread overview]
Message-ID: <CA+tGwnnyDVtoNy=_CVTjpEpxw7B2omPLGvq50LYYwd4htgvxMg@mail.gmail.com> (raw)
In-Reply-To: <YJstva9S9qPO+2F3@sashalap>
On Wed, May 12, 2021 at 3:22 AM Sasha Levin <sashal@kernel.org> 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.
Veronika
> --
> Thanks,
> Sasha
>
next prev parent reply other threads:[~2021-05-12 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 21:43 ❌ FAIL: Test report for kernel 5.11.19 (stable-queue, beb6df0c) CKI Project
2021-05-12 1:22 ` Sasha Levin
2021-05-12 10:16 ` Veronika Kabatova [this message]
[not found] ` <CAJxqp2-KA+VPS59hKsN9z-ysZdo1Edv52vfnHYsXioO-CqeXcg@mail.gmail.com>
2021-05-12 11:23 ` Veronika Kabatova
2021-05-12 12:59 ` Veronika Kabatova
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+tGwnnyDVtoNy=_CVTjpEpxw7B2omPLGvq50LYYwd4htgvxMg@mail.gmail.com' \
--to=vkabatov@redhat.com \
--cc=cki-project@redhat.com \
--cc=haliu@redhat.com \
--cc=jiji@redhat.com \
--cc=jishi@redhat.com \
--cc=jstancek@redhat.com \
--cc=mm-qe@redhat.com \
--cc=sashal@kernel.org \
--cc=skt-results-master@redhat.com \
--cc=stable@vger.kernel.org \
--cc=xzhou@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.