From: Namhyung Kim <namhyung@kernel.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: Thomas Richter <tmricht@linux.ibm.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
Linux Memory Management List <linux-mm@kvack.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [linux-next:master] [perf test] 658a8805cb: perf-sanity-tests.perf_annotate_basic_tests.fail
Date: Wed, 19 Jun 2024 14:34:28 -0400 [thread overview]
Message-ID: <CAM9d7cgDUQL82ToJN5kXJpdEm0aTEJmU1iuxCwSK5Vhi2jnpPQ@mail.gmail.com> (raw)
In-Reply-To: <202406181535.eacba363-oliver.sang@intel.com>
Hello,
On Tue, Jun 18, 2024 at 3:54 AM kernel test robot <oliver.sang@intel.com> wrote:
>
>
>
> Hello,
>
> kernel test robot noticed "perf-sanity-tests.perf_annotate_basic_tests.fail" on:
>
> commit: 658a8805cb604260ae9f35ae5e50012e3d1ed5e3 ("perf test: Speed up test case 70 annotate basic tests")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> [test failed on linux-next/master 6906a84c482f098d31486df8dc98cead21cce2d0]
>
> in testcase: perf-sanity-tests
> version:
> with following parameters:
>
> perf_compiler: gcc
>
>
>
> compiler: gcc-13
> test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (Skylake) with 32G memory
>
> (please refer to attached dmesg/kmsg for entire log/backtrace)
>
>
> we didn't observed the issue on parent.
>
> f5803651b4a4b67d 658a8805cb604260ae9f35ae5e5
> ---------------- ---------------------------
> fail:runs %reproduction fail:runs
> | | |
> :6 100% 6:6 perf-sanity-tests.perf_annotate_basic_tests.fail
Hmm.. strange. The only change in the commit is to save
the output of perf annotate into a file. I'm not sure if it'd affect
the test result. Maybe because of sanitizers..?
Thanks,
Namhyung
>
>
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <oliver.sang@intel.com>
> | Closes: https://lore.kernel.org/oe-lkp/202406181535.eacba363-oliver.sang@intel.com
>
>
> 2024-06-14 20:09:34 sudo /usr/src/linux-perf-x86_64-rhel-8.3-bpf-658a8805cb604260ae9f35ae5e50012e3d1ed5e3/tools/perf/perf test 76
> 76: perf annotate basic tests : FAILED!
> 2024-06-14 20:12:46 sudo /usr/src/linux-perf-x86_64-rhel-8.3-bpf-658a8805cb604260ae9f35ae5e50012e3d1ed5e3/tools/perf/perf test 77
> 77: Add 'perf probe's, list and remove them : Ok
> 2024-06-14 20:12:46 sudo /usr/src/linux-perf-x86_64-rhel-8.3-bpf-658a8805cb604260ae9f35ae5e50012e3d1ed5e3/tools/perf/perf test 78
> 78: build id cache operations : Ok
>
>
>
> The kernel config and materials to reproduce are available at:
> https://download.01.org/0day-ci/archive/20240618/202406181535.eacba363-oliver.sang@intel.com
>
>
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
>
prev parent reply other threads:[~2024-06-19 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 7:53 kernel test robot
2024-06-19 18:34 ` Namhyung Kim [this message]
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=CAM9d7cgDUQL82ToJN5kXJpdEm0aTEJmU1iuxCwSK5Vhi2jnpPQ@mail.gmail.com \
--to=namhyung@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=tmricht@linux.ibm.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