From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: kernel test robot <rong.a.chen@intel.com>
Cc: "David S. Miller" <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
lkp@01.org, Martin KaFai Lau <kafai@fb.com>,
Okash Khawaja <osk@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [LKP] [tools] 6534770d6f: kernel_selftests.bpf.test_lwt_seg6local.fail
Date: Thu, 1 Nov 2018 11:18:49 -0700 [thread overview]
Message-ID: <20181101111849.183d4383@cakuba.netronome.com> (raw)
In-Reply-To: <20181101032643.GB24195@shao2-debian>
On Thu, 1 Nov 2018 11:26:44 +0800, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 6534770d6f176093b50896961107b2d545ef38f0 ("tools: bpf: fix BTF code added twice to different trees")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
That's a fix to a merge commit, perhaps something before broke it?
> in testcase: kernel_selftests
> with following parameters:
>
> group: kselftests-00
>
> test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
> test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
>
>
> on test machine: 80 threads Skylake with 64G memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
> commit:
> 6b431d50d2a8acd1c418b998b856a055252ebc3a
> 6534770d6f176093b50896961107b2d545ef38f0
>
> 6b431d50d2a8acd1 6534770d6f176093b508969611
> ---------------- --------------------------
> fail:runs %reproduction fail:runs
> | | |
> 443:8 14689% 1618:8 dmesg.timestamp:last
> :8 100% 8:8 kernel_selftests.bpf.test_lwt_seg6local.fail
> :8 100% 8:8 kernel_selftests.bpf.test_lwt_seg6local.sh.fail
>
>
>
>
> To reproduce:
>
> git clone https://github.com/intel/lkp-tests.git
> cd lkp-tests
> bin/lkp install job.yaml # job file is attached in this email
> bin/lkp run job.yaml
>
>
>
> Thanks,
> Rong Chen
parent reply other threads:[~2018-11-01 18:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20181101032643.GB24195@shao2-debian>]
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=20181101111849.183d4383@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=netdev@vger.kernel.org \
--cc=osk@fb.com \
--cc=rong.a.chen@intel.com \
--cc=torvalds@linux-foundation.org \
/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