public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: cedric.hombourger@siemens.com,
	Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 0/6] Various improvements to the testsuite
Date: Wed, 17 Dec 2025 15:08:20 +0100	[thread overview]
Message-ID: <20251217140827.166531-1-felix.moessbauer@siemens.com> (raw)

This series aims at simplifying and speeding up the testsuite execution.
This should enable contributors to actually run it and test their patches.

As pointed out in [1], the testsuite currently tests various features over
and over again, while others are not tested at all. We try to improve this
by focusing on "feature" tests, whereby each test case checks a set of
features instead of a whole image. We further identified long running tasks
(like the kernel builds) and move them to a dedicated test.

The execution time reduction varies greatly depending on the hardware,
network and sstate usage. When applying these changes on recently added
patches, the time was often decreased by more than 50% on "fast".

Note, that more refactorings of the testsuite are needed - and planned,
but this series should already address the biggest pain points.

[1] https://groups.google.com/g/isar-users/c/uZBTIHzLp8Q/m/8k0L1vfMDAAJ

Best regards,
Felix Moessbauer
Siemens AG

Felix Moessbauer (6):
  testsuite: move targets with custom kernel to separate test
  testsuite: enable ccache on kernel tests
  testsuite: make prebuilt container a feature test
  testsuite: make compat test standalone test
  testsuite: handle IMAGE_INSTALL solely in cibuilder.py
  testsuite: limit cross_debsrc test to subset of packages

 meta-test/conf/local.conf.sample              | 10 ----
 .../recipes-core/images/isar-image-ci.bb      |  2 -
 testsuite/cibuilder.py                        | 24 ++++++--
 testsuite/citest.py                           | 56 +++++++++++++++++--
 4 files changed, 71 insertions(+), 21 deletions(-)

-- 
2.51.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/20251217140827.166531-1-felix.moessbauer%40siemens.com.

             reply	other threads:[~2025-12-17 14:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-17 14:08 'Felix Moessbauer' via isar-users [this message]
2025-12-17 14:08 ` [PATCH 1/6] testsuite: move targets with custom kernel to separate test 'Felix Moessbauer' via isar-users
2025-12-17 14:08 ` [PATCH 2/6] testsuite: enable ccache on kernel tests 'Felix Moessbauer' via isar-users
2025-12-17 14:08 ` [PATCH 3/6] testsuite: make prebuilt container a feature test 'Felix Moessbauer' via isar-users
2025-12-17 14:08 ` [PATCH 4/6] testsuite: make compat test standalone test 'Felix Moessbauer' via isar-users
2025-12-17 14:08 ` [PATCH 5/6] testsuite: handle IMAGE_INSTALL solely in cibuilder.py 'Felix Moessbauer' via isar-users
2025-12-17 14:08 ` [PATCH 6/6] testsuite: limit cross_debsrc test to subset of packages '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=20251217140827.166531-1-felix.moessbauer@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=cedric.hombourger@siemens.com \
    --cc=felix.moessbauer@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