Linux Trace Kernel
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Cc: kernel test robot <oliver.sang@intel.com>,
	Steven Rostedt <rostedt@goodmis.org>, <oe-lkp@lists.linux.dev>,
	<lkp@intel.com>, <linux-kernel@vger.kernel.org>,
	Shuah Khan <skhan@linuxfoundation.org>,
	<linux-trace-kernel@vger.kernel.org>
Subject: Re: [linus:master] [selftests/tracing]  c5c413534d: kselftests-bpf.ftrace.ftracetest-ktap._instance_event_trigger_-_test_poll_wait_on_histogram.fail
Date: Tue, 21 Jul 2026 09:38:30 +0900	[thread overview]
Message-ID: <20260721093830.bb1d57a6a6d30c3f8651a292@kernel.org> (raw)
In-Reply-To: <20260720232952.94b33d59eddb69cf6457ded4@kernel.org>

On Mon, 20 Jul 2026 23:29:52 +0900
Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:

> On Thu, 16 Jul 2026 22:30:11 +0800
> kernel test robot <oliver.sang@intel.com> wrote:
> 
> > 
> > 
> > 
> > Hello,
> > 
> > in fact, we found below two test cases randomly failed upon c5c413534d, while
> > keep succeed on parent:
> > 
> > =========================================================================================
> > tbox_group/testcase/rootfs/kconfig/compiler/group:
> >   igk-rpl-d04/kselftests-bpf/debian-13-x86_64-20250902.cgz/x86_64-rhel-9.4-bpf/gcc-14/ftrace
> > 
> > 22a78be4123dce81 c5c413534d40eb4c982f1794e62
> > ---------------- ---------------------------
> >        fail:runs  %reproduction    fail:runs
> >            |             |             |
> >            :31          52%          16:32    kselftests-bpf.ftrace.ftracetest-ktap._instance_event_trigger_-_test_poll_wait_on_histogram.fail
> >            :31          29%           9:32    kselftests-bpf.ftrace.ftracetest-ktap.event_trigger_-_test_poll_wait_on_histogram.fail
> > 
> > 
> > 
> > kernel test robot noticed "kselftests-bpf.ftrace.ftracetest-ktap._instance_event_trigger_-_test_poll_wait_on_histogram.fail" on:
> > 
> > commit: c5c413534d40eb4c982f1794e62813f926aba747 ("selftests/tracing: Have trigger-hist-poll.tc use sched_process_exit")
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> > 
> > [test failed on linux-next/master 49362394dad7df66c274c867a271394c10ca2bb8]
> 
> Hmm, this seems like a scheduler (event) behavior is different from what
> the test expected.
> 
> Steve, I think we should use another deterministic events.

I've sent a fix.

https://lore.kernel.org/all/178459323652.354837.10711230683477156733.stgit@devnote2/

But this drops 2 checkpoints. I think we need to use another deterministic
event, like trace_marker (but trace_marker does not support histogram trigger)

Thanks,


> 
> Thank you,
> 
> -- 
> Masami Hiramatsu (Google) <mhiramat@kernel.org>


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

      reply	other threads:[~2026-07-21  0:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-16 14:30 [linus:master] [selftests/tracing] c5c413534d: kselftests-bpf.ftrace.ftracetest-ktap._instance_event_trigger_-_test_poll_wait_on_histogram.fail kernel test robot
2026-07-20 14:29 ` Masami Hiramatsu
2026-07-21  0:38   ` Masami Hiramatsu [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=20260721093830.bb1d57a6a6d30c3f8651a292@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=rostedt@goodmis.org \
    --cc=skhan@linuxfoundation.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