Linux Trace Kernel
 help / color / mirror / Atom feed
From: Oliver Sang <oliver.sang@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Pu Lehui <pulehui@huaweicloud.com>, <oe-lkp@lists.linux.dev>,
	<lkp@intel.com>, <linux-kernel@vger.kernel.org>,
	<linux-trace-kernel@vger.kernel.org>, <mhiramat@kernel.org>,
	<mathieu.desnoyers@efficios.com>, <pulehui@huawei.com>,
	<oliver.sang@intel.com>
Subject: Re: [PATCH] tracing: Fix missing errno when zero parser->idx in trace_pid_write
Date: Thu, 11 Sep 2025 16:23:35 +0800	[thread overview]
Message-ID: <aMKHBwzgqHOhILUQ@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20250905150312.02bef848@gandalf.local.home>

hi, Steve,

On Fri, Sep 05, 2025 at 03:03:12PM -0400, Steven Rostedt wrote:
> On Tue, 2 Sep 2025 23:09:53 +0800
> kernel test robot <oliver.sang@intel.com> wrote:
> 
> > commit: cebdd2c9a622becc41349f32ace1795d750beda8 ("[PATCH] tracing: Fix missing errno when zero parser->idx in trace_pid_write")
> > url: https://github.com/intel-lab-lkp/linux/commits/Pu-Lehui/tracing-Fix-missing-errno-when-zero-parser-idx-in-trace_pid_write/20250821-151736
> > base: https://git.kernel.org/cgit/linux/kernel/git/trace/linux-trace for-next
> > patch link: https://lore.kernel.org/all/20250821071721.3609109-1-pulehui@huaweicloud.com/
> > patch subject: [PATCH] tracing: Fix missing errno when zero parser->idx in trace_pid_write
> > 
> > in testcase: perf-sanity-tests
> > version: 
> > with following parameters:
> > 
> > 	perf_compiler: gcc
> > 	group: group-01
> 
> This is why I hate LKP. It's huge, complex, and I never can get it working.
> 
> I did the following:
> 
>  # lkp split-job jobs/perf-sanity-tests.yaml
>  # lkp install -f ./perf-sanity-tests-defaults.yaml
> 
> [ had to fix python up a little because it wanted python3.9 where I had 3.13 ]
> 
>  # lkp run ./perf-sanity-tests-defaults.yaml
> /work/git/lkp-tests.git/programs/perf-sanity-tests/run: 7: .: cannot open /work/git/lkp-tests.git/lib/tests/perf_test.sh: No such file
> kill 37975 vmstat --timestamp -n 10 
> kill 37973 dmesg --follow --decode 
> wait for background processes: 37978 meminfo
> 
> 
> I have no idea where this "perf_test.sh" is supposed to come from, and why
> it doesn't exist :-p

sorry for inconvenience. for this "perf_test.sh" issue, we pushed a fix
https://github.com/intel/lkp-tests/commit/3ab6496813796e537d277242d220c4571790a363

however, we found there are other issues which block reproducer to work out of
our cluster env that we can not resolve shortly.

but if you have any debug/fix patch, we'll be very glad to test/verify.

> 
> 
> -- Steve

  reply	other threads:[~2025-09-11  8:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21  7:17 [PATCH] tracing: Fix missing errno when zero parser->idx in trace_pid_write Pu Lehui
2025-08-28  2:02 ` Pu Lehui
2025-08-28  2:58   ` Steven Rostedt
2025-09-02 15:09 ` kernel test robot
2025-09-05 19:03   ` Steven Rostedt
2025-09-11  8:23     ` Oliver Sang [this message]
2025-09-11 14:04       ` Steven Rostedt
2025-09-03  4:15 ` Pu Lehui
2025-09-05 19:39   ` Steven Rostedt
2025-09-08  2:47     ` Pu Lehui

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=aMKHBwzgqHOhILUQ@xsang-OptiPlex-9020 \
    --to=oliver.sang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=oe-lkp@lists.linux.dev \
    --cc=pulehui@huawei.com \
    --cc=pulehui@huaweicloud.com \
    --cc=rostedt@goodmis.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