From: kernel test robot <lkp@intel.com>
To: Milan Tripkovic <Milan.Tripkovic@rt-rk.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
0day robot <lkp@intel.com>
Subject: lib/tests/string_kunit.c:1014:18: error: use of undeclared identifier 'string_bench_memcmp'; did you mean 'string_test_memcmp'?
Date: Thu, 14 May 2026 08:53:39 +0200 [thread overview]
Message-ID: <202605140827.Qg1DZpcB-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Milan-Tripkovic/lib-string_kunit-extend-benchmarks-and-unit-test-to-memcmp/20260514-061117
head: 63994c99c1cec63db18bebab3030f0c0e9d43ea5
commit: 63994c99c1cec63db18bebab3030f0c0e9d43ea5 lib/string_kunit: extend benchmarks and unit test to memcmp()
date: 9 hours ago
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260514/202605140827.Qg1DZpcB-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260514/202605140827.Qg1DZpcB-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/202605140827.Qg1DZpcB-lkp@intel.com/
All errors (new ones prefixed by >>):
>> lib/tests/string_kunit.c:1014:18: error: use of undeclared identifier 'string_bench_memcmp'; did you mean 'string_test_memcmp'?
1014 | KUNIT_CASE_SLOW(string_bench_memcmp),
| ^~~~~~~~~~~~~~~~~~~
| string_test_memcmp
include/kunit/test.h:188:17: note: expanded from macro 'KUNIT_CASE_SLOW'
188 | { .run_case = test_name, .name = #test_name, \
| ^
lib/tests/string_kunit.c:883:13: note: 'string_test_memcmp' declared here
883 | static void string_test_memcmp(struct kunit *test)
| ^
1 error generated.
vim +1014 lib/tests/string_kunit.c
983
984 static struct kunit_case string_test_cases[] = {
985 KUNIT_CASE(string_test_memset16),
986 KUNIT_CASE(string_test_memset32),
987 KUNIT_CASE(string_test_memset64),
988 KUNIT_CASE(string_test_strlen),
989 KUNIT_CASE(string_test_strnlen),
990 KUNIT_CASE(string_test_strchr),
991 KUNIT_CASE(string_test_strnchr),
992 KUNIT_CASE(string_test_strrchr),
993 KUNIT_CASE(string_test_strspn),
994 KUNIT_CASE(string_test_strcmp),
995 KUNIT_CASE(string_test_strcmp_long_strings),
996 KUNIT_CASE(string_test_strncmp),
997 KUNIT_CASE(string_test_strncmp_long_strings),
998 KUNIT_CASE(string_test_strcasecmp),
999 KUNIT_CASE(string_test_strcasecmp_long_strings),
1000 KUNIT_CASE(string_test_strncasecmp),
1001 KUNIT_CASE(string_test_strncasecmp_long_strings),
1002 KUNIT_CASE(string_test_strscpy),
1003 KUNIT_CASE(string_test_strcat),
1004 KUNIT_CASE(string_test_strncat),
1005 KUNIT_CASE(string_test_strlcat),
1006 KUNIT_CASE(string_test_strtomem),
1007 KUNIT_CASE(string_test_memtostr),
1008 KUNIT_CASE(string_test_strends),
1009 KUNIT_CASE(string_bench_strlen),
1010 KUNIT_CASE(string_bench_strnlen),
1011 KUNIT_CASE(string_bench_strchr),
1012 KUNIT_CASE(string_bench_strrchr),
1013 KUNIT_CASE(string_test_memcmp),
> 1014 KUNIT_CASE_SLOW(string_bench_memcmp),
1015 {}
1016 };
1017
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-14 6:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202605140827.Qg1DZpcB-lkp@intel.com \
--to=lkp@intel.com \
--cc=Milan.Tripkovic@rt-rk.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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.