rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Guillaume Gomez <guillaume1.gomez@gmail.com>,
	linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
	ojeda@kernel.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 1/1] Use new `--output-format=doctest` rustdoc command line flag to improve doctest handling
Date: Wed, 18 Jun 2025 13:50:26 +0800	[thread overview]
Message-ID: <202506181334.f0STx6ta-lkp@intel.com> (raw)
In-Reply-To: <20250617140032.1133337-2-guillaume1.gomez@gmail.com>

Hi Guillaume,

kernel test robot noticed the following build errors:

[auto build test ERROR on rust/rust-next]
[also build test ERROR on shuah-kselftest/kunit shuah-kselftest/kunit-fixes linus/master v6.16-rc2 next-20250617]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Guillaume-Gomez/Use-new-output-format-doctest-rustdoc-command-line-flag-to-improve-doctest-handling/20250617-220502
base:   https://github.com/Rust-for-Linux/linux rust-next
patch link:    https://lore.kernel.org/r/20250617140032.1133337-2-guillaume1.gomez%40gmail.com
patch subject: [PATCH 1/1] Use new `--output-format=doctest` rustdoc command line flag to improve doctest handling
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250618/202506181334.f0STx6ta-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/202506181334.f0STx6ta-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/202506181334.f0STx6ta-lkp@intel.com/

All errors (new ones prefixed by >>):

   PATH=/opt/cross/clang-18/bin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
   INFO PATH=/opt/cross/rustc-1.78.0-bindgen-0.65.1/cargo/bin:/opt/cross/clang-18/bin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
   /usr/bin/timeout -k 100 12h /usr/bin/make KCFLAGS= -Wno-error=return-type -Wreturn-type -funsigned-char -Wundef W=1 --keep-going LLVM=1 -j32 -C source O=/kbuild/obj/consumer/x86_64-rhel-9.4-rust ARCH=x86_64 SHELL=/bin/bash rustfmtcheck
   make: Entering directory '/kbuild/src/consumer'
   make[1]: Entering directory '/kbuild/obj/consumer/x86_64-rhel-9.4-rust'
>> Diff in scripts/rustdoc_test_builder.rs at line 16:
    //! the `gen` script (done there since we need to be aware of all the tests in a given file).
    
    use std::collections::HashMap;
   -use std::io::Read;
    use std::fs::create_dir_all;
   +use std::io::Read;
    
    use json::JsonValue;
    
   Diff in scripts/rustdoc_test_builder.rs at line 25:
    
    fn generate_doctest(file: &str, line: i32, doctest_code: &HashMap<String, JsonValue>) -> bool {
        // FIXME: Once let chain feature is stable, please use it instead.
   -    let Some(JsonValue::Object(wrapper)) = doctest_code.get("wrapper") else { return false };
   -    let Some(JsonValue::String(before)) = wrapper.get("before") else { return false };
   -    let Some(JsonValue::String(after)) = wrapper.get("after") else { return false };
   -    let Some(JsonValue::String(code)) = doctest_code.get("code") else { return false };
   -    let Some(JsonValue::String(crate_level_code)) = doctest_code.get("crate_level") else { return false };
   +    let Some(JsonValue::Object(wrapper)) = doctest_code.get("wrapper") else {
   +        return false;
   +    };
   +    let Some(JsonValue::String(before)) = wrapper.get("before") else {
   +        return false;
   +    };
   +    let Some(JsonValue::String(after)) = wrapper.get("after") else {
   +        return false;
   +    };
   +    let Some(JsonValue::String(code)) = doctest_code.get("code") else {
   +        return false;
   +    };
   +    let Some(JsonValue::String(crate_level_code)) = doctest_code.get("crate_level") else {
   +        return false;
   +    };
    
        // For tests that get generated with `Result`, `rustdoc` generates an `unwrap()` on
        // the return value to check there were no returned errors. Instead, we use our assert macro
   make[1]: Leaving directory '/kbuild/obj/consumer/x86_64-rhel-9.4-rust'
   make[2]: *** [Makefile:1825: rustfmt] Error 123
   make[2]: Target 'rustfmtcheck' not remade because of errors.
   make[1]: *** [Makefile:248: __sub-make] Error 2
   make[1]: Target 'rustfmtcheck' not remade because of errors.
   make: *** [Makefile:248: __sub-make] Error 2
   make: Target 'rustfmtcheck' not remade because of errors.
   make: Leaving directory '/kbuild/src/consumer'

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

  reply	other threads:[~2025-06-18  5:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 14:00 [PATCH 1/1] Use new `--output-format=doctest` rustdoc command line flag to improve doctest handling Guillaume Gomez
2025-06-18  5:50 ` kernel test robot [this message]
2025-06-18  6:19   ` Miguel Ojeda
2025-10-09  9:14 ` Miguel Ojeda
2025-10-18  7:18   ` David Gow
  -- strict thread matches above, loose matches on Subject: below --
2025-02-28 13:29 Guillaume Gomez
2025-02-28 15:43 ` Miguel Ojeda
2025-02-28 16:33   ` Guillaume Gomez
2025-02-28 16:38   ` Guillaume Gomez
     [not found]   ` <CAAOQCfSEUnp8U3+6amWCd6+yPrAmPy6gsjJnQdrqmpER5md3kA@mail.gmail.com>
2025-02-28 16:48     ` Miguel Ojeda
2025-02-28 16:55       ` Guillaume Gomez
2025-02-28 13:25 Guillaume Gomez

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=202506181334.f0STx6ta-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=guillaume1.gomez@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).