From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 0/2] Isolate test classes, make them reproducible
Date: Tue, 17 Nov 2026 13:02:58 +0100 [thread overview]
Message-ID: <20261117120300.374231-1-felix.moessbauer@siemens.com> (raw)
This series goes on top of "A couple of fixes for snapshot handling on
Ubuntu". It is another attempt to make the testsuite more isolated and
reproducible by allowing it to run against a specific snapshot date.
This hopefully helps to reproduce issues reported from upstream (the
official isar CI) locally more easily.
Best regards,
Felix Moessbauer
Felix Moessbauer (2):
testsuite: add support to run testsuite against specific SDE
testsuite: cleanup artifacts if not requested otherwise
testsuite/README.md | 4 ++++
testsuite/cibase.py | 18 ++++++++++++++++++
testsuite/cibuilder.py | 7 +++++++
testsuite/citest.py | 33 ++++++++++++++++++++++++++++-----
4 files changed, 57 insertions(+), 5 deletions(-)
--
2.55.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/20261117120300.374231-1-felix.moessbauer%40siemens.com.
next reply other threads:[~2026-11-17 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 12:02 'Felix Moessbauer' via isar-users [this message]
2026-11-17 12:02 ` [PATCH 1/2] testsuite: add support to run testsuite against specific SDE 'Felix Moessbauer' via isar-users
2026-11-17 12:03 ` [PATCH 2/2] testsuite: cleanup artifacts if not requested otherwise '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=20261117120300.374231-1-felix.moessbauer@siemens.com \
--to=isar-users@googlegroups.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