From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Pgowda" <pgowda.cve@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
richard.purdie@linuxfoundation.org, rwmacleod@gmail.com,
Vinay Kumar <vinay.m.engg@gmail.com>
Subject: Re: [OE-core] [PATCH v6] Rust Oe-Selftest implementation
Date: Tue, 2 Aug 2022 10:38:33 +0200 [thread overview]
Message-ID: <20220802103833.0b32b669@booty> (raw)
In-Reply-To: <20220802035352.1497111-1-pgowda.cve@gmail.com>
On Tue, 2 Aug 2022 09:23:52 +0530
"Pgowda" <pgowda.cve@gmail.com> wrote:
> From: pgowda <pgowda.cve@gmail.com>
>
> The patch implements Rust testing framework similar to other selftest,
> specifically the gcc selftest in OE. It uses the client and server
> based method to test the binaries for cross-target on the image.
> The test framework is a wrapper around the Rust build system as ./x.py
> test.
> It tests many functionalities of Rust distribution like tools,
> documentation, libraries, packages, tools, Cargo, Crater etc.
> Please refer the following link for detailed description of Rust
> testing:-
> https://rustc-dev-guide.rust-lang.org/tests/intro.html#tool-tests
>
> To support the rust tests in oe-core, the following functions were
> added:-
> setup_cargo_environment(): Build bootstrap and some early stage tools.
> do_rust_setup_snapshot(): Install the snapshot version of rust binaries.
> do_configure(): To generate config.toml
> do_compile(): To build "remote-test-server" for qemu target image.
>
> Approximate Number of Tests Run in the Rust Testsuite :- 18000
> Approximate Number of Tests that FAIL in bitbake environment :- 100-150
> Normally majority of the testcases are present in major folder "test/"
> It contributes to more than 80% of the testcases present in Rust test
> framework. These tests pass as expected on any Rust versions without
> much fuss. The tests that fail are of less important and contribute to
> less than 2% of the total testcases. These minor tests are observed to
> work on some versions and fail on others. They have to be added, ignored
> or excluded for different versions as per the behavior.
> These tests have been ignored or excluded in the Rust selftest
> environment to generate success of completing the testsuite.
>
> These tests work in parallel mode even in the skipped test mode as
> expected. Although the patch to disable tests is large, it is very simple
> in that it only disables tests. When updating to a newer version of Rust,
> the patch can usually be ported in a day.
>
> Signed-off-by: pgowda <pgowda.cve@gmail.com>
> Signed-off-by: Vinay Kumar <vinay.m.engg@gmail.com>
> ---
> meta/classes/rust-target-config.bbclass | 2 +-
> meta/lib/oeqa/selftest/cases/rust.py | 57 +++
> meta/recipes-devtools/rust/rust-testsuite.inc | 164 ++++++
> .../rust-testsuite/rust-oe-selftest.patch | 477 ++++++++++++++++++
> .../rust/rust-testsuite_1.62.0.bb | 3 +
> 5 files changed, 702 insertions(+), 1 deletion(-)
> create mode 100644 meta/lib/oeqa/selftest/cases/rust.py
> create mode 100644 meta/recipes-devtools/rust/rust-testsuite.inc
> create mode 100644 meta/recipes-devtools/rust/rust-testsuite/rust-oe-selftest.patch
> create mode 100644 meta/recipes-devtools/rust/rust-testsuite_1.62.0.bb
>
> diff --git a/meta/classes/rust-target-config.bbclass b/meta/classes/rust-target-config.bbclass
> index 87b7dee3ed..26dc931971 100644
> --- a/meta/classes/rust-target-config.bbclass
> +++ b/meta/classes/rust-target-config.bbclass
> @@ -344,7 +344,7 @@ def rust_gen_target(d, thing, wd, arch):
> tspec['linker-is-gnu'] = True
> tspec['linker-flavor'] = "gcc"
> tspec['has-rpath'] = True
> - tspec['has-elf-tls'] = True
> +# tspec['has-elf-tls'] = True
I'm not sure of the meaning of the above change, can you clarify that?
Thanks.
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-08-02 8:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 3:53 [PATCH v6] Rust Oe-Selftest implementation pgowda.cve
2022-08-02 8:38 ` Luca Ceresoli [this message]
2022-08-02 9:07 ` [OE-core] " pgowda cve
2022-08-02 9:52 ` Luca Ceresoli
2022-08-02 12:22 ` pgowda cve
-- strict thread matches above, loose matches on Subject: below --
2022-05-24 20:56 [OE-core] [PATCH v5] " Luca Ceresoli
2022-05-25 4:32 ` [PATCH v6] " pgowda
2022-05-25 7:57 ` [OE-core] " Luca Ceresoli
[not found] ` <16F24A16BC7F056F.12338@lists.openembedded.org>
2022-05-31 13:05 ` Luca Ceresoli
2022-06-03 13:07 ` pgowda cve
2022-06-06 8:51 ` Richard Purdie
2022-06-29 8:18 ` pgowda cve
2022-06-29 16:19 ` Khem Raj
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=20220802103833.0b32b669@booty \
--to=luca.ceresoli@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pgowda.cve@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=rwmacleod@gmail.com \
--cc=vinay.m.engg@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 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.