From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com,
Felix Moessbauer <felix.moessbauer@siemens.com>,
Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH 2/3] testsuite: use more recent distros in SignatureTest
Date: Fri, 19 Dec 2025 13:25:33 +0200 [thread overview]
Message-ID: <5c49b11a-1d63-42cc-8fb3-3555e923912f@ilbers.de> (raw)
In-Reply-To: <20251218102343.1074824-2-felix.moessbauer@siemens.com>
Hello Felix,
18/12/2025 12:23, 'Felix Moessbauer' via isar-users wrote:
> In general, that should not make a difference. However, we better test
> things that users actually use than old-old-stable distros. As this test
> is just a parser test, it is fast. Hence add the fast tag.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
> testsuite/citest.py | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/testsuite/citest.py b/testsuite/citest.py
> index 95ce891c..cc2bdf41 100755
> --- a/testsuite/citest.py
> +++ b/testsuite/citest.py
> @@ -700,16 +700,16 @@ class SignatureTest(CIBaseTest):
> SstateTest also checks for these, but this test is faster and will check
> more cases.
>
> - :avocado: tags=signatures,sstate
> + :avocado: tags=signatures,sstate,fast
Adding this test case to fast makes it to cleanup isar-image-ci images which
are used later on startvm tests. You can try to run fast CI to reproduce
this.
To prevent issues like that in future, we should perform startvm tests
in the
same places were artifacts got generated, like I've tried to do in:
[18/23] CI: Execute startvm testcases after building
> """
>
> def test_signature_lint(self):
> verbose = bool(int(self.params.get('verbose', default=0)))
> targets = [
> - 'mc:qemuamd64-bullseye:isar-image-ci',
> - 'mc:qemuarm-bullseye:isar-image-base',
> - 'mc:qemuarm-bullseye:isar-image-base:do_populate_sdk',
> - 'mc:qemuamd64-focal:isar-image-base',
> + 'mc:qemuamd64-trixie:isar-image-ci',
> + 'mc:qemuarm-trixie:isar-image-base',
> + 'mc:qemuarm-trixie:isar-image-base:do_populate_sdk',
> + 'mc:qemuamd64-noble:isar-image-base',
> ]
>
> self.init()
--
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/5c49b11a-1d63-42cc-8fb3-3555e923912f%40ilbers.de.
next prev parent reply other threads:[~2025-12-19 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 10:23 [PATCH 1/3] testsuite: fix SignatureTest by avoiding absolute path in bblayers 'Felix Moessbauer' via isar-users
2025-12-18 10:23 ` [PATCH 2/3] testsuite: use more recent distros in SignatureTest 'Felix Moessbauer' via isar-users
2025-12-19 11:25 ` Anton Mikanovich [this message]
2025-12-18 10:23 ` [PATCH 3/3] testsuite: make SignatureTest idempotent 'Felix Moessbauer' via isar-users
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=5c49b11a-1d63-42cc-8fb3-3555e923912f@ilbers.de \
--to=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=ibr@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