All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Timur Tabi <ttabi@nvidia.com>, Miguel Ojeda <ojeda@kernel.org>,
	Benno Lossin <lossin@kernel.org>,
	Alice Ryhl <aliceryhl@google.com>,
	Danilo Krummrich <dakr@kernel.org>,
	rust-for-linux@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v4] rust: introduce sfile macro for succinct code tracing
Date: Wed, 18 Jun 2025 19:20:30 +0800	[thread overview]
Message-ID: <202506181849.TxpYI9gO-lkp@intel.com> (raw)
In-Reply-To: <20250616193433.2643407-1-ttabi@nvidia.com>

Hi Timur,

kernel test robot noticed the following build errors:

[auto build test ERROR on 27605c8c0f69e319df156b471974e4e223035378]

url:    https://github.com/intel-lab-lkp/linux/commits/Timur-Tabi/rust-introduce-sfile-macro-for-succinct-code-tracing/20250617-034332
base:   27605c8c0f69e319df156b471974e4e223035378
patch link:    https://lore.kernel.org/r/20250616193433.2643407-1-ttabi%40nvidia.com
patch subject: [PATCH v4] rust: introduce sfile macro for succinct code tracing
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250618/202506181849.TxpYI9gO-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
rustc: rustc 1.78.0 (9b00956e5 2024-04-29)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250618/202506181849.TxpYI9gO-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/202506181849.TxpYI9gO-lkp@intel.com/

All errors (new ones prefixed by >>):

>> error[E0432]: unresolved import `kernel::print::rfind_const`
   --> rust/doctests_kernel_generated.rs:7755:5
   |
   7755 | use kernel::print::rfind_const;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^ no `rfind_const` in `print`
--
>> error[E0308]: mismatched types
   --> rust/doctests_kernel_generated.rs:5834:29
   |
   5834 | const SFILE: &'static str = sfile!();
   |                             ^^^^^^^^
   |                             |
   |                             expected `&str`, found `&CStr`
   |                             arguments to this function are incorrect
   |
   = note: expected reference `&str`
   found reference `&'static rust_doctest_kernel_alloc_kbox_rs_7::kernel::prelude::CStr`
   note: method defined here
   --> /opt/cross/rustc-1.78.0-bindgen-0.65.1/rustup/toolchains/1.78.0-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/str/mod.rs:2446:18
   |
   2446 |     pub const fn is_ascii(&self) -> bool {
   |                  ^^^^^^^^
   = note: this error originates in the macro `sfile` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0308]: mismatched types
   --> rust/doctests_kernel_generated.rs:5833:20
   |
   5833 | pr_err!("{}:{}n", sfile!(), line!());
   |                    ^^^^^^^^
   |                    |
   |                    expected `&str`, found `&CStr`
   |                    arguments to this function are incorrect
   |
   = note: expected reference `&str`
   found reference `&'static rust_doctest_kernel_alloc_kbox_rs_7::kernel::prelude::CStr`
   note: method defined here
   --> /opt/cross/rustc-1.78.0-bindgen-0.65.1/rustup/toolchains/1.78.0-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/str/mod.rs:2446:18
   |
   2446 |     pub const fn is_ascii(&self) -> bool {
   |                  ^^^^^^^^
   = note: this error originates in the macro `sfile` (in Nightly builds, run with -Z macro-backtrace for more info)

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

      parent reply	other threads:[~2025-06-18 11:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16 19:34 [PATCH v4] rust: introduce sfile macro for succinct code tracing Timur Tabi
2025-06-16 21:03 ` Miguel Ojeda
2025-06-17  7:29   ` Benno Lossin
2025-06-17  7:54     ` Miguel Ojeda
2025-06-18 20:05       ` Timur Tabi
2025-06-21 16:59         ` Miguel Ojeda
2025-06-26 16:30           ` Timur Tabi
2025-06-26 20:57             ` Miguel Ojeda
2025-06-18 20:07   ` Timur Tabi
2025-06-21 16:47     ` Miguel Ojeda
2025-06-18 11:20 ` kernel test robot [this message]

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=202506181849.TxpYI9gO-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=aliceryhl@google.com \
    --cc=dakr@kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=lossin@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=ttabi@nvidia.com \
    /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.