From: sundeep.kokkonda@eng.windriver.com
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v14] Rust Oe-Selftest implementation
Date: Tue, 06 Jun 2023 02:47:31 -0700 [thread overview]
Message-ID: <17458.1686044851774043729@lists.openembedded.org> (raw)
In-Reply-To: <32fea4adeae13df4a98727293e9aa82b0f65b87d.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
Hello Richard,
Thank you for review, testing and confirming that oe-selftest is passed. We've worked on the regressions caused with the patch and fixed the issue.
The rust builds (bitbake rust/nativesdk-rust) were not part of our regular oe-selftest so we've not tested those earlier. From now we will make these tests are part of our regular testing.
With latest sources there are a few new test case failures observed and we are working on it.
Also, we see there is a rust 1.70.0 upgrade patch in mailing list. We will send the V15 after rebasing to it.
Thank you,
Sundeep K.
[-- Attachment #2: Type: text/html, Size: 750 bytes --]
next prev parent reply other threads:[~2023-06-06 9:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 10:51 [PATCH v14] Rust Oe-Selftest implementation Yash Shinde
2023-05-30 13:59 ` Richard Purdie
2023-05-30 14:35 ` [OE-core] " Frédéric Martinsons
2023-05-30 14:44 ` Richard Purdie
2023-05-30 15:05 ` Frédéric Martinsons
2023-05-30 18:28 ` Randy MacLeod
2023-05-30 20:48 ` Alexandre Belloni
2023-05-30 21:20 ` Richard Purdie
2023-05-31 0:19 ` Randy MacLeod
2023-05-31 6:19 ` Frédéric Martinsons
2023-05-31 6:49 ` Kokkonda, Sundeep
2023-06-02 7:25 ` Shinde, Yash
2023-06-02 11:32 ` Richard Purdie
2023-06-02 11:42 ` Shinde, Yash
2023-06-06 9:47 ` sundeep.kokkonda [this message]
2023-06-06 11:06 ` [OE-core] " Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2023-05-30 10:48 Yash Shinde
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=17458.1686044851774043729@lists.openembedded.org \
--to=sundeep.kokkonda@eng.windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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