[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241107104022.47f2b527@gandalf.local.home>
Date: Thu, 7 Nov 2024 10:40:22 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: kernel test robot <oliver.sang@...el.com>
Cc: Zheng Yejian <zhengyejian@...weicloud.com>, <oe-lkp@...ts.linux.dev>,
<lkp@...el.com>, <linux-kernel@...r.kernel.org>,
<linux-trace-kernel@...r.kernel.org>, <nouveau@...ts.freedesktop.org>
Subject: Re: [linux-next:master] [tracing] 49e4154f4b:
INFO:task_blocked_for_more_than#seconds
On Thu, 7 Nov 2024 22:25:23 +0800
kernel test robot <oliver.sang@...el.com> wrote:
> kernel test robot noticed "INFO:task_blocked_for_more_than#seconds" on:
>
> commit: 49e4154f4b16345da5e219b23ed9737a6e735bc1 ("tracing: Remove TRACE_EVENT_FL_FILTERED logic")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> [test failed on linux-next/master 850f22c42f4b0a14a015aecc26f46f9948ded6dd]
>
> in testcase: boot
The commit in question does not even get executed in the boot process
(unless you have tracing on boot enabled). So I'll simply ignore this.
-- Steve
Powered by blists - more mailing lists