public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Harish Sadineni <Harish.Sadineni@windriver.com>
To: Yoann Congal <yoann.congal@smile.fr>,
	Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
	openembedded-core@lists.openembedded.org
Cc: Randy.MacLeod@windriver.com, Sundeep.Kokkonda@windriver.com,
	bruce.ashfield@gmail.com, paul@pbarker.dev,
	elmehdi.younes@smile.fr
Subject: Re: [OE-core] [PATCH v6 09/14] selftest/cases/runtime_test: Add test for Linux Rust sample
Date: Mon, 16 Feb 2026 18:39:54 +0530	[thread overview]
Message-ID: <7d5ca94b-0062-44ae-b941-5401bbc56aae@windriver.com> (raw)
In-Reply-To: <DGFP3A56EZTR.1TWUE93WL575C@smile.fr>

[-- Attachment #1: Type: text/plain, Size: 3573 bytes --]


On 2/15/2026 10:31 PM, Yoann Congal 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 Sun Feb 15, 2026 at 2:40 PM CET, Mathieu Dubois-Briand wrote:
>> On Thu Feb 12, 2026 at 7:10 PM CET, Harish via lists.openembedded.org Sadineni wrote:
>>> From: Yoann Congal<yoann.congal@smile.fr>
>>>
>>> This new case tests that the rust_mininal sample inside the kernel source
>>> tree is buildable and works properly: check that the module can be
>>> loaded and that it prints correctly.
>>>
>>> Signed-off-by: Yoann Congal<yoann.congal@smile.fr>
>>> Signed-off-by: Harish Sadineni<Harish.Sadineni@windriver.com>
>>> ---
>> Hi Harish, Yoann,
>>
>> It looks like this test is still a bit intermittent:
>>
>> 2026-02-15 09:27:44,140 - oe-selftest - INFO - runtime_test.RustKernel.test_kernel_rust_sample (subunit.RemotedTestCase)
>> 2026-02-15 09:27:44,142 - oe-selftest - INFO -  ... FAIL
>> ...
>> 2026-02-15 09:27:44,142 - oe-selftest - INFO - 11: 13/57 404/671 (87.99s) (0 failed) (runtime_test.RustKernel.test_kernel_rust_sample)
>> 2026-02-15 09:27:44,142 - oe-selftest - INFO - testtools.testresult.real._StringException: Traceback (most recent call last):
>>    File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/runtime_test.py", line 506, in test_kernel_rust_sample
>>      self.assertEqual(status, 1, "Loading rust_minimal module failed!")
>>      ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>    File "/usr/lib/python3.13/unittest/case.py", line 907, in assertEqual
>>      assertion_func(first, second, msg=msg)
>>      ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
>>    File "/usr/lib/python3.13/unittest/case.py", line 900, in _baseAssertEqual
>>      raise self.failureException(msg)
>> AssertionError: 0 != 1 : Loading rust_minimal module failed!
>>
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/3319
> This is oe-selftest-armhost on ubuntu2504-vk-arm1.
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

>
> Harish, do you have access to an ARM host to reproduce/debug this?
> (I have looked but the builddir for this particular run was already deleted)
>
> --
> Yoann Congal
> Smile ECS
>

[-- Attachment #2: Type: text/html, Size: 5133 bytes --]

  reply	other threads:[~2026-02-16 13:10 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 [this message]
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
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=7d5ca94b-0062-44ae-b941-5401bbc56aae@windriver.com \
    --to=harish.sadineni@windriver.com \
    --cc=Randy.MacLeod@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=elmehdi.younes@smile.fr \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul@pbarker.dev \
    --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