From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH v2 1/3] ci: run vm_start tests right after targets that built it
Date: Mon, 20 Jul 2026 09:37:01 +0200 [thread overview]
Message-ID: <20260720073703.3782697-2-felix.moessbauer@siemens.com> (raw)
In-Reply-To: <20260720073703.3782697-1-felix.moessbauer@siemens.com>
As a preparation to reduce the parsing effort, we need to order the
vm_start tests right after the target that built the corresponding
image. This is needed to ensure we still have the cache data for the
to-be-booted configuration.
Technically, this was already incorrect before, as the vm_start tests
are related to a specific target that has to be built before execution.
If other targets are built in-between, the vm that is executed for the
test is likely not what was intended to be tested.
Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
testsuite/citest.py | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/testsuite/citest.py b/testsuite/citest.py
index 1facc8c2..fb44036c 100644
--- a/testsuite/citest.py
+++ b/testsuite/citest.py
@@ -75,6 +75,10 @@ class DevTest(CIBaseTest):
self.init()
self.perform_build_test(targets, image_install='example-raw')
+ def test_dev_run_arm_bookworm(self):
+ self.init()
+ self.vm_start('arm', 'bookworm', skip_modulecheck=True)
+
def test_dev_apps(self):
targets = [
'mc:qemuamd64-bookworm:isar-image-ci',
@@ -84,6 +88,10 @@ class DevTest(CIBaseTest):
self.init()
self.perform_build_test(targets)
+ def test_dev_run_arm64_bookworm(self):
+ self.init()
+ self.vm_start('arm64', 'bookworm')
+
def test_dev_rebuild(self):
self.init()
layerdir_core = CIUtils.getVars('LAYERDIR_core')
@@ -103,14 +111,6 @@ class DevTest(CIBaseTest):
self.init()
self.vm_start('amd64', 'bookworm', image='isar-image-ci')
- def test_dev_run_arm64_bookworm(self):
- self.init()
- self.vm_start('arm64', 'bookworm')
-
- def test_dev_run_arm_bookworm(self):
- self.init()
- self.vm_start('arm', 'bookworm', skip_modulecheck=True)
-
class CompatTest(CIBaseTest):
"""
--
2.53.0
--
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/20260720073703.3782697-2-felix.moessbauer%40siemens.com.
next prev parent reply other threads:[~2026-07-20 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 7:37 [PATCH v2 0/3] speedup testsuite execution execution 'Felix Moessbauer' via isar-users
2026-07-20 7:37 ` 'Felix Moessbauer' via isar-users [this message]
2026-07-24 9:50 ` [PATCH v2 1/3] ci: run vm_start tests right after targets that built it Zhihang Wei
2026-07-20 7:37 ` [PATCH v2 2/3] testsuite: speedup execution by limiting mc parsing to selected targets 'Felix Moessbauer' via isar-users
2026-07-24 14:56 ` Zhihang Wei
2026-07-24 15:27 ` 'MOESSBAUER, Felix' via isar-users
2026-07-20 7:37 ` [PATCH v2 3/3] testsuite: remove duplicated cross test '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=20260720073703.3782697-2-felix.moessbauer@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.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