public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
	Cedric Hombourger <cedric.hombourger@siemens.com>
Subject: [PATCH 0/9] Improve testsuite executability, basic GitHub CI
Date: Mon, 23 Mar 2026 09:30:30 +0100	[thread overview]
Message-ID: <cover.1774254639.git.jan.kiszka@siemens.com> (raw)

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

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

Jan Kiszka (9):
  Update kas-container to 5.2
  testsuite: Provide a new kas-based test container and wrapper script
  testsuite: Install avocado-framework-plugin-varianter-yaml-to-mux in
    test-container
  testsuite: Add squid to test-container
  ci: Add github workflow for building and deploying test-container
  ci: Switch gitlab-ci to new test-container
  CONTRIBUTING: Switch to new run-tests.sh
  testsuite: Drop KFAIL from trixie tests
  ci: Add github test job to github workflow

 .github/workflows/main.yml                    | 101 ++++++++++++++++++
 .gitlab-ci.yml                                |  22 ++--
 CONTRIBUTING.md                               |  72 +++----------
 kas/kas-container                             |   6 +-
 scripts/ci_setup.sh                           |  32 ------
 scripts/run-tests.sh                          |  18 ++++
 testsuite/citest.py                           |  15 +--
 testsuite/dockerdata/Dockerfile               |  19 +++-
 testsuite/dockerdata/README.md                |  20 ----
 testsuite/dockerdata/build.sh                 |  14 +++
 .../dockerdata/test-container-entrypoint      |  99 +++++++++++++++++
 testsuite/dockerdata/version                  |   1 +
 12 files changed, 280 insertions(+), 139 deletions(-)
 create mode 100644 .github/workflows/main.yml
 delete mode 100755 scripts/ci_setup.sh
 create mode 100755 scripts/run-tests.sh
 delete mode 100644 testsuite/dockerdata/README.md
 create mode 100755 testsuite/dockerdata/build.sh
 create mode 100755 testsuite/dockerdata/test-container-entrypoint
 create mode 100644 testsuite/dockerdata/version

-- 
2.47.3

-- 
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/cover.1774254639.git.jan.kiszka%40siemens.com.

             reply	other threads:[~2026-03-23  8:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23  8:30 'Jan Kiszka' via isar-users [this message]
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

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=cover.1774254639.git.jan.kiszka@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