[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250725080818.3b1581c5@kernel.org>
Date: Fri, 25 Jul 2025 08:08:18 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: kernel test robot <oliver.sang@...el.com>
Cc: Carolina Jubran <cjubran@...dia.com>, <oe-lkp@...ts.linux.dev>,
<lkp@...el.com>, Cosmin Ratiu <cratiu@...dia.com>, Tariq Toukan
<tariqt@...dia.com>, Mark Bloch <mbloch@...dia.com>,
<netdev@...r.kernel.org>
Subject: Re: [linux-next:master] [selftest] 236156d80d:
kernel-selftests.drivers/net/netdevsim.devlink.sh.rate_test.fail
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...
Powered by blists - more mailing lists