From: Jakub Kicinski <kuba@kernel.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: Carolina Jubran <cjubran@nvidia.com>, <oe-lkp@lists.linux.dev>,
<lkp@intel.com>, Cosmin Ratiu <cratiu@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
<netdev@vger.kernel.org>
Subject: Re: [linux-next:master] [selftest] 236156d80d: kernel-selftests.drivers/net/netdevsim.devlink.sh.rate_test.fail
Date: Fri, 25 Jul 2025 08:08:18 -0700 [thread overview]
Message-ID: <20250725080818.3b1581c5@kernel.org> (raw)
In-Reply-To: <202507251144.b4d9d40b-lkp@intel.com>
On Fri, 25 Jul 2025 20:34:58 +0800 kernel test robot wrote:
> kernel test robot noticed "kernel-selftests.drivers/net/netdevsim.devlink.sh.rate_test.fail" on:
>
> commit: 236156d80d5efd942fc395a078d6ec6d810c2c40 ("selftest: netdevsim: Add devlink rate tc-bw test")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> [test failed on linux-next/master 97987520025658f30bb787a99ffbd9bbff9ffc9d]
This is not helpful, you have old tools in your environment.
Ideally you'd report regressions in existing test _cases_
(I mean an individial [ OK ] turning into a [FAIL]).
The bash tests depend on too many CLI tools to be expected
to pass. Having to detect the tool versions is an unnecessary
burden on the test author. Tools usually get updated within
3 months and then all these checks become dead code for the
rest of time...
next prev parent reply other threads:[~2025-07-25 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 12:34 [linux-next:master] [selftest] 236156d80d: kernel-selftests.drivers/net/netdevsim.devlink.sh.rate_test.fail kernel test robot
2025-07-25 15:08 ` Jakub Kicinski [this message]
2025-07-28 1:38 ` Oliver Sang
2025-07-28 9:21 ` Philip Li
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=20250725080818.3b1581c5@kernel.org \
--to=kuba@kernel.org \
--cc=cjubran@nvidia.com \
--cc=cratiu@nvidia.com \
--cc=lkp@intel.com \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=tariqt@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox