From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Mikko Rapeli <mikko.rapeli@linaro.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 0/2] image specific configuration with oeqa runtime tests
Date: Thu, 17 Nov 2022 15:22:20 +0100 [thread overview]
Message-ID: <Y3ZDnOCC+mzyjdEl@mail.local> (raw)
In-Reply-To: <20221117071223.107064-1-mikko.rapeli@linaro.org>
Hello,
With this two patches, I have multiple new warnings on the autobuilders
for qemuarm and qemuarm-alt
https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/6185/steps/13/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/110/builds/5064/steps/12/logs/stdio
On 17/11/2022 09:12:21+0200, Mikko Rapeli wrote:
> Many runtime tests would need customization for different
> machines and images. Currently some tests like parselogs.py are hard
> coding machine specific exceptions into the test itself. I think these
> machine specific exceptions fit better as image specific ones, since a
> single machine config can generate multiple images which behave
> differently. Thus create a "testimage_data.json" file format which image
> recipes can deploy. This is then used by tests like parselogs.py to find
> the image specific exception list.
>
> Same approach would fit other runtime tests too. For example systemd
> tests could include a test case which checks that an image specific list of
> services are running.
>
> I don't know how this data storage would be used with SDK or selftests,
> but maybe it could work there too with some small tweaks.
>
> Mikko Rapeli (2):
> oeqa: add utils/data.py with get_data() function
> oeqa parselogs.py: use get_data() to fetch image specific error list
>
> meta/lib/oeqa/runtime/cases/parselogs.py | 17 +++++++---
> meta/lib/oeqa/utils/data.py | 41 ++++++++++++++++++++++++
> 2 files changed, 54 insertions(+), 4 deletions(-)
> create mode 100644 meta/lib/oeqa/utils/data.py
>
> --
> 2.34.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#173404): https://lists.openembedded.org/g/openembedded-core/message/173404
> Mute This Topic: https://lists.openembedded.org/mt/95085492/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-11-17 14:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 7:12 [PATCH 0/2] image specific configuration with oeqa runtime tests Mikko Rapeli
2022-11-17 7:12 ` [PATCH 1/2] oeqa: add utils/data.py with get_data() function Mikko Rapeli
2022-11-17 7:12 ` [PATCH 2/2] oeqa parselogs.py: use get_data() to fetch image specific error list Mikko Rapeli
2022-11-17 14:22 ` Alexandre Belloni [this message]
2022-11-17 14:28 ` [OE-core] [PATCH 0/2] image specific configuration with oeqa runtime tests Mikko Rapeli
2022-11-17 15:17 ` Richard Purdie
2022-11-17 15:39 ` Mikko Rapeli
2022-11-17 16:57 ` Richard Purdie
2022-11-18 14:32 ` Mikko Rapeli
2022-11-18 15:04 ` Richard Purdie
2022-11-18 15:57 ` Mikko Rapeli
2022-11-18 16:04 ` Richard Purdie
2022-11-18 16:09 ` Mikko Rapeli
2022-11-18 16:11 ` Richard Purdie
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=Y3ZDnOCC+mzyjdEl@mail.local \
--to=alexandre.belloni@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