From: Zhihang Wei <wzh@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH] testsuite: Split test_nocross_trixie and drop KFAIL for QEMU targets
Date: Tue, 24 Feb 2026 09:42:27 +0100 [thread overview]
Message-ID: <a7c7d186-2219-4a5a-9d73-edfc6cb58563@ilbers.de> (raw)
In-Reply-To: <20260220080456.45398-1-wzh@ilbers.de>
Applied to next.
Zhihang
On 2/20/26 09:04, Zhihang Wei wrote:
> "test_nocross_trixie" was previously wrapped in KFAIL, even though it
> produces QEMU artifacts which are later used by vm_start tests (not
> marked as KFAIL). As a result, failed incomplete builds were not
> reported directly and only only showed up later as failures in the
> vm_start tests, making CI debugging difficult.
>
> Recently, interrupted downloads have become more frequent when
> starfive-visionfive2-trixie pulls a 200+ MB archive from GitHub. These
> interruptions cause checksum mismatches, abort the test early, and
> prevent other QEMU targets from completing their builds. With KFAIL in
> place, this masked the actual root cause while breaking later tests.
>
> As a workaround (until a proper mirror is added for the external
> resource), split the test so that the QEMU targets are built first and
> without KFAIL, and build the hardware board targets in a separate step.
> This ensures that download issues from board-specific targets no longer
> prevent QEMU artifacts from being built, and makes QEMU build failures
> visible directly in CI.
>
> Signed-off-by: Zhihang Wei <wzh@ilbers.de>
> ---
> testsuite/citest.py | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/testsuite/citest.py b/testsuite/citest.py
> index f11cd5af..115cdbaa 100755
> --- a/testsuite/citest.py
> +++ b/testsuite/citest.py
> @@ -954,11 +954,16 @@ class NoCrossTest(CIBaseTest):
> 'mc:qemuarm64-trixie:isar-image-base',
> 'mc:qemuarm-trixie:isar-image-base',
> 'mc:qemuriscv64-trixie:isar-image-base',
> + ]
> +
> + self.init()
> + self.perform_build_test(targets, cross=False)
> +
> + targets = [
> 'mc:sifive-fu540-trixie:isar-image-base',
> 'mc:starfive-visionfive2-trixie:isar-image-base',
> ]
>
> - self.init()
> try:
> self.perform_build_test(targets, cross=False)
> except exceptions.TestFail:
--
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/a7c7d186-2219-4a5a-9d73-edfc6cb58563%40ilbers.de.
prev parent reply other threads:[~2026-02-24 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 8:04 Zhihang Wei
2026-02-24 8:42 ` Zhihang Wei [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=a7c7d186-2219-4a5a-9d73-edfc6cb58563@ilbers.de \
--to=wzh@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