From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v2 0/9] Update testsuite targets
Date: Thu, 30 Dec 2021 09:13:04 +0300 [thread overview]
Message-ID: <20211230061313.236578-1-amikan@ilbers.de> (raw)
The most QEMU targets of CI are still Debian Stretch which was already
became oldoldstable. Meantime Debian Bullseye was not fully covered by
CI because it was protected by KFAIL and any errors were ignored. So we
need to move the most common CI targets from stretch to bullseye.
We also need to cover all existing machines by CI, so adding also some
new targets to full CI.
Building repro tests takes too much time during fast testing, so remove
it from fast and left only for full CI.
Also update real hardware targets to at least Debian Bullseye.
This patchset is placed on the top of
[PATCH v3] conf: add new debian version "bookworm"
---
Changes since v1:
- Remove container-amd64 SDK target update patch.
Anton Mikanovich (5):
CI: Remove KFAIL for bullseye
meta-isar: Add bullseye config for nand-ubi-demo
CI: Cover RISC-V targets
CI: Move qemu-stretch targets to bullseye
CI: Remove repro from fast testing
Uladzimir Bely (4):
meta-isar: Add bullseye config for de0-nano-soc
meta-isar: Add bullseye config for bananapi
meta-isar: Add bullseye config for nanopi-neo
meta-isar: Add bullseye and bookworm configs for stm32mp15x
meta-isar/conf/local.conf.sample | 6 ++
.../conf/multiconfig/bananapi-bullseye.conf | 8 ++
.../multiconfig/de0-nano-soc-bullseye.conf | 8 ++
.../multiconfig/nand-ubi-demo-bullseye.conf | 14 ++++
.../conf/multiconfig/nanopi-neo-bullseye.conf | 8 ++
.../conf/multiconfig/stm32mp15x-bookworm.conf | 8 ++
.../conf/multiconfig/stm32mp15x-bullseye.conf | 8 ++
testsuite/build_test/build_test.py | 73 +++++++------------
testsuite/vm_boot_test/vm_boot_test.py | 12 +--
9 files changed, 94 insertions(+), 51 deletions(-)
create mode 100644 meta-isar/conf/multiconfig/bananapi-bullseye.conf
create mode 100644 meta-isar/conf/multiconfig/de0-nano-soc-bullseye.conf
create mode 100644 meta-isar/conf/multiconfig/nand-ubi-demo-bullseye.conf
create mode 100644 meta-isar/conf/multiconfig/nanopi-neo-bullseye.conf
create mode 100644 meta-isar/conf/multiconfig/stm32mp15x-bookworm.conf
create mode 100644 meta-isar/conf/multiconfig/stm32mp15x-bullseye.conf
--
2.25.1
next reply other threads:[~2021-12-30 6:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 6:13 Anton Mikanovich [this message]
2021-12-30 6:13 ` [PATCH v2 1/9] CI: Remove KFAIL for bullseye Anton Mikanovich
2021-12-30 6:13 ` [PATCH v2 2/9] meta-isar: Add bullseye config for de0-nano-soc Anton Mikanovich
2021-12-30 6:13 ` [PATCH v2 3/9] meta-isar: Add bullseye config for bananapi Anton Mikanovich
2021-12-30 6:13 ` [PATCH v2 4/9] meta-isar: Add bullseye config for nanopi-neo Anton Mikanovich
2021-12-30 6:13 ` [PATCH v2 5/9] meta-isar: Add bullseye and bookworm configs for stm32mp15x Anton Mikanovich
2021-12-30 6:13 ` [PATCH v2 6/9] meta-isar: Add bullseye config for nand-ubi-demo Anton Mikanovich
2021-12-30 6:13 ` [PATCH v2 7/9] CI: Cover RISC-V targets Anton Mikanovich
2021-12-30 6:13 ` [PATCH v2 8/9] CI: Move qemu-stretch targets to bullseye Anton Mikanovich
2021-12-30 6:13 ` [PATCH v2 9/9] CI: Remove repro from fast testing Anton Mikanovich
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=20211230061313.236578-1-amikan@ilbers.de \
--to=amikan@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