From: "Bret Barkelew" <bret.barkelew@microsoft.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: UnitTests + Rust = <3
Date: Wed, 15 Jan 2020 01:56:21 +0000 [thread overview]
Message-ID: <CY4PR21MB074395AE6B6DFBE1E51B03E0EF370@CY4PR21MB0743.namprd21.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1622 bytes --]
What’s better than UnitTests almost being ready for deployment in TianoCore?
How about using those UnitTests to validate a native Rust port of one of our VarCheck libs?
Building upon Jiewen’s work (among others) I’ve finally managed to prototype a port of the UefiVariablePolicyLib to Rust, and have shown that it can build as part of our normal CI process and run the same UnitTests that are used for the C version…
https://github.com/corthon/edk2-staging/tree/rust_and_tests
There is a Readme.md in the root directory with a “Notes for this branch” section. All of those steps are important to get Rust set up correctly.
You can run a CI build of MdeModulePkg with the “-t NOOPT” target and it will build the UnitTests. It will build one version against the C library, and another against the Rust library.
You can also run native Rust test cases by going to https://github.com/corthon/edk2-staging/tree/rust_and_tests/MdeModulePkg/Library/UefiVariablePolicyLibRust
And running “cargo test”.
I acknowledge that this code is a little rough. It’s definitely a prototype, but one that I’m excited about and thing that it can be used as a pattern for interop with other core libraries.
I even found a couple small bugs in the original library through the process of porting to Rust, since Rust is so pedantic about covering all possible cases.
Anyway, super interested in any feedback or advice for improvement. 😊
- Bret
PS. Thanks again, Jiewen, for laying the groundwork. I’ve seen several of your contributions to Rust and the UEFI prototype while working on this.
[-- Attachment #2: Type: text/html, Size: 4109 bytes --]
next reply other threads:[~2020-01-15 1:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 1:56 Bret Barkelew [this message]
2020-01-15 2:44 ` UnitTests + Rust = <3 Yao, Jiewen
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-list 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=CY4PR21MB074395AE6B6DFBE1E51B03E0EF370@CY4PR21MB0743.namprd21.prod.outlook.com \
--to=devel@edk2.groups.io \
/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