public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "Kiszka, Jan" <jan.kiszka@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Cc: "Hombourger, Cedric" <cedric.hombourger@siemens.com>
Subject: Re: [PATCH 0/9] Improve testsuite executability, basic GitHub CI
Date: Thu, 7 May 2026 08:27:16 +0000	[thread overview]
Message-ID: <490c9bd19a2f74014e178c68e056ddf480bfb173.camel@siemens.com> (raw)
In-Reply-To: <cover.1774254639.git.jan.kiszka@siemens.com>

On Mon, 2026-03-23 at 09:30 +0100, Jan Kiszka wrote:
> There were several proposals for wrapping the testsuite execution into
> some container. There is even docker-isar already, though this one was
> not yet used for a wrapper.
> 
> This new approach enhances the existing container to "test-container", a
> kas-based environment that contains all required testsuite dependencies
> and can run them both as CI base container as well as via a script that
> is kas-container-like (actually using it). So, all the setup steps are
> history now, just call
> 
>     scripts/run-tests.sh -t dev
> 
> to execute the minimal testsuite locally. Or just run
> 
>     scripts/run-tests.sh testsuite/citest.py:test_dev_apps

Hi,

this series is super-useful for local testing. It especially helps when
switching between isar patch series and testing multiple things in a
row. It further can be easily extended for testing the rootless mode,
which otherwise is tricky.

Can we please integrate this, it still cleanly applies on top of isar
1.1.

Felix

> 
> to execute a specific test (avocado command line interface).
> 
> Along that, kas is updated consistently to 5.2, using the trixie
> container now. The testsuite loses some obsolete KFAIL tags. And,
> finally, some basic CI step is added as GitHub action.
> 
> The latter can be considered an RFC for now. It's unclear how far we can
> go on public CI by parallelizing some of the test sets. Avocado lacks
> support for test dependencies [1], thus this would require additional
> maintenance and may still run into the limitations of public GitHub
> runners.
> 
> A full run of this series can be found at [2]. This also allows to try
> out the container before it was built officially, just set this prior to
> calling run-tests.sh:
> 
>     CONTAINER_BASENAME=ghcr.io/siemens/isar
> 
> Jan
> 
> [1] https://github.com/avocado-framework/avocado/issues/6131#issuecomment-2694016818
> [2] https://github.com/siemens/isar/actions/runs/23426024062
> 

-- 
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/490c9bd19a2f74014e178c68e056ddf480bfb173.camel%40siemens.com.

  parent reply	other threads:[~2026-05-07  8:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23  8:30 'Jan Kiszka' via isar-users
2026-03-23  8:30 ` [PATCH 1/9] Update kas-container to 5.2 'Jan Kiszka' via isar-users
2026-03-23  8:30 ` [PATCH 2/9] testsuite: Provide a new kas-based test container and wrapper script 'Jan Kiszka' via isar-users
2026-03-23  8:30 ` [PATCH 3/9] testsuite: Install avocado-framework-plugin-varianter-yaml-to-mux in test-container 'Jan Kiszka' via isar-users
2026-03-23  8:30 ` [PATCH 4/9] testsuite: Add squid to test-container 'Jan Kiszka' via isar-users
2026-03-23  8:30 ` [PATCH 5/9] ci: Add github workflow for building and deploying test-container 'Jan Kiszka' via isar-users
2026-03-23  8:30 ` [PATCH 6/9] ci: Switch gitlab-ci to new test-container 'Jan Kiszka' via isar-users
2026-03-23  8:30 ` [PATCH 7/9] CONTRIBUTING: Switch to new run-tests.sh 'Jan Kiszka' via isar-users
2026-03-26 17:01   ` Zhihang Wei
2026-03-26 18:41     ` 'Jan Kiszka' via isar-users
2026-03-23  8:30 ` [PATCH 8/9] testsuite: Drop KFAIL from trixie tests 'Jan Kiszka' via isar-users
2026-03-23  8:30 ` [PATCH 9/9] ci: Add github test job to github workflow 'Jan Kiszka' via isar-users
2026-05-07  8:27 ` 'MOESSBAUER, Felix' via isar-users [this message]
2026-05-07  8:54   ` [PATCH 0/9] Improve testsuite executability, basic GitHub CI Zhihang Wei

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=490c9bd19a2f74014e178c68e056ddf480bfb173.camel@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=cedric.hombourger@siemens.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