From: Harish Sadineni <Harish.Sadineni@windriver.com>
To: Yoann Congal <yoann.congal@smile.fr>,
openembedded-core@lists.openembedded.org
Cc: Randy.MacLeod@windriver.com, Sundeep.Kokkonda@windriver.com,
Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Subject: Re: [OE-core] [PATCH v6 09/14] selftest/cases/runtime_test: Add test for Linux Rust sample
Date: Wed, 4 Mar 2026 18:09:02 +0530 [thread overview]
Message-ID: <56f69f79-77b8-4bdc-8401-f51d3e7d3bed@windriver.com> (raw)
In-Reply-To: <DGHECF0K4Z1P.2HFBCFPWDKJQ2@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 3249 bytes --]
On 2/17/2026 10:31 PM, Mathieu Dubois-Briand wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Mon Feb 16, 2026 at 4:48 PM CET, Mathieu Dubois-Briand wrote:
>> On Mon Feb 16, 2026 at 2:09 PM CET, Harish Sadineni wrote:
>>> Hi Yoann, Mathieu,
>>>
>>> I tried few builds locally, but not able to reproduce this.
>>>
>>> On the autobuilder, We ran following builds which were completed
>>> successfully on ubuntu2504-vk-arm1:
>>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/3326
>>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/3331
>>>
>>> Additionally, One of Mathieu's build also ran successfully on
>>> oe-selftest-armhost ubuntu2504-vk-arm1:
>>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/3323
>>> <https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/3323>
>>> From what I can see, build 3319
>>> <https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/3319>was
>>> triggered from a-full/3219
>>> <https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3219>:
>>> However, when checking a-full/3219, it triggered build 3317
>>> <https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/3317>,
>>> where the rust kernel selftest passed.
>>>
>>> I can see few other builds were successful on oe-selftest-armhost with
>>> this patch series. I’m not sure why the failure occurred in this case.
>>> Mathieu, could you please try running a few additional builds to see if
>>> it reproduces?
>>>
>>> Thanks,
>>> Harish
>> Sure, I will launch a few builds and see how it goes.
>>
>> AB maintenance will begin soon, so I will start either later today or
>> tomorrow morning.
> I believe I got one:
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/3346
Hi Yoann,
We performed few build with additional debug logging on autobuilder to
investigate why the test case was failing.
From the analysis, we observed that the failure occurs because
*qemu.run_serial("modprobe rust_minimal") *intermittently returns status
as *0*.
This causes the assertion to fail, even though the module is actually
loading successfully via modprobe.
To address this instability, we are removing**the assertion that depends
on the return status of*qemu.run_serial("modprobe rust_minimal")*.
Instead, we will rely on on the existing*dmesg *validation to confirm
whether the module has been successfully loaded.
The build with debug logging can be found at the following link:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/3432/steps/15/logs/stdio
The relevant debug information is visible around lines 1202–1204.
Thanks,
Harish
>
> I backed up the build folder, it should stay there until next Monday.
> (/srv/pokybuild/yocto-worker/oe-selftest-armhost-3346-mathieu-2026-02-17
> on ubuntu2404-vk-arm1)
>
> Please tell me if you need me to extract any build artifact.
>
> Thanks,
> Mathieu
>
> --
> Mathieu Dubois-Briand, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
[-- Attachment #2: Type: text/html, Size: 5262 bytes --]
next prev parent reply other threads:[~2026-03-04 12:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 18:10 [PATCH v6 05/14] kernel-yocto-rust: Fix for buildpaths errors when rust is enabled for kernel Harish.Sadineni
2026-02-12 18:10 ` [PATCH v6 06/14] make-mod-scripts: split `HOSTCC` flag to align with to linux-yocto Harish.Sadineni
2026-02-12 18:10 ` [PATCH v6 07/14] kernel: Disable ccache when kernel rust support is enabled Harish.Sadineni
2026-02-26 22:59 ` [OE-core] " Yoann Congal
2026-02-12 18:10 ` [PATCH v6 08/14] kernel-devsrc: copying rust-kernel source to $kerneldir/build Harish.Sadineni
2026-02-12 18:10 ` [PATCH v6 09/14] selftest/cases/runtime_test: Add test for Linux Rust sample Harish.Sadineni
2026-02-15 13:40 ` [OE-core] " Mathieu Dubois-Briand
2026-02-15 17:01 ` Yoann Congal
2026-02-16 13:09 ` Harish Sadineni
2026-02-16 15:48 ` Mathieu Dubois-Briand
2026-02-17 17:01 ` Mathieu Dubois-Briand
2026-02-23 7:21 ` Mathieu Dubois-Briand
2026-02-23 11:19 ` Sundeep KOKKONDA
2026-02-27 13:33 ` Harish Sadineni
2026-03-04 12:39 ` Harish Sadineni [this message]
2026-02-12 18:10 ` [PATCH v6 10/14] kernel.bbclass: Copy include/config/auto.conf in STAGING_KERNEL_BUILDDIR Harish.Sadineni
2026-02-12 18:10 ` [PATCH v6 11/14] module-rust.bbclass: Prepare out-of-tree rust module compilation Harish.Sadineni
2026-02-12 18:10 ` [PATCH v6 12/14] meta-skeleton: Add rust-out-of-tree-module recipe Harish.Sadineni
2026-02-12 18:10 ` [PATCH v6 13/14] make-mod-scripts: fix for buildpath issues with rust-out-of-tree compilation Harish.Sadineni
2026-02-12 18:10 ` [PATCH v6 14/14] runtime_test: Add rust-out-of-tree selftest Harish.Sadineni
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=56f69f79-77b8-4bdc-8401-f51d3e7d3bed@windriver.com \
--to=harish.sadineni@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yoann.congal@smile.fr \
/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