From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: openembedded-core@lists.openembedded.org
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [OE-core] [PATCH v2] migration-guides: update 4.2 migration and release notes
Date: Thu, 6 Apr 2023 22:53:51 +0200 [thread overview]
Message-ID: <1a1b7d4b-8273-2c7c-d55a-ed9e1bef1e6b@bootlin.com> (raw)
In-Reply-To: <927715c9e53832471789990ddccaba4cfc77c3ca.camel@linuxfoundation.org>
On 06.04.23 at 12:12, Richard Purdie wrote:
> The ptest images have changed structure in this release. The underlying
> core-image-ptest recipe now uses BBCLASSEXTEND to create a variant for
> each ptest enabled recipe in OE-Core.
>
> For example, this means that "core-image-ptest-bzip2", "core-image-
> ptest-lttng-tools" and many more image targets now exist and can be
> built/tested individually.
>
> The core-image-ptest-all and core-image-ptest-fast targets are now
> wrappers that target groups of individual images and means that the
> tests can be executed in parallel during our automated testing. This
> also means the dependencies are more accurately tested.
Thanks Richard. This will be included in the next update I send.
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-04-06 20:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17531B0D0DFA1CB6.3977@lists.openembedded.org>
2023-04-05 18:40 ` [OE-core] [PATCH] migration-guides: update 4.2 migration and release notes Michael Opdenacker
2023-04-05 19:04 ` Frédéric Martinsons
2023-04-06 8:23 ` [docs] " Michael Opdenacker
2023-04-06 8:52 ` Frédéric Martinsons
2023-04-06 9:12 ` [PATCH v2] " michael.opdenacker
2023-04-06 10:12 ` [OE-core] " Richard Purdie
2023-04-06 20:53 ` Michael Opdenacker [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=1a1b7d4b-8273-2c7c-d55a-ed9e1bef1e6b@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.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