From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v2 00/10] Move testsuite hacks to separate layer
Date: Fri, 2 Jun 2023 08:47:19 +0200 [thread overview]
Message-ID: <20230602064729.10331-1-ubely@ilbers.de> (raw)
There are a lot of hacks in Isar are used by testsuite only. Some of
them even cause variable setting issues for users. To prevent this kind
of issues introduce separate meta-test layer to be used by testsuite
only.
This patchset also removes variables setting from multiconfigs to allow
building without multiconfigs.
The current patchset version is not fully tested and lack some
documentation, but it should be a good starting point.
Changes since v1:
- Rebased on latest `next`
- Added RECIPE-API-CHANGELOG.md entry
The patchset is additionally tested with `meta-iot2050` downstream.
Anton Mikanovich (10):
CI: Introduce meta-test layer
ubuntu: Fix WKS_FILE overriding
CI: Move qemuamd64-bookworm hacks to CI layer
CI: Move qemuamd64-bullseye hacks to CI layer
CI: Move qemuamd64-buster hacks to CI layer
CI: Move qemuarm-bookworm hacks to CI layer
CI: Move qemuarm64-bookworm hacks to CI layer
meta-isar: Remove qemuamd64-sb settings from multiconfig
meta-isar: Remove imx6-sabrelite settings from multiconfig
meta-isar: Unify multiconfigs to use weak assignments
RECIPE-API-CHANGELOG.md | 5 +
meta-isar/conf/distro/ubuntu-common.inc | 2 +
meta-isar/conf/machine/imx6-sabrelite.conf | 6 +
meta-isar/conf/machine/qemuamd64-sb.conf | 9 +
meta-isar/conf/machine/qemuamd64.conf | 12 -
.../conf/multiconfig/bananapi-bullseye.conf | 4 +-
.../conf/multiconfig/bananapi-buster.conf | 4 +-
.../multiconfig/de0-nano-soc-bullseye.conf | 4 +-
.../conf/multiconfig/de0-nano-soc-buster.conf | 4 +-
.../conf/multiconfig/hikey-bookworm.conf | 4 +-
.../conf/multiconfig/hikey-bullseye.conf | 4 +-
.../multiconfig/imx6-sabrelite-bullseye.conf | 6 -
.../multiconfig/imx6-sabrelite-buster.conf | 6 -
.../conf/multiconfig/nanopi-neo-bullseye.conf | 4 +-
.../conf/multiconfig/nanopi-neo-buster.conf | 4 +-
.../conf/multiconfig/qemuamd64-bookworm.conf | 1 -
.../conf/multiconfig/qemuamd64-bullseye.conf | 2 -
.../conf/multiconfig/qemuamd64-buster.conf | 4 -
.../conf/multiconfig/qemuamd64-focal.conf | 2 -
.../conf/multiconfig/qemuamd64-jammy.conf | 2 -
.../multiconfig/qemuamd64-sb-bullseye.conf | 10 +-
.../conf/multiconfig/qemuarm-bookworm.conf | 6 -
.../conf/multiconfig/qemuarm64-bookworm.conf | 3 -
.../multiconfig/sifive-fu540-sid-ports.conf | 4 +-
.../starfive-visionfive2-sid-ports.conf | 4 +-
.../conf/multiconfig/stm32mp15x-bullseye.conf | 4 +-
.../conf/multiconfig/stm32mp15x-buster.conf | 4 +-
.../conf/multiconfig/virtualbox-bullseye.conf | 5 +-
meta-isar/recipes-ci/images/isar-image-ci.bb | 9 -
meta-test/conf/bblayers.conf.sample | 15 +
meta-test/conf/conf-notes.txt | 3 +
meta-test/conf/layer.conf | 20 ++
meta-test/conf/local.conf.sample | 264 ++++++++++++++++++
meta-test/recipes-ci/images/isar-image-ci.bb | 47 ++++
.../isar-ci-ssh-setup/files/postinst | 0
.../isar-ci-ssh-setup_0.1.bb | 0
testsuite/cibuilder.py | 1 +
testsuite/citest.py | 32 ++-
38 files changed, 417 insertions(+), 103 deletions(-)
delete mode 100644 meta-isar/recipes-ci/images/isar-image-ci.bb
create mode 100644 meta-test/conf/bblayers.conf.sample
create mode 100644 meta-test/conf/conf-notes.txt
create mode 100644 meta-test/conf/layer.conf
create mode 100644 meta-test/conf/local.conf.sample
create mode 100644 meta-test/recipes-ci/images/isar-image-ci.bb
rename {meta-isar => meta-test}/recipes-ci/isar-ci-ssh-setup/files/postinst (100%)
rename {meta-isar => meta-test}/recipes-ci/isar-ci-ssh-setup/isar-ci-ssh-setup_0.1.bb (100%)
--
2.20.1
next reply other threads:[~2023-06-02 6:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 6:47 Uladzimir Bely [this message]
2023-06-02 6:47 ` [PATCH v2 01/10] CI: Introduce meta-test layer Uladzimir Bely
2023-06-02 6:47 ` [PATCH v2 02/10] ubuntu: Fix WKS_FILE overriding Uladzimir Bely
2023-06-02 6:47 ` [PATCH v2 03/10] CI: Move qemuamd64-bookworm hacks to CI layer Uladzimir Bely
2023-06-02 6:47 ` [PATCH v2 04/10] CI: Move qemuamd64-bullseye " Uladzimir Bely
2023-06-02 6:47 ` [PATCH v2 05/10] CI: Move qemuamd64-buster " Uladzimir Bely
2023-06-02 6:47 ` [PATCH v2 06/10] CI: Move qemuarm-bookworm " Uladzimir Bely
2023-06-02 6:47 ` [PATCH v2 07/10] CI: Move qemuarm64-bookworm " Uladzimir Bely
2023-06-02 6:47 ` [PATCH v2 08/10] meta-isar: Remove qemuamd64-sb settings from multiconfig Uladzimir Bely
2023-06-02 6:47 ` [PATCH v2 09/10] meta-isar: Remove imx6-sabrelite " Uladzimir Bely
2023-06-02 6:47 ` [PATCH v2 10/10] meta-isar: Unify multiconfigs to use weak assignments Uladzimir Bely
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=20230602064729.10331-1-ubely@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
/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