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/190-rust 96/170] error: cannot find macro `vec` in this scope
Date: Sat, 23 Nov 2024 21:01:00 +0800 [thread overview]
Message-ID: <202411232001.pjkAkjgA-lkp@intel.com> (raw)
tree: https://github.com/AsahiLinux/linux bits/190-rust
head: d2162ac6537bde95fc68fe4ec97d67c43846231c
commit: 4083ae246e9f06bcf4c1e1e9208cd82c18ca6e48 [96/170] rust: alloc: Vec: Implement .clear()/.truncate()
config: x86_64-randconfig-001-20241123 (https://download.01.org/0day-ci/archive/20241123/202411232001.pjkAkjgA-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241123/202411232001.pjkAkjgA-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/202411232001.pjkAkjgA-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error: cannot find macro `vec` in this scope
--> rust/doctests_kernel_generated.rs:1127:15
|
1127 | let mut vec = vec![1, 2, 3];
| ^^^
--
>> error: cannot find macro `vec` in this scope
--> rust/doctests_kernel_generated.rs:1079:15
|
1079 | let mut vec = vec![1, 2, 3];
| ^^^
--
>> error: cannot find macro `vec` in this scope
--> rust/doctests_kernel_generated.rs:1031:15
|
1031 | let mut vec = vec![1, 2, 3, 4, 5];
| ^^^
--
>> error: cannot find macro `vec` in this scope
--> rust/doctests_kernel_generated.rs:981:13
|
981 | let mut v = vec![1, 2, 3];
| ^^^
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-11-23 13:01 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=202411232001.pjkAkjgA-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 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.