From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <adrian.freihofer@siemens.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2 0/3] fragments: add a 'devtool-ide-sdk' fragment
Date: Mon, 29 Dec 2025 14:13:22 +0100 [thread overview]
Message-ID: <DFAQ6QDTDTS4.3M7RPQAK1GZP0@bootlin.com> (raw)
In-Reply-To: <20251228180935.2077478-1-adrian.freihofer@siemens.com>
On Sun Dec 28, 2025 at 7:08 PM CET, Adrian Freihofer via lists.openembedded.org wrote:
> From: Adrian Freihofer <adrian.freihofer@siemens.com>
>
> Changes in comparison to v1:
> - Drop the insecure root login part from the fragment description.
> - Add support for fragments in write_config.
> - Use the ide-sdk fragment in the ide_sdk selftest.
>
> Adrian Freihofer (3):
> fragments: add a 'devtool-ide-sdk' fragment
> oe-selftest: case: support fragments in write_config
> oe-selftest: ide_sdk: use the ide-sdk fragment
>
> .../conf/fragments/yocto/devtool-ide-sdk.conf | 26 +++++++++++++++++++
> meta/lib/oeqa/selftest/case.py | 9 ++++++-
> meta/lib/oeqa/selftest/cases/devtool.py | 8 +++---
> meta/lib/oeqa/selftest/context.py | 1 +
> 4 files changed, 38 insertions(+), 6 deletions(-)
> create mode 100644 meta/conf/fragments/yocto/devtool-ide-sdk.conf
Hi Adrian,
Thanks for your patches.
It looks like it is breaking some test:
2025-12-29 09:09:18,661 - oe-selftest - INFO - gdbserver.GdbServerTest.test_gdb_server (subunit.RemotedTestCase)
2025-12-29 09:09:18,661 - oe-selftest - INFO - ... ERROR
File "/srv/pokybuild/yocto-worker/oe-selftest-fedora/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/gdbserver.py", line 42, in test_gdb_server
shutil.unpack_archive(filename, debugfs)
File "/usr/lib64/python3.9/shutil.py", line 1278, in unpack_archive
func(filename, extract_dir, **kwargs)
File "/usr/lib64/python3.9/shutil.py", line 1199, in _unpack_tarfile
tarobj = tarfile.open(filename)
File "/usr/lib64/python3.9/tarfile.py", line 1848, in open
return func(name, "r", fileobj, **kwargs)
File "/usr/lib64/python3.9/tarfile.py", line 1912, in gzopen
fileobj = GzipFile(name, mode + "b", compresslevel, fileobj)
File "/usr/lib64/python3.9/gzip.py", line 173, in __init__
fileobj = self.myfileobj = builtins.open(filename, mode or 'rb')
FileNotFoundError: [Errno 2] No such file or directory: '/srv/pokybuild/yocto-worker/oe-selftest-fedora/build/build-st-4140890/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.rootfs-dbg.tar.bz2'
https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/2816
https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/2923
https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/3060
Can you have a look at what's wrong here?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-12-29 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-28 18:08 [PATCH v2 0/3] fragments: add a 'devtool-ide-sdk' fragment AdrianF
2025-12-28 18:08 ` [PATCH v2 1/3] " AdrianF
2025-12-28 18:08 ` [PATCH v2 2/3] oe-selftest: case: support fragments in write_config AdrianF
2025-12-29 11:46 ` [OE-core] " Alexander Kanavin
2025-12-28 18:08 ` [PATCH v2 3/3] oe-selftest: ide_sdk: use the ide-sdk fragment AdrianF
2025-12-29 13:13 ` Mathieu Dubois-Briand [this message]
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=DFAQ6QDTDTS4.3M7RPQAK1GZP0@bootlin.com \
--to=mathieu.dubois-briand@bootlin.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 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.