From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh " <linux@weissschuh.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [thomas-weissschuh:b4/rust-kunit-assertion 15/16] ld.lld: error: undefined symbol: kunit_string_stream_add
Date: Sat, 10 Oct 2026 00:42:16 +0800 [thread overview]
Message-ID: <202610100031.yvgHqzdD-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git b4/rust-kunit-assertion
head: e8ef2ab596ea6cb29ff501ab4abf4757bf950871
commit: b1f6b44f2151569e88b5bb5e652e31aebffa0d19 [15/16] kunit: msg
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20261010/202610100031.yvgHqzdD-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 80cd965b6323b208519f8ab1d5ee86e4ea9862f4)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261010/202610100031.yvgHqzdD-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/202610100031.yvgHqzdD-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: kunit_string_stream_add
>>> referenced by kunit.rs:57 (rust/kernel/kunit.rs:57)
>>> rust/kernel.o:(kernel::kunit::kunit_rust_assert_format) in archive vmlinux.a
>>> referenced by kunit.rs:57 (rust/kernel/kunit.rs:57)
>>> rust/kernel.o:(kernel::kunit::kunit_rust_assert_format) in archive vmlinux.a
--
>> ld.lld: error: undefined symbol: kunit_assert_print_msg
>>> referenced by kunit.rs:64 (rust/kernel/kunit.rs:64)
>>> rust/kernel.o:(kernel::kunit::kunit_rust_assert_format) in archive vmlinux.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-09 16:43 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=202610100031.yvgHqzdD-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux@weissschuh.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox