From: "Thomas Weißschuh" <linux@weissschuh.net>
To: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, "Thomas Weißschuh" <linux@weissschuh.net>
Subject: [PATCH 0/2] rust: two small improvements for kunit
Date: Sat, 08 Feb 2025 14:31:13 +0100 [thread overview]
Message-ID: <20250208-rust-kunit-v1-0-94a026be6d72@weissschuh.net> (raw)
Two quality of live improvements for running kunit tests for rust/.
While today there are only the doctests, more are coming [0].
$ ./tools/testing/kunit/kunit.py run --kunitconfig rust/
[14:25:48] Configuring KUnit Kernel ...
[14:25:48] Building KUnit Kernel ...
Populating config with:
$ make ARCH=um O=.kunit olddefconfig
Building with:
$ make all compile_commands.json ARCH=um O=.kunit --jobs=16
[14:25:53] Starting KUnit Kernel (1/1)...
[14:25:53] ============================================================
Running tests with:
$ .kunit/linux kunit.enable=1 mem=1G console=tty kunit_shutdown=halt
[14:25:53] =========== rust_doctests_kernel (135 subtests) ============
[14:25:53] [PASSED] rust_doctest_kernel_alloc_kbox_rs_0
...
[14:25:53] [PASSED] rust_doctest_kernel_workqueue_rs_3
[14:25:53] ============== [PASSED] rust_doctests_kernel ===============
[14:25:53] ============================================================
[14:25:53] Testing complete. Ran 135 tests: passed: 135
[14:25:53] Elapsed time: 5.431s total, 0.001s configuring, 5.314s building, 0.086s running
[0] https://lore.kernel.org/rust-for-linux/20241213081035.2069066-1-davidgow@google.com/
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
---
Thomas Weißschuh (2):
rust: pass correct target to bindgen on Usermode Linux
rust: add kunitconfig
rust/.kunitconfig | 3 +++
rust/Makefile | 1 +
2 files changed, 4 insertions(+)
---
base-commit: beeb78d46249cab8b2b8359a2ce8fa5376b5ad2d
change-id: 20250208-rust-kunit-dd350e1a463c
Best regards,
--
Thomas Weißschuh <linux@weissschuh.net>
next reply other threads:[~2025-02-08 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 13:31 Thomas Weißschuh [this message]
2025-02-08 13:31 ` [PATCH 1/2] rust: pass correct target to bindgen on Usermode Linux Thomas Weißschuh
2025-02-10 10:55 ` David Gow
2025-03-18 8:07 ` David Gow
2025-03-18 10:10 ` Miguel Ojeda
2025-03-18 10:14 ` Johannes Berg
2025-03-18 10:34 ` Miguel Ojeda
2025-02-08 13:31 ` [PATCH 2/2] rust: add kunitconfig Thomas Weißschuh
2025-02-10 10:55 ` David Gow
2025-03-20 11:21 ` [PATCH 0/2] rust: two small improvements for kunit 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=20250208-rust-kunit-v1-0-94a026be6d72@weissschuh.net \
--to=linux@weissschuh.net \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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
all inboxes | Powered by JetHome®