From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2F841C28B30 for ; Sun, 23 Mar 2025 17:31:57 +0000 (UTC) Subject: Re: [PATCH] bluez5: upgrade 5.79 -> 5.80 To: openembedded-core@lists.openembedded.org From: =?UTF-8?B?R3XDsG5pIE3DoXIgR2lsYmVydA==?= X-Originating-Location: Kopavogur, Capital Region, IS (81.15.100.92) X-Originating-Platform: Windows Firefox 136 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Sun, 23 Mar 2025 10:31:53 -0700 References: <1298.1742735985396496900@lists.openembedded.org> In-Reply-To: <1298.1742735985396496900@lists.openembedded.org> Message-ID: <15989.1742751113848859897@lists.openembedded.org> Content-Type: multipart/alternative; boundary="7pWSchpm4uArsCgpPNfb" List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Sun, 23 Mar 2025 17:31:57 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/213507 --7pWSchpm4uArsCgpPNfb Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I managed to reproduce this locally using QEMU. It looks like to me this is= not a new issue, see the following two Github issues which are mostly repo= rt from users with Alpine Linux using musl: * https://github.com/bluez/bluez/issues/683 * https://github.com/bluez/bluez/issues/726 There is a theory in one of the Github issues that the problem is related t= o enabling LTO. I'm not sure how to proceed/debug this exactly but I'll at = least add my input into the Github issue in case it helps. Moving forward... is it acceptable to disable running this test? I don't pe= rsonally like it as it is likely it won't be enabled again. For reference, these are the commands I used: On host machine: 1) source layers/openembedded-core/oe-init-build-env 2) bitbake core-image-ptest-bluez5 3) runqemu qemux86-64 core-image-ptest-bluez5 slirp nographic Within the QEMU image terminal: 1) ptest-runner bluez5 In local.conf I added: TCLIBC=3D"musl" DISTRO_FEATURES:append =3D " ptest" EXTRA_IMAGE_FEATURES +=3D "ptest-pkgs" IMAGE_FEATURES:append =3D " allow-empty-password empty-root-password allow-= root-login" # (I was having some trouble with the root login, this line see= med to work for QEMU) Best regards Gudni --7pWSchpm4uArsCgpPNfb Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
I managed to reproduce this locally using QEMU. It looks like to me th= is is not a new issue, see the following two Github issues which are mostly= report from users with Alpine Linux using musl:
 
 
There is a theory in one of the Github issues that the problem is rela= ted to enabling LTO. I'm not sure how to proceed/debug this exactly but I'l= l at least add my input into the Github issue in case it helps.
 
Moving forward... is it acceptable to disable running this test? I don= 't personally like it as it is likely it won't be enabled again.
 
 
For reference, these are the commands I used:
 
On host machine:
 
1) source layers/openembedded-core/oe-init-build-env
2) bitbake core-image-ptest-bluez5
3) runqemu qemux86-64 core-image-ptest-bluez5 slirp nographic
 
Within the QEMU image terminal:
1) ptest-runner bluez5
 
In local.conf I added:
TCLIBC=3D"musl"
DISTRO_FEATURES:append =3D " ptest"
EXTRA_IM= AGE_FEATURES +=3D "ptest-pkgs"
IMAGE_FEATURES:append =3D " allow-empty-password empty-root-password a= llow-root-login" # (I was having some trouble with the root login, this lin= e seemed to work for QEMU)
 
Best regards
Gudni
 
--7pWSchpm4uArsCgpPNfb--