public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Sundeep KOKKONDA <Sundeep.Kokkonda@windriver.com>
To: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
	Harish Sadineni <Harish.Sadineni@windriver.com>,
	Yoann Congal <yoann.congal@smile.fr>,
	openembedded-core@lists.openembedded.org
Cc: Randy.MacLeod@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, 23 Feb 2026 16:49:48 +0530	[thread overview]
Message-ID: <176df973-9458-449f-b166-308847608822@windriver.com> (raw)
In-Reply-To: <DGM5RWWI8ITI.1N1WPFMB4FBJB@bootlin.com>


On 23-Feb-26 12:51, 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 Tue Feb 17, 2026 at 6:01 PM CET, Mathieu Dubois-Briand wrote:
>> 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
>>
>> 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.
>>
> Hi Harish,
>
> Do you need any file from this build before it is removed?

Hello Mathieu,

I copied the build logs and we will be looking into the failures.


Thanks,

Sundeep K.

>
> Thanks,
> Mathieu
>
> --
> Mathieu Dubois-Briand, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>


  reply	other threads:[~2026-02-23 11:20 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 [this message]
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=176df973-9458-449f-b166-308847608822@windriver.com \
    --to=sundeep.kokkonda@windriver.com \
    --cc=Harish.Sadineni@windriver.com \
    --cc=Randy.MacLeod@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