From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <deepesh.varatharajan@windriver.com>,
<openembedded-core@lists.openembedded.org>
Cc: <Shivaprasad.Moodalappa@windriver.com>,
<Sundeep.Kokkonda@windriver.com>,
<Deepesh.Varatharajan@windriver.com>
Subject: Re: [OE-core] [PATCH] rust: restore unit tests that were marked as ignored
Date: Thu, 24 Apr 2025 12:00:06 +0200 [thread overview]
Message-ID: <D9ES53X06ZYS.O2YBSMHAGNG2@bootlin.com> (raw)
In-Reply-To: <20250423112604.3718426-1-Deepesh.Varatharajan@windriver.com>
On Wed Apr 23, 2025 at 1:26 PM CEST, Deepesh via lists.openembedded.org Varatharajan wrote:
> From: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
>
> Some unit tests were previously marked as ignored due to failures
> in earlier Rust versions. Following the upgrade to Rust 1.85.1,
> these tests now pass reliably and have been re-enabled. They have
> been verified to run successfully on the latest version.
>
> Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
> ---
Hi Deepesh,
Thanks for your patch.
I believe we can still see some test failures on the autobuilder:
2025-04-24 08:28:31,576 - oe-selftest - INFO - rust.RustSelfTestSystemEmulated.test_rust (subunit.RemotedTestCase)
2025-04-24 08:28:31,590 - oe-selftest - INFO - ... FAIL
...
test fs::tests::file_lock_drop ... FAILED
https://autobuilder.yoctoproject.org/valkyrie/#/builders/42/builds/1422
Can you have a look at this issue please?
Best regards,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-04-24 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 11:26 [PATCH] rust: restore unit tests that were marked as ignored Deepesh.Varatharajan
2025-04-24 10:00 ` Mathieu Dubois-Briand [this message]
2025-04-29 4:23 ` [OE-core] " Deepesh Varatharajan
2025-04-29 8:26 ` Mathieu Dubois-Briand
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=D9ES53X06ZYS.O2YBSMHAGNG2@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=Shivaprasad.Moodalappa@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=deepesh.varatharajan@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