From: Tom Hochstein <tom.hochstein@oss.nxp.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v5 4/5] oeqa/sdk/meson: improve test to validate host/build target assignments
Date: Thu, 10 Apr 2025 13:58:20 -0500 [thread overview]
Message-ID: <cdae0d74-ade9-4b2b-a0ab-45788cd8044f@oss.nxp.com> (raw)
In-Reply-To: <1834FEA34534143E.27206@lists.openembedded.org>
On 4/10/2025 10:28 AM, Tom Hochstein via lists.openembedded.org wrote:
> On 4/10/2025 8:28 AM, Tom Hochstein via lists.openembedded.org wrote:
>> On 4/8/2025 10:10 AM, Tom Hochstein via lists.openembedded.org wrote:
>>> On 4/8/2025 8:37 AM, Mathieu Dubois-Briand wrote:
>>>> [You don't often get email from mathieu.dubois-briand@bootlin.com.
>>>> Learn why this is important at
>>>> https://aka.ms/LearnAboutSenderIdentification ]
>>>>
>>>> On Mon Apr 7, 2025 at 11:18 PM CEST, Tom Hochstein via
>>>> lists.openembedded.org wrote:
>>>>> From: Ross Burton <ross.burton@arm.com>
>>>>>
>>>>> Use 'meson introspect' to dump JSON describing the build configuration
>>>>> and validate that the build and host architectures are correctly
>>>>> set in
>>>>> the meson.cross file.
>>>>>
>>>>> Also instead of calling ninja directly, call the relevant meson
>>>>> commands.
>>>>>
>>>>> Fixes: [YOCTO #15485]
>>>>> Signed-off-by: Ross Burton <ross.burton@arm.com>
>>>>> Signed-off-by: Tom Hochstein <tom.hochstein@oss.nxp.com>
>>>>> ---
>>>>
>>>> Hi,
>>>>
>>>> Thanks for the new version, but we have a new error now:
>>>>
>>>> Traceback (most recent call last):
>>>> File
>>>> "/srv/pokybuild/yocto-worker/qemux86/build/meta/lib/oeqa/sdk/cases/meson.py", line 47, in test_epoxy
>>>> self.assertNotEqual(data["build"]["c"]["exelist"],
>>>> data["host"]["c"]["exelist"])
>>>> ~~~~~~~~~~~~~^^^^^
>>>> KeyError: 'c'
>>>
>>> Thanks, Mathieu.
>>>
>>> Ross, can you have a look?
>>
>> An update: I thought this was working for me, but I realize now that I
>> may not be running the modified test. This is what I ended up running
>> after looking around using oe-selftest list commands, as it was the
>> only thing that looked close to an SDK meson test:
>>
>> `oe-selftest -r
>> devtool.DevtoolIdeSdkTests.test_devtool_ide_sdk_code_meson`
>>
>> How do I run the modified test?
>>
>
> Never mind, I figured it out and successfully ran `bitbake -c testsdk
> core-image-minimal` with no failures, including the modified test.
>
> RESULTS - meson.MesonTest.test_epoxy: PASSED (19.43s)
>
> Trying now with core-image-sato as is done on the autobuilder.
Unfortunately, I still cannot reproduce the issue. Another variance was
that I had used the default machine qemux86-64, while the autobuilder
test failed using qemux86. I updated the machine, but still cannot
reproduce the error.
>
>>>
>>>>
>>>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/30/builds/1330
>>>>
>>>> Can you have a look at this please?
>>>>
>>>> --
>>>> Mathieu Dubois-Briand, Bootlin
>>>> Embedded Linux and Kernel engineering
>>>> https://bootlin.com
>>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#214680): https://lists.openembedded.org/g/openembedded-core/message/214680
> Mute This Topic: https://lists.openembedded.org/mt/112142020/3617670
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [tom.hochstein@oss.nxp.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2025-04-10 18:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 21:18 [PATCH v5 1/5] toolchain-scripts: Add Meson settings for Yocto build SDK Tom Hochstein
2025-04-07 21:18 ` [PATCH v5 2/5] toolchain-scripts: Export meson settings for SDK builds Tom Hochstein
2025-04-07 21:18 ` [PATCH v5 3/5] meson: Fix host_machine setting for native cross-file Tom Hochstein
2025-04-07 21:18 ` [PATCH v5 4/5] oeqa/sdk/meson: improve test to validate host/build target assignments Tom Hochstein
2025-04-08 13:37 ` [OE-core] " Mathieu Dubois-Briand
2025-04-08 15:10 ` Tom Hochstein
[not found] ` <183460753CA35884.31078@lists.openembedded.org>
2025-04-10 13:28 ` Tom Hochstein
[not found] ` <1834F816ACB44615.7383@lists.openembedded.org>
2025-04-10 15:28 ` Tom Hochstein
[not found] ` <1834FEA34534143E.27206@lists.openembedded.org>
2025-04-10 18:58 ` Tom Hochstein [this message]
2025-04-11 10:01 ` Mathieu Dubois-Briand
[not found] ` <18353B5DF2EF4BC1.27206@lists.openembedded.org>
2025-04-11 10:13 ` Mathieu Dubois-Briand
2025-04-11 15:37 ` Tom Hochstein
2025-04-15 8:29 ` Mathieu Dubois-Briand
2025-04-07 21:18 ` [PATCH v5 5/5] meson: Allow user to override setup command options Tom Hochstein
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=cdae0d74-ade9-4b2b-a0ab-45788cd8044f@oss.nxp.com \
--to=tom.hochstein@oss.nxp.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