* Re: [PATCH v4] rust: kernel: introduce `unsafe_precondition_assert!` macro [not found] <20250808192005.209188-1-ritvikfoss@gmail.com> @ 2025-08-12 15:52 ` kernel test robot 2025-08-12 18:08 ` Ritvik Gupta 0 siblings, 1 reply; 2+ messages in thread From: kernel test robot @ 2025-08-12 15:52 UTC (permalink / raw) To: Ritvik Gupta, Miguel Ojeda, Alex Gaynor, Boqun Feng, Gary Guo, Björn Roy Baron, Benno Lossin, Andreas Hindborg, Alice Ryhl, Trevor Gross, Danilo Krummrich Cc: llvm, oe-kbuild-all, linux-kernel, rust-for-linux Hi Ritvik, kernel test robot noticed the following build errors: [auto build test ERROR on 37816488247ddddbc3de113c78c83572274b1e2e] url: https://github.com/intel-lab-lkp/linux/commits/Ritvik-Gupta/rust-kernel-introduce-unsafe_precondition_assert-macro/20250809-032122 base: 37816488247ddddbc3de113c78c83572274b1e2e patch link: https://lore.kernel.org/r/20250808192005.209188-1-ritvikfoss%40gmail.com patch subject: [PATCH v4] rust: kernel: introduce `unsafe_precondition_assert!` macro config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250812/202508122341.rb7U1Q2P-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/20250812/202508122341.rb7U1Q2P-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/202508122341.rb7U1Q2P-lkp@intel.com/ All errors (new ones prefixed by >>): >> error[E0423]: cannot initialize a tuple struct which contains private fields --> rust/doctests_kernel_generated.rs:8841:5 | 8841 | CpuId(id) | ^^^^^ | note: constructor is not visible here due to private fields --> rust/kernel/cpu.rs:47:18 | 47 | pub struct CpuId(u32); | ^^^ private field help: you might have meant to use an associated function to build this type | 8841 - CpuId(id) 8841 + CpuId::from_i32_unchecked(_) | 8841 - CpuId(id) 8841 + CpuId::from_u32_unchecked(_) | 8841 - CpuId(id) 8841 + CpuId::current() | -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH v4] rust: kernel: introduce `unsafe_precondition_assert!` macro 2025-08-12 15:52 ` [PATCH v4] rust: kernel: introduce `unsafe_precondition_assert!` macro kernel test robot @ 2025-08-12 18:08 ` Ritvik Gupta 0 siblings, 0 replies; 2+ messages in thread From: Ritvik Gupta @ 2025-08-12 18:08 UTC (permalink / raw) To: kernel test robot Cc: Miguel Ojeda, Alex Gaynor, Boqun Feng, Gary Guo, Björn Roy Baron, Benno Lossin, Andreas Hindborg, Alice Ryhl, Trevor Gross, Danilo Krummrich, llvm, oe-kbuild-all, linux-kernel, rust-for-linux If someone's referring to it in the future, this was doctest issue. It’s actually the second time I’ve hit it. On my end, this error wasn't occurring when compiling the kernel. What I was missing: 1. Enable `Kernel Hacking > Kernel Testing and Coverage > KUnit` 2. Enable Doctest in `Rust hacking > Doctests for the 'kernel' crate` I can now reproduce capture the issue locally. Won't happen again :) ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-08-12 18:07 UTC | newest] Thread overview: 2+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- [not found] <20250808192005.209188-1-ritvikfoss@gmail.com> 2025-08-12 15:52 ` [PATCH v4] rust: kernel: introduce `unsafe_precondition_assert!` macro kernel test robot 2025-08-12 18:08 ` Ritvik Gupta
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).