All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Richter <tmricht@linux.ibm.com>
To: Namhyung Kim <namhyung@kernel.org>,
	kernel test robot <oliver.sang@intel.com>
Cc: lkp@intel.com, 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: Thu, 20 Jun 2024 10:05:57 +0200	[thread overview]
Message-ID: <fb82c22e-e72d-4d0b-9e66-29e3975919a4@linux.ibm.com> (raw)
In-Reply-To: <CAM9d7cgDUQL82ToJN5kXJpdEm0aTEJmU1iuxCwSK5Vhi2jnpPQ@mail.gmail.com>

On 6/19/24 20:34, Namhyung Kim wrote:
> 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
> 

Apologies that this patches causes trouble.
I retried the patch again on my Intel virtual machine and it did succeed.
I do not know how to help to get this fixed. Please advise.

Thanks a lot

>> 0-DAY CI Kernel Test Service
>> https://github.com/intel/lkp-tests/wiki
>>
> -- 
Thomas Richter, Dept 3303, IBM s390 Linux Development, Boeblingen, Germany
--
IBM Deutschland Research & Development GmbH

Vorsitzender des Aufsichtsrats: Wolfgang Wendt

Geschäftsführung: David Faller

Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294


      reply	other threads:[~2024-06-20  8:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18  7:53 [linux-next:master] [perf test] 658a8805cb: perf-sanity-tests.perf_annotate_basic_tests.fail kernel test robot
2024-06-19 18:34 ` Namhyung Kim
2024-06-20  8:05   ` Thomas Richter [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=fb82c22e-e72d-4d0b-9e66-29e3975919a4@linux.ibm.com \
    --to=tmricht@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=namhyung@kernel.org \
    --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 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.