From: Sasha Levin <sashal@kernel.org>
To: CKI Project <cki-project@redhat.com>
Cc: Linux Stable maillist <stable@vger.kernel.org>,
Memory Management <mm-qe@redhat.com>,
Jan Stancek <jstancek@redhat.com>,
LTP Mailing List <ltp@lists.linux.it>,
Ondrej Moris <omoris@redhat.com>,
Ondrej Mosnacek <omosnace@redhat.com>,
William Gomeringer <wgomeringer@redhat.com>
Subject: Re: ❌ PANICKED: Test report for kernel 5.5.8-c30f33b.cki (stable-queue)
Date: Mon, 9 Mar 2020 17:53:05 -0400 [thread overview]
Message-ID: <20200309215305.GV21491@sasha-vm> (raw)
In-Reply-To: <cki.411617A928.D7E40QQCW6@redhat.com>
On Mon, Mar 09, 2020 at 09:24:35PM -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: c30f33bfb014 - selftests: forwarding: vxlan_bridge_1d: use more proper tos value
>
>The results of these automated tests are provided below.
>
> Overall result: FAILED (see details below)
> Merge: OK
> Compile: OK
> Tests: PANICKED
>
>All kernel binaries, config files, and logs are available for download here:
>
> https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawarehouse/2020/03/09/480158
>
>One or more kernel tests failed:
>
> s390x:
> ❌ LTP
>
> ppc64le:
> ❌ LTP
>
> aarch64:
> ❌ audit: audit testsuite test
>
> x86_64:
> ❌ audit: audit testsuite test
Following the link above I got to
https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawarehouse/2020/03/09/480158/audit__audit_testsuite_test/,
but it shows that all tests are passing? The console log looks fine too:
https://cki-artifacts.s3.us-east-2.amazonaws.com/datawarehouse/2020/03/09/480158/x86_64_5_console.log.
Where's the panic?
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-03-09 21:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 21:24 ❌ PANICKED: Test report for kernel 5.5.8-c30f33b.cki (stable-queue) CKI Project
2020-03-09 21:53 ` Sasha Levin [this message]
2020-03-09 22:03 ` Ondrej Mosnacek
2020-03-10 7:58 ` Jan Stancek
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=20200309215305.GV21491@sasha-vm \
--to=sashal@kernel.org \
--cc=cki-project@redhat.com \
--cc=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
--cc=mm-qe@redhat.com \
--cc=omoris@redhat.com \
--cc=omosnace@redhat.com \
--cc=stable@vger.kernel.org \
--cc=wgomeringer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).