From: Cyril Hrubis <chrubis@suse.cz>
To: Joel Granados <joel.granados@kernel.org>
Cc: Oliver Sang <oliver.sang@intel.com>,
lkp@intel.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, oe-lkp@lists.linux.dev,
ltp@lists.linux.itccccbjfeunckknjvluceftfithdduijkhkcinjndvek
Subject: Re: [LTP] [linux-next:master] [sysctl] 50b496351d: ltp.proc01.fail
Date: Thu, 27 Nov 2025 12:14:09 +0100 [thread overview]
Message-ID: <aSgygYnVBK1MxdOT@yuki.lan> (raw)
In-Reply-To: <774fersjoa3ymtmorfoxs7xei3vjdf5h4dohkkjjgxo6qgpz5w@kqn6du5d62m7>
Hi!
> > > > PATH=/lkp/benchmarks/ltp:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/lkp/lkp/src/bin
> > > > 2025-11-25 05:37:33 cd /lkp/benchmarks/ltp
> > > > 2025-11-25 05:37:33 export LTP_RUNTIME_MUL=2
> > > > 2025-11-25 05:37:33 export LTPROOT=/lkp/benchmarks/ltp
> > > > 2025-11-25 05:37:33 kirk -U ltp -f fs-00
> > >
> > > Oliver can you please record the test logs with '-o results.json' and
> > > include that file in the download directory?
> >
> > I attached one results.json FYI.
> I can see the errors and I can reproduce on my side. I'll take a look.
> thx.
>
> BTW: I saw this path in the logs
> /proc/sys/net/ipv5/neigh/default/anycast_delay
>
> not sure if "ipv5" is part of the suit, but worth mentioning from my
> side.
The proc01 test walks over proc files and attempts to read one after
another. It does not invent paths that are not on the system already.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2025-11-27 11:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 8:56 [LTP] [linux-next:master] [sysctl] 50b496351d: ltp.proc01.fail kernel test robot
2025-11-25 8:56 ` kernel test robot
2025-11-25 10:45 ` [LTP] " Cyril Hrubis
2025-11-25 10:45 ` Cyril Hrubis
2025-11-26 2:34 ` Oliver Sang
2025-11-26 2:34 ` Oliver Sang
2025-11-26 9:03 ` Cyril Hrubis
2025-11-26 9:03 ` Cyril Hrubis
2025-11-27 4:50 ` Oliver Sang
2025-11-27 4:50 ` Oliver Sang
2025-11-27 10:35 ` Joel Granados
2025-11-27 11:14 ` Cyril Hrubis [this message]
2025-11-27 15:06 ` Joel Granados
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=aSgygYnVBK1MxdOT@yuki.lan \
--to=chrubis@suse.cz \
--cc=joel.granados@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ltp@lists.linux.itccccbjfeunckknjvluceftfithdduijkhkcinjndvek \
--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 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.