From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <ankur.tyagi85@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH 1/7] bluez5: upgrade 5.87 -> 5.88
Date: Tue, 10 Nov 2026 17:52:15 +0100 [thread overview]
Message-ID: <DMROQGZJRL7N.3QN1UPWBZNROY@bootlin.com> (raw)
In-Reply-To: <20261110035229.2940188-1-ankur.tyagi85@gmail.com>
On Tue Nov 10, 2026 at 4:52 AM CET, Ankur Tyagi via openembedded-core wrote:
> From: Ankur Tyagi <ankur.tyagi85@gmail.com>
>
> - Upstream deprecated gatttool[1]
> - Dropped patches that are merged in the upstream version
> - Refreshed 0001-tests-add-a-target-for-building-tests-without-runnin.patch
>
> Changelog:
> https://github.com/bluez/bluez/releases/tag/5.88
>
> [1]https://github.com/bluez/bluez/commit/a7da60ed45e9b7aea429f1472588c9070ebecdf7
>
> Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
> ---
Hi Ankur,
Thanks for the upgrade.
I can see some failing ptest:
WARNING: core-image-ptest-bluez5-1.0-r0 do_testimage: There were failing ptests.
Traceback (most recent call last):
File "/srv/pokybuild/yocto-worker/qemuriscv64-ptest/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
return func(*args, **kwargs)
File "/srv/pokybuild/yocto-worker/qemuriscv64-ptest/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
return func(*args, **kwargs)
File "/srv/pokybuild/yocto-worker/qemuriscv64-ptest/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
return func(*args, **kwargs)
File "/srv/pokybuild/yocto-worker/qemuriscv64-ptest/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/ptest.py", line 27, in test_ptestrunner_expectfail
self.do_ptestrunner()
~~~~~~~~~~~~~~~~~~~^^
File "/srv/pokybuild/yocto-worker/qemuriscv64-ptest/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/ptest.py", line 121, in do_ptestrunner
self.fail(failmsg)
~~~~~~~~~^^^^^^^^^
AssertionError:
Failed ptests:
{'bluez5': ['test-sdp-xml']}
https://autobuilder.yoctoproject.org/valkyrie/#/builders/109/builds/1540
https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/1560
https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/2769
Can you have a look at the issue?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-11-10 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 3:52 [OE-core][PATCH 1/7] bluez5: upgrade 5.87 -> 5.88 ankur.tyagi85
2026-11-10 3:52 ` [OE-core][PATCH 2/7] ppp: upgrade 2.5.4 -> 2.5.5 ankur.tyagi85
2026-11-10 3:52 ` [OE-core][PATCH 3/7] apt: upgrade 3.0.3 -> 3.0.4 ankur.tyagi85
2026-11-10 3:52 ` [OE-core][PATCH 4/7] ccache: upgrade 4.14.2 -> 4.14.3 ankur.tyagi85
2026-11-10 3:52 ` [OE-core][PATCH 5/7] desktop-file-utils: upgrade 0.28 -> 0.29 ankur.tyagi85
2026-11-10 3:52 ` [OE-core][PATCH 6/7] stress-ng: upgrade 0.22.01 -> 0.22.02 ankur.tyagi85
2026-11-10 6:03 ` Babanpreet Singh
2026-11-10 3:52 ` [OE-core][PATCH 7/7] libarchive: upgrade 3.8.10 -> 3.8.11 ankur.tyagi85
2026-11-10 16:52 ` Mathieu Dubois-Briand [this message]
2026-11-10 21:52 ` [OE-core][PATCH 1/7] bluez5: upgrade 5.87 -> 5.88 Ankur Tyagi
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=DMROQGZJRL7N.3QN1UPWBZNROY@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=ankur.tyagi85@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.