From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Kees Cook" <kees@kernel.org>,
"Andy Lutomirski" <luto@amacapital.net>,
"Will Drewry" <wad@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Subject: Re: [PATCH 3/5] selftests: kselftest: Add ksft_reset_state()
Date: Thu, 29 Jan 2026 00:49:12 +0100 [thread overview]
Message-ID: <202601290039.37LnFCGx-lkp@intel.com> (raw)
In-Reply-To: <20260128-kselftest-harness-v1-3-cb259fa81cd0@linutronix.de>
Hi Thomas,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 6d6ad32e22f028c525d5df471c5522616e645a6b]
url: https://github.com/intel-lab-lkp/linux/commits/Thomas-Wei-schuh/selftests-kselftest-Treat-xpass-as-successful-result/20260128-182856
base: 6d6ad32e22f028c525d5df471c5522616e645a6b
patch link: https://lore.kernel.org/r/20260128-kselftest-harness-v1-3-cb259fa81cd0%40linutronix.de
patch subject: [PATCH 3/5] selftests: kselftest: Add ksft_reset_state()
config: i386-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260129/202601290039.37LnFCGx-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260129/202601290039.37LnFCGx-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202601290039.37LnFCGx-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from ovpn-cli.c:35:
>> tools/testing/selftests/../../../tools/testing/selftests/kselftest.h:488:2: warning: extra ';' outside of a function [-Wextra-semi]
488 | };
| ^
1 warning generated.
vim +488 tools/testing/selftests/../../../tools/testing/selftests/kselftest.h
478
479 static inline void ksft_reset_state(void)
480 {
481 ksft_cnt.ksft_pass = 0;
482 ksft_cnt.ksft_fail = 0;
483 ksft_cnt.ksft_xfail = 0;
484 ksft_cnt.ksft_xpass = 0;
485 ksft_cnt.ksft_xskip = 0;
486 ksft_cnt.ksft_error = 0;
487 ksft_plan = 0;
> 488 };
489
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-28 23:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 10:24 [PATCH 0/5] selftests: harness: Detect illegal mixing of kselftest and harness functionality Thomas Weißschuh
2026-01-28 10:24 ` [PATCH 1/5] selftests: kselftest: Treat xpass as successful result Thomas Weißschuh
2026-01-28 10:24 ` [PATCH 2/5] selftests: harness: Validate that explicit kselftest exitcodes are handled Thomas Weißschuh
2026-01-28 10:24 ` [PATCH 3/5] selftests: kselftest: Add ksft_reset_state() Thomas Weißschuh
2026-01-28 22:10 ` kernel test robot
2026-01-28 23:49 ` kernel test robot [this message]
2026-01-28 10:24 ` [PATCH 4/5] selftests: harness: Detect illegal mixing of kselftest and harness functionality Thomas Weißschuh
2026-01-28 10:24 ` [PATCH 5/5] selftests: harness: Validate intermixing " Thomas Weißschuh
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=202601290039.37LnFCGx-lkp@intel.com \
--to=lkp@intel.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=thomas.weissschuh@linutronix.de \
--cc=wad@chromium.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