From: kernel test robot <lkp@intel.com>
To: Janne Grunau <j@jannau.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [asahilinux:bits/250-aop 15/68] error: cannot find macro `vec` in this scope
Date: Tue, 07 Apr 2026 11:56:51 +0800 [thread overview]
Message-ID: <202604050253.RkhQPGru-lkp@intel.com> (raw)
tree: https://github.com/AsahiLinux/linux bits/250-aop
head: f7a3080ba37b989ad2fd83054a4b458af97b635d
commit: 76aa8a8de9fb5488da45a470fada7e8d6bfcd5ca [15/68] rust: alloc: vec: Add TryFrom trait
config: x86_64-randconfig-073-20260404 (https://download.01.org/0day-ci/archive/20260405/202604050253.RkhQPGru-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/20260405/202604050253.RkhQPGru-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/202604050253.RkhQPGru-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error: cannot find macro `vec` in this scope
--> rust/doctests_kernel_generated.rs:1557:19
|
1557 | assert_eq!(r, Err(vec![0, 1, 2, 3, 4, 5, 6, 7, 8, 9]));
| ^^^
--
>> error: cannot find macro `vec` in this scope
--> rust/doctests_kernel_generated.rs:1504:12
|
1504 | assert_eq!(vec![1, 2, 3].try_into(), Ok([1, 2, 3]));
| ^^^
--
>> error[E0107]: struct takes 2 generic arguments but 1 generic argument was supplied
--> rust/doctests_kernel_generated.rs:1505:13
|
1505 | assert_eq!(<Vec<i32>>::new().try_into(), Ok([]));
| ^^^ --- supplied 1 generic argument
| |
| expected 2 generic arguments
|
note: struct defined here, with 2 generic parameters: `T`, `A`
--> rust/kernel/alloc/kvec.rs:104:12
|
104 | pub struct Vec<T, A: Allocator> {
| ^^^ - -
help: add missing generic argument
|
1505 | assert_eq!(<Vec<i32, A>>::new().try_into(), Ok([]));
| +++
--
>> error[E0107]: struct takes 2 generic arguments but 1 generic argument was supplied
--> rust/doctests_kernel_generated.rs:1556:48
|
1556 | let r: Result<[i32; 4], _> = (0..10).collect::<Vec<_>>().try_into();
| ^^^ - supplied 1 generic argument
| |
| expected 2 generic arguments
|
note: struct defined here, with 2 generic parameters: `T`, `A`
--> rust/kernel/alloc/kvec.rs:104:12
|
104 | pub struct Vec<T, A: Allocator> {
| ^^^ - -
help: add missing generic argument
|
1556 | let r: Result<[i32; 4], _> = (0..10).collect::<Vec<_, _>>().try_into();
| +++
--
>> error[E0433]: failed to resolve: use of undeclared type `String`
--> rust/doctests_kernel_generated.rs:1608:13
|
1608 | let mut v = String::from("hello world").into_bytes();
| ^^^^^^ use of undeclared type `String`
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-07 3:57 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=202604050253.RkhQPGru-lkp@intel.com \
--to=lkp@intel.com \
--cc=j@jannau.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