From: Uladzimir Bely <ubely@ilbers.de>
To: Anton Mikanovich <amikan@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 0/8] Testsuite coverage update
Date: Tue, 15 Apr 2025 20:58:05 +0300 [thread overview]
Message-ID: <98c9916f5366b401cbd8725275793bf06b4d595f.camel@ilbers.de> (raw)
In-Reply-To: <20250410105025.47019-1-amikan@ilbers.de>
On Thu, 2025-04-10 at 13:50 +0300, Anton Mikanovich wrote:
> To keep testsuite up to date, this patchset has all the CI test suite
> related changes which includes migration of dev and repro CI tests to
> bookworm. Also it contains CI coverage related changes for Ubuntu
> Noble,
> Jammy and x86 targets.
>
> Maria Selvam (8):
> Migrate bullseye dev test to bookworm
> Migrate repro test from bullseye to bookworm
> Migrate riscv64 targets to Trixie
> Cover Ubuntu Noble distro with CI
> Cover Ubuntu Jammy with CI
> Cover x86 PC target with CI
> Create QEMU targets for Sid
> CI: Resolve sourceTest failure
>
> meta-isar/conf/mc.conf | 12 ++--
> meta-isar/conf/multiconfig/qemuamd64-sid.conf | 7 +++
> meta-isar/conf/multiconfig/qemuarm64-sid.conf | 7 +++
> ...scv64-sid.conf => qemuriscv64-trixie.conf} | 4 +-
> .../conf/multiconfig/sifive-fu540-sid.conf | 7 ---
> .../conf/multiconfig/sifive-fu540-trixie.conf | 7 +++
> .../multiconfig/starfive-visionfive2-sid.conf | 7 ---
> .../starfive-visionfive2-trixie.conf | 7 +++
> testsuite/cibase.py | 14 ++++-
> testsuite/citest.py | 55 ++++++++++-------
> --
> 10 files changed, 81 insertions(+), 46 deletions(-)
> create mode 100644 meta-isar/conf/multiconfig/qemuamd64-sid.conf
> create mode 100644 meta-isar/conf/multiconfig/qemuarm64-sid.conf
> rename meta-isar/conf/multiconfig/{qemuriscv64-sid.conf =>
> qemuriscv64-trixie.conf} (67%)
> delete mode 100644 meta-isar/conf/multiconfig/sifive-fu540-sid.conf
> create mode 100644 meta-isar/conf/multiconfig/sifive-fu540-
> trixie.conf
> delete mode 100644 meta-isar/conf/multiconfig/starfive-visionfive2-
> sid.conf
> create mode 100644 meta-isar/conf/multiconfig/starfive-visionfive2-
> trixie.conf
>
> --
> 2.34.1
Applied to next.
--
Best regards,
Uladzimir.
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/98c9916f5366b401cbd8725275793bf06b4d595f.camel%40ilbers.de.
prev parent reply other threads:[~2025-04-15 17:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 10:50 Anton Mikanovich
2025-04-10 10:50 ` [PATCH 1/8] Migrate bullseye dev test to bookworm Anton Mikanovich
2025-04-10 10:50 ` [PATCH 2/8] Migrate repro test from bullseye " Anton Mikanovich
2025-04-10 10:50 ` [PATCH 3/8] Migrate riscv64 targets to Trixie Anton Mikanovich
2025-04-10 10:50 ` [PATCH 4/8] Cover Ubuntu Noble distro with CI Anton Mikanovich
2025-04-10 10:50 ` [PATCH 5/8] Cover Ubuntu Jammy " Anton Mikanovich
2025-04-10 10:50 ` [PATCH 6/8] Cover x86 PC target " Anton Mikanovich
2025-04-10 10:50 ` [PATCH 7/8] Create QEMU targets for Sid Anton Mikanovich
2025-04-10 10:50 ` [PATCH 8/8] CI: Resolve sourceTest failure Anton Mikanovich
2025-04-15 17:58 ` Uladzimir Bely [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=98c9916f5366b401cbd8725275793bf06b4d595f.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=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