From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <adrian.freihofer@gmail.com>, <adrian.freihofer@siemens.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2 00/14] IDE SDK Improvements
Date: Tue, 20 Jan 2026 12:59:09 +0100 [thread overview]
Message-ID: <DFTEDVX1EJ4O.ADHORW5LAF40@bootlin.com> (raw)
In-Reply-To: <3fce84b4562ce40c8ee858f36640ca1cfca39b20.camel@gmail.com>
Hi,
On Wed Jan 14, 2026 at 7:37 PM CET, adrian.freihofer wrote:
> Hi Antonin
>
> My proposal for proceeding here is to drop one patch from my series:
> [OE-core] [PATCH v2 13/14]
> oe-selftest: devtool: add test for gdb pretty-printing
>
> This one get killed by patches which are currently on master-next too.
> This makes it almost impossible to fix at the moment.
> When things will settle down, I will test and send this one again.
>
> It is just one more test step which would be nice to have but not
> essential.
> It also fails only on a ARM host, which I cannot reproduce.
>
> All in all just too many floating parts for getting this to final state
> right now.
>
> Could we please proceed with 13 out of 14 patches from my series as a
> next step? Mathieu already hat such a branch for a while.
Sorry for messing up with what Mathieu had on his branch, probably a miss on my
side as I've picked up his work.
I picked your patches again, and while some oe-selftest runs did succeed, I hit
this error, which seem related to your series:
https://autobuilder.yoctoproject.org/valkyrie/api/v2/logs/4983396/raw_inline
From this build:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/3035
It was run with the following commits:
https://git.yoctoproject.org/poky-ci-archive/log/?h=oecore/autobuilder.yoctoproject.org/valkyrie/a-full-3073
I don't recall hitting the issue before having your series in my branch, so to
be sure I ran another build with only your series applied on master, and I still
have the issue:
https://autobuilder.yoctoproject.org/valkyrie/api/v2/logs/5038061/raw_inline
Can you have a look?
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-01-20 11:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 11:46 [PATCH v2 00/14] IDE SDK Improvements AdrianF
2025-12-31 11:46 ` [PATCH v2 01/14] devtool: ide-sdk find bitbake-setup init-build-env AdrianF
2025-12-31 11:46 ` [PATCH v2 02/14] oe-selftest: devtool: DevtoolIdeSdkTests debug logging AdrianF
2025-12-31 11:46 ` [PATCH v2 03/14] cpp-example: run as a service AdrianF
2025-12-31 11:46 ` [PATCH v2 04/14] oe-selftest: devtool: check example services are running AdrianF
2025-12-31 11:46 ` [PATCH v2 05/14] devtool: ide-sdk: add gdbserver attach mode support AdrianF
2025-12-31 11:46 ` [PATCH v2 06/14] devtool: ide-sdk: move code to ide_none AdrianF
2025-12-31 11:46 ` [PATCH v2 07/14] devtool: ide-sdk: make install_and_deploy script pass target arg AdrianF
2025-12-31 11:46 ` [PATCH v2 08/14] devtool: ide-sdk: vscode replace scripts AdrianF
2025-12-31 11:46 ` [PATCH v2 09/14] oe-selftest: devtool ide-sdk cover vscode remote debugging AdrianF
2025-12-31 11:46 ` [PATCH v2 10/14] devtool: ide-sdk: evaluate DEBUG_PREFIX_MAP AdrianF
2025-12-31 11:46 ` [PATCH v2 11/14] cpp-example: Add std::vector example AdrianF
2025-12-31 11:46 ` [PATCH v2 12/14] devtool: ide-sdk: Support GDB pretty-printing for C++ STL types AdrianF
2025-12-31 11:46 ` [PATCH v2 13/14] oe-selftest: devtool: add test for gdb pretty-printing AdrianF
2026-01-02 14:44 ` [OE-core] " Mathieu Dubois-Briand
2025-12-31 11:46 ` [PATCH v2 14/14] oe-selftest: devtool: add compile step in ide-sdk tests AdrianF
2026-01-13 8:17 ` [OE-core] [PATCH v2 00/14] IDE SDK Improvements Antonin Godard
2026-01-14 18:37 ` adrian.freihofer
2026-01-20 11:59 ` Antonin Godard [this message]
2026-01-26 7:47 ` adrian.freihofer
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=DFTEDVX1EJ4O.ADHORW5LAF40@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=adrian.freihofer@gmail.com \
--cc=adrian.freihofer@siemens.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