From: Richard Purdie <richard.purdie@linuxfoundation.org>
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: Fri, 18 Nov 2022 16:11:08 +0000 [thread overview]
Message-ID: <a7d53c70e704a72d2a05a0fb4a96a93dc4b9c4b8.camel@linuxfoundation.org> (raw)
In-Reply-To: <Y3erTB2Qulh8Wfn+@nuoska>
On Fri, 2022-11-18 at 17:57 +0200, Mikko Rapeli wrote:
> On Fri, Nov 18, 2022 at 03:04:29PM +0000, Richard Purdie wrote:
>
> > My concern is having multiple different file formats and data streams.
> > It means we no longer have one definitive data mechanism but two, then
> > the argument for people also shipping yaml and other files with recipes
> > also becomes difficult. We'd also have people wanting to query from one
> > to the other eventually.
> >
> > The real issue here seems to be that our data format (.bb) is
> > struggling with some forms of data. I've therefore a preference for
> > fixing that rather than encouraging working around it.
>
> For oeqa runtime tests I propose this json file. If tests have any
> customization need they should use either image recipe variables or this
> file format if recipe variables can't support the format. For other
> alternatives I'd need pointers where to implement and what. ptests are
> normal packages so they don't complicate this.
The key question this comes down to is can anyone suggest a syntax for
including python data structures in our metadata (and/or json data)?
Cheers,
Richard
prev parent reply other threads:[~2022-11-18 16:11 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 ` [OE-core] [PATCH 0/2] image specific configuration with oeqa runtime tests Alexandre Belloni
2022-11-17 14:28 ` 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 [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=a7d53c70e704a72d2a05a0fb4a96a93dc4b9c4b8.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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