From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Pgowda" <pgowda.cve@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Alexander Kanavin <alex.kanavin@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Randy MacLeod <rwmacleod@gmail.com>,
Vinay Kumar <vinay.m.engg@gmail.com>
Subject: Re: [OE-core] [PATCH v5] Rust Oe-Selftest implementation
Date: Tue, 24 May 2022 22:56:03 +0200 [thread overview]
Message-ID: <20220524225603.50d60963@melee> (raw)
In-Reply-To: <CALY4987EVjw2cMmRSo78+Pjq7ToDnzD_zbS+c=Rg4LoRZ3DC+g@mail.gmail.com>
hi Pgowda,
Il giorno Tue, 24 May 2022 17:23:04 +0530
"Pgowda" <pgowda.cve@gmail.com> ha scritto:
> Gentle Ping on the following patch
>
> On Fri, May 13, 2022 at 5:50 PM pgowda <pgowda.cve@gmail.com> wrote:
> >
> > 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>
This patch is ailing on the autobuilders:
The following recipes do not have a maintainer assigned to them. Please
add an entry to meta/conf/distro/include/maintainers.inc file.
rust-testsuite
(/home/pokybuild/yocto-worker/oe-selftest-centos/build/meta/recipes-devtools/rust/rust-testsuite_1.60.0.bb)
https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/3623/steps/15/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/3565/steps/14/logs/stdio
Can you resend with that fixed?
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-05-24 20:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 12:20 [PATCH v5] Rust Oe-Selftest implementation pgowda
2022-05-24 11:53 ` pgowda cve
2022-05-24 20:56 ` Luca Ceresoli [this message]
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=20220524225603.50d60963@melee \
--to=luca.ceresoli@bootlin.com \
--cc=alex.kanavin@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox