From: Tim Orling <tim.orling@konsulko.com>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH 0/3] fix PTESTS_PPROBLEMS_*
Date: Wed, 21 Feb 2024 20:26:28 -0800 [thread overview]
Message-ID: <cover.1708573650.git.tim.orling@konsulko.com> (raw)
When PTESTS_FAST_* and PTESTS_SLOW_* were added, we should also have added
PTEST_PROBLEMS_* for meta-*-image-ptest.bb and meta-*-image-ptest-all.bb
so that the BBCLASSEXTEND magic works, even for the "problem children".
This series makes meta-oe, meta-perl and meta-python behave the same as
oe-core (even the PTESTS_PROBLEMS are available there in core-image-ptest-*).
The following changes since commit 7f173ed0fb3d91200e22762f3f6c8b62955fc39e:
netdata: version bump 1.43.2 -> 1.44.3 (2024-02-21 14:36:06 -0800)
are available in the Git repository at:
https://git.openembedded.org/meta-openembedded-contrib timo/fix-PTESTS_PROBLEMS
https://git.openembedded.org/meta-openembedded-contrib/log/?h=timo/fix-PTESTS_PROBLEMS
Tim Orling (3):
meta-oe-image-ptest: add PTESTS_PROBLEMS_META_OE
meta-perl-image-ptest: add PTESTS_PROBLEMS_META_PERL
meta-python-image-ptest: add PTESTS_PROBLEMS_META_PYTHON
meta-oe/recipes-core/images/meta-oe-image-ptest-all.bb | 2 +-
meta-oe/recipes-core/images/meta-oe-image-ptest.bb | 2 +-
meta-perl/recipes-core/images/meta-perl-image-ptest-all.bb | 2 +-
meta-perl/recipes-core/images/meta-perl-image-ptest.bb | 2 +-
meta-python/recipes-core/images/meta-python-image-ptest-all.bb | 2 +-
meta-python/recipes-core/images/meta-python-image-ptest.bb | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
--
2.34.1
next reply other threads:[~2024-02-22 4:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 4:26 Tim Orling [this message]
2024-02-22 4:26 ` [meta-oe][PATCH 1/3] meta-oe-image-ptest: add PTESTS_PROBLEMS_META_OE Tim Orling
2024-02-22 4:26 ` [meta-perl][PATCH 2/3] meta-perl-image-ptest: add PTESTS_PROBLEMS_META_PERL Tim Orling
2024-02-22 4:26 ` [meta-python][PATCH 3/3] meta-python-image-ptest: add PTESTS_PROBLEMS_META_PYTHON Tim Orling
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=cover.1708573650.git.tim.orling@konsulko.com \
--to=tim.orling@konsulko.com \
--cc=openembedded-devel@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.