From: Boqun Feng <boqun.feng@gmail.com>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "David Gow" <davidgow@google.com>,
"Brendan Higgins" <brendan.higgins@linux.dev>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Alice Ryhl" <aliceryhl@google.com>,
"Andreas Hindborg" <nmi@metaspace.dk>,
kunit-dev@googlegroups.com, linux-kselftest@vger.kernel.org,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev
Subject: Re: [PATCH v2 0/7] KUnit integration for Rust doctests
Date: Tue, 18 Jul 2023 11:00:37 -0700 [thread overview]
Message-ID: <ZLbTRZMjcFNAamit@boqun-archlinux> (raw)
In-Reply-To: <20230718052752.1045248-1-ojeda@kernel.org>
On Tue, Jul 18, 2023 at 07:27:45AM +0200, Miguel Ojeda wrote:
[...]
>
> - Collected `Reviewed-by`s and `Tested-by`s, except for the main
> commit due to the substantial changes.
I've applied the series and run the following command:
./tools/testing/kunit/kunit.py run --make_options LLVM=1 --arch x86_64 --kconfig_add CONFIG_RUST=y
everything works as expected, and I also tried modifying one of the
`assert!` to trigger it, all looks good to me. Feel free to add:
Tested-by: Boqun Feng <boqun.feng@gmail.com>
Regards,
Boqun
>
> Miguel Ojeda (7):
> kunit: test-bug.h: include `stddef.h` for `NULL`
> rust: init: make doctests compilable/testable
> rust: str: make doctests compilable/testable
> rust: sync: make doctests compilable/testable
> rust: types: make doctests compilable/testable
> rust: support running Rust documentation tests as KUnit ones
> MAINTAINERS: add Rust KUnit files to the KUnit entry
>
> MAINTAINERS | 2 +
> include/kunit/test-bug.h | 2 +
> lib/Kconfig.debug | 13 ++
> rust/.gitignore | 2 +
> rust/Makefile | 29 ++++
> rust/bindings/bindings_helper.h | 1 +
> rust/helpers.c | 7 +
> rust/kernel/init.rs | 26 +--
> rust/kernel/kunit.rs | 163 +++++++++++++++++++
> rust/kernel/lib.rs | 2 +
> rust/kernel/str.rs | 4 +-
> rust/kernel/sync/arc.rs | 9 +-
> rust/kernel/sync/lock/mutex.rs | 1 +
> v1: https://lore.kernel.org/rust-for-linux/20230614180837.630180-1-ojeda@kernel.org/
> v2:
>
> - Rebased on top of v6.5-rc1, which requires a change from
> `kunit_do_failed_assertion` to `__kunit_do_failed_assertion` (since
> the former became a macro) and the addition of a call to
> `__kunit_abort` (since previously the call was done by the old
> function which we cannot use anymore since it is a macro). (David)
>
> - Added prerequisite patch to KUnit header to include `stddef.h` to
> support the `KUNIT=y` case. (Reported by Boqun)
>
> - Added comment on the purpose of `trait FromErrno`. (Martin asked
> about it)
>
> - Simplify code to use `std::fs::write` instead of `write!`, which
> improves code size too. (Suggested by Alice)
>
> - Fix copy-paste type in docs from "error" to "info" and, to make it
> proper English, copy the `printk` docs style, i.e. from "info"
> to "info-level message" -- and same for the "error" one. (Miguel)
>
> - Swap `FILE` and `LINE` `static`s to keep the same order as done
> elsewhere. (Miguel)
>
> - Rename config option from `RUST_KERNEL_KUNIT_TEST` to
> `RUST_KERNEL_DOCTESTS` (and update its title), so that we can use
> the former for the "normal" (i.e. non-doctests, e.g. `#[test]` ones)
> tests in the future. (David)
>
> - Follow the syntax proposed for declaring test metadata in the KTAP
> v2 spec, which may also get used for the KUnit test attributes API.
>
> Thus, instead of "# Doctest from line {line}", use
> "# {test_name}.location: {file}.{line}", which ideally will allow to
> migrate to a KUnit attribute later.
>
> This is done in all cases, i.e. when the tests succeeds, because
> it may be useful for users running KUnit manually, or when passing
> `--raw_output` to `kunit.py`. (David)
>
> David: I used "location" instead of your suggested "line" alone, in
> order to have both in a single line, which looked nice and closer to
> the "ASSERTION FAILURE" case/line, since now we do have the original
> file (please see below).
>
> - Figure out the original line. This is done by deploying an anchor
> so that the difference in lines between the beginning of the test
> and the assert, in the generated file, can be computed. Then, we
> offset the line number of the original test, which is given by
> `rustdoc`. (developed by Boqun)
>
> - Figure out the original file. This is done by walking the
> filesystem, checking directory prefixes to reduce the amount of
> combinations to check, and it is only done once per file (rather
> than per test).
>
> Ambiguities are detected and reported. It does limit the filenames
> (module names) we can use, but it is unlikely we will hit it soon
> and this should be temporary anyway until `rustdoc` provides us
> with the real path. (Miguel)
>
> Tested with both in-tree and `O=` builds, but I would appreciate
> extra testing on this one, including via the `kunit.py` script.
>
> - The three last items combined means that we now see this output even
> for successful cases:
>
> # rust_doctest_kernel_sync_locked_by_rs_0.location: rust/kernel/sync/locked_by.rs:28
> ok 53 rust_doctest_kernel_sync_locked_by_rs_0
>
> Which basically gives the user all the information they need to go
> back to the source code of the doctest, while keeping them fairly
> stable for bisection, and while avoiding to require users to write
> test names manually. (David + Boqun + Miguel)
>
> David: from what I saw in v2 of the RFC for the test attributes API,
> the syntax still contains the test name when it is not a suite, so
> I followed that, but if you prefer to omit it, please feel free to
> do so (for me either way it is fine, and if this is the expected
> attribute syntax, I guess it is worth to follow it to make migration
> easier later on):
>
> # location: rust/kernel/sync/locked_by.rs:28
> ok 53 rust_doctest_kernel_sync_locked_by_rs_0
> rust/kernel/sync/lock/spinlock.rs | 1 +
> rust/kernel/types.rs | 6 +-
> scripts/.gitignore | 2 +
> scripts/Makefile | 4 +
> scripts/rustdoc_test_builder.rs | 72 +++++++++
> scripts/rustdoc_test_gen.rs | 260 ++++++++++++++++++++++++++++++
> 19 files changed, 591 insertions(+), 15 deletions(-)
> create mode 100644 rust/kernel/kunit.rs
> create mode 100644 scripts/rustdoc_test_builder.rs
> create mode 100644 scripts/rustdoc_test_gen.rs
>
>
> base-commit: 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5
> --
> 2.41.0
>
next prev parent reply other threads:[~2023-07-18 18:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 5:27 [PATCH v2 0/7] KUnit integration for Rust doctests Miguel Ojeda
2023-07-18 5:27 ` [PATCH v2 1/7] kunit: test-bug.h: include `stddef.h` for `NULL` Miguel Ojeda
2023-07-18 8:08 ` David Gow
2023-07-18 5:27 ` [PATCH v2 2/7] rust: init: make doctests compilable/testable Miguel Ojeda
2023-07-18 5:27 ` [PATCH v2 3/7] rust: str: " Miguel Ojeda
2023-07-18 5:27 ` [PATCH v2 4/7] rust: sync: " Miguel Ojeda
2023-07-18 5:27 ` [PATCH v2 5/7] rust: types: " Miguel Ojeda
2023-07-18 5:27 ` [PATCH v2 6/7] rust: support running Rust documentation tests as KUnit ones Miguel Ojeda
2023-07-18 8:17 ` David Gow
2023-07-18 10:50 ` Miguel Ojeda
2023-07-20 6:36 ` David Gow
2023-07-20 9:59 ` Miguel Ojeda
2023-07-18 5:27 ` [PATCH v2 7/7] MAINTAINERS: add Rust KUnit files to the KUnit entry Miguel Ojeda
2023-07-18 8:38 ` [PATCH v2 0/7] KUnit integration for Rust doctests David Gow
2023-07-18 10:50 ` Miguel Ojeda
2023-07-18 18:00 ` Boqun Feng [this message]
2023-07-20 19:28 ` Miguel Ojeda
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=ZLbTRZMjcFNAamit@boqun-archlinux \
--to=boqun.feng@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=brendan.higgins@linux.dev \
--cc=davidgow@google.com \
--cc=gary@garyguo.net \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=nmi@metaspace.dk \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.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 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).