From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <mikko.rapeli@linaro.org>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2 1/6] oeqa runtime: set self.runner and handle None
Date: Wed, 02 Jul 2025 08:30:52 +0200 [thread overview]
Message-ID: <DB1CWHVP7UW6.Z2K1JXYVC2N8@bootlin.com> (raw)
In-Reply-To: <20250701073359.979368-1-mikko.rapeli@linaro.org>
On Tue Jul 1, 2025 at 9:33 AM CEST, Mikko Rapeli via lists.openembedded.org wrote:
> Set default self.runner to None. qemu target sets
> the runner to qemu. Then handle self.runner None in
> run_network_serialdebug(). This way ssh runner
> and failing ping or ssh tests handle the error cases.
>
> Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> ---
> meta/lib/oeqa/core/target/__init__.py | 1 +
> meta/lib/oeqa/runtime/case.py | 2 ++
> 2 files changed, 3 insertions(+)
>
> v2: setting self.runner for all target types instead of target conditional
> paths in tests
>
> v1: https://lists.openembedded.org/g/openembedded-core/message/219377
> and https://lists.openembedded.org/g/openembedded-core/message/219378
>
> diff --git a/meta/lib/oeqa/core/target/__init__.py b/meta/lib/oeqa/core/target/__init__.py
> index 1382aa9b5239..177f648fe358 100644
> --- a/meta/lib/oeqa/core/target/__init__.py
> +++ b/meta/lib/oeqa/core/target/__init__.py
> @@ -10,6 +10,7 @@ class OETarget(object):
>
> def __init__(self, logger, *args, **kwargs):
> self.logger = logger
> + self.runner = None
>
> @abstractmethod
> def start(self):
> diff --git a/meta/lib/oeqa/runtime/case.py b/meta/lib/oeqa/runtime/case.py
> index 9515ca2f3d62..2a47771a3d47 100644
> --- a/meta/lib/oeqa/runtime/case.py
> +++ b/meta/lib/oeqa/runtime/case.py
> @@ -23,6 +23,8 @@ class OERuntimeTestCase(OETestCase):
> uninstall_package(self)
>
> def run_network_serialdebug(runner):
> + if not runner:
> + return
> status, output = runner.run_serial("ip addr")
> print("ip addr on target: %s %s" % (output, status))
> status, output = runner.run_serial("ping -c 1 %s" % self.target.server_ip)
Hi Mikko,
I think this series caused some issues on the Autobuilder:
AssertionError: 100 != 0 : apt-get install --yes run-postinsts-dev
https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/2031
https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/1879
https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/1816
Can you have a look?
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-07-02 6:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 7:33 [PATCH v2 1/6] oeqa runtime: set self.runner and handle None Mikko Rapeli
2025-07-01 7:33 ` [PATCH v2 2/6] oeqa runtime apt.py: check errors and fix quoting Mikko Rapeli
2025-07-02 9:42 ` [OE-core] " Richard Purdie
2025-07-02 9:50 ` Mikko Rapeli
2025-07-01 7:33 ` [PATCH v2 3/6] oeqa context.py: use TEST_SUITES if set Mikko Rapeli
2025-07-01 7:33 ` [PATCH v2 4/6] testexport.bbclass oe-test: capture all tests and data from all layers Mikko Rapeli
2025-07-01 7:33 ` [PATCH v2 5/6] testexport.bbclass: use image suffix in testexport tar ball name Mikko Rapeli
2025-07-02 6:30 ` Antonin Godard [this message]
2025-07-02 7:24 ` [OE-core] [PATCH v2 1/6] oeqa runtime: set self.runner and handle None Mikko Rapeli
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=DB1CWHVP7UW6.Z2K1JXYVC2N8@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=mikko.rapeli@linaro.org \
--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