From: Adrian Hunter <adrian.hunter@intel.com>
To: Oliver Sang <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [perf-tools-next:tmp.perf-tools-next] [perf dlfilter] f178a76b05: perf-sanity-tests.dlfilter_C_API.fail
Date: Thu, 24 Aug 2023 07:45:25 +0300 [thread overview]
Message-ID: <8685878c-8de0-88b9-4434-f823620f6abf@intel.com> (raw)
In-Reply-To: <ZOa1LnnwETWCQ6n5@xsang-OptiPlex-9020>
On 24/08/23 04:41, Oliver Sang wrote:
> hi, Adrian Hunter,
>
> On Wed, Aug 23, 2023 at 06:37:49PM +0300, Adrian Hunter wrote:
>> On 23/08/23 17:57, kernel test robot wrote:
>>>
>>>
>>> Hello,
>>>
>>> kernel test robot noticed "perf-sanity-tests.dlfilter_C_API.fail" on:
>>>
>>> commit: f178a76b054fd046d212c3c67745146ff191a443 ("perf dlfilter: Add a test for resolve_address()")
>>> https://git.kernel.org/cgit/linux/kernel/git/perf/perf-tools-next.git tmp.perf-tools-next
>>>
>>> [test failed on linux-next/master 28c736b0e92e11bfe2b9997688213dc43cb22182]
>>
>> We sometimes make a test for an issue then fix it, so the new test fails,
>> but is fixed in a subsequent patch. If you read the commit it says as much:
>>
>> commit f178a76b054fd046d212c3c67745146ff191a443
>> Author: Adrian Hunter <adrian.hunter@intel.com>
>> Date: Mon Jul 31 12:18:55 2023 +0300
>>
>> perf dlfilter: Add a test for resolve_address()
>>
>> Extend the "dlfilter C API" test to test
>> perf_dlfilter_fns.resolve_address(). The test currently fails, but passes
>> after a subsequent patch.
>>
>> Reviewed-by: Ian Rogers <irogers@google.com>
>> Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
>> Cc: Jiri Olsa <jolsa@kernel.org>
>> Cc: Namhyung Kim <namhyung@kernel.org>
>> Link: https://lore.kernel.org/r/20230731091857.10681-1-adrian.hunter@intel.com
>> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
>>
>> The fix is:
>>
>> 42c6dd9d23019ff339d0aca80a444eb71087050e perf dlfilter: Initialize addr_location before passing it to thread__find_symbol_fb()
>
> thanks a lot for information!
>
> as above mentioned, when this auto-bisect done, it confirmed the issue still
> exists linux-next/master:
> [test failed on linux-next/master 28c736b0e92e11bfe2b9997688213dc43cb22182]
> which includes 42c6dd9d23019ff339d0aca80a444eb71087050e
>
> we will test again on latest linux-next/master:
> e3f80d3eae76c (tag: next-20230823, linux-next/master, broonie-ci/next-master) Add linux-next specific files for 20230823
> and 42c6dd9d23019ff339d0aca80a444eb71087050e
>
> Thanks
Could you include the output from:
perf test -v dlfilter
>
>>>
>>> in testcase: perf-sanity-tests
>>> version: perf-x86_64-00c7b5f4ddc5-1_20230402
>>> with following parameters:
>>>
>>> perf_compiler: gcc
>>>
>>>
>>>
>>> compiler: gcc-12
>>> test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480+ (Sapphire Rapids) with 256G memory
>>>
>>> (please refer to attached dmesg/kmsg for entire log/backtrace)
>>>
>>>
>>>
>>>
>>> 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/202308232146.94d82cb4-oliver.sang@intel.com
>>>
>>>
>>>
>>> 66: Convert perf time to TSC :
>>> 66.1: TSC support : Ok
>>> 66.2: Perf time to TSC : Ok
>>> 67: dlfilter C API : FAILED! <---
>>> 68: Sigtrap : Ok
>>>
>>>
>>>
>>> The kernel config and materials to reproduce are available at:
>>> https://download.01.org/0day-ci/archive/20230823/202308232146.94d82cb4-oliver.sang@intel.com
>>>
>>>
>>>
>>
next prev parent reply other threads:[~2023-08-24 4:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 14:57 [perf-tools-next:tmp.perf-tools-next] [perf dlfilter] f178a76b05: perf-sanity-tests.dlfilter_C_API.fail kernel test robot
2023-08-23 15:37 ` Adrian Hunter
2023-08-23 16:55 ` Arnaldo Carvalho de Melo
2023-08-24 1:41 ` Oliver Sang
2023-08-24 4:45 ` Adrian Hunter [this message]
2023-08-29 2:42 ` Oliver Sang
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=8685878c-8de0-88b9-4434-f823620f6abf@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@redhat.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lkp@intel.com \
--cc=namhyung@kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.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).