public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v3 00/10] Move testsuite hacks to separate layer
Date: Tue, 13 Jun 2023 09:27:25 +0300	[thread overview]
Message-ID: <f7d3118146f8cf27bd861d13e48e71f23d2d7975.camel@ilbers.de> (raw)
In-Reply-To: <20230612071256.8688-1-ubely@ilbers.de>

On Mon, 2023-06-12 at 09:12 +0200, Uladzimir Bely wrote:
> There are a lot of hacks in Isar are used by testsuite only. Some of
> them even cause variable setting issues for users. To prevent this
> kind
> of issues introduce separate meta-test layer to be used by testsuite
> only.
> This patchset also removes variables setting from multiconfigs to
> allow
> building without multiconfigs.
> The current patchset version is not fully tested and lack some
> documentation, but it should be a good starting point.
> 

The patchset is going to be merged soon. Since it may require changes
in the downstreams (cleaned up multiconfigs, moved some stuff in new
'meta-test' layer) we want to warn about it so that the downstreams
could test it in advance.

  parent reply	other threads:[~2023-06-13  6:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12  7:12 Uladzimir Bely
2023-06-12  7:12 ` [PATCH v3 01/10] CI: Introduce meta-test layer Uladzimir Bely
2023-06-12  7:12 ` [PATCH v3 02/10] ubuntu: Fix WKS_FILE overriding Uladzimir Bely
2023-06-12  7:12 ` [PATCH v3 03/10] CI: Move qemuamd64-bookworm hacks to CI layer Uladzimir Bely
2023-06-12  7:12 ` [PATCH v3 04/10] CI: Move qemuamd64-bullseye " Uladzimir Bely
2023-06-12  7:12 ` [PATCH v3 05/10] CI: Move qemuamd64-buster " Uladzimir Bely
2023-06-12  7:12 ` [PATCH v3 06/10] CI: Move qemuarm-bookworm " Uladzimir Bely
2023-06-12  7:12 ` [PATCH v3 07/10] CI: Move qemuarm64-bookworm " Uladzimir Bely
2023-06-12  7:12 ` [PATCH v3 08/10] meta-isar: Remove qemuamd64-sb settings from multiconfig Uladzimir Bely
2023-06-15  5:07   ` Jan Kiszka
2023-06-15  8:19     ` Anton Mikanovich
2023-06-15  9:15       ` MOESSBAUER, Felix
2023-06-12  7:12 ` [PATCH v3 09/10] meta-isar: Remove imx6-sabrelite " Uladzimir Bely
2023-06-12  7:12 ` [PATCH v3 10/10] meta-isar: Unify multiconfigs to use weak assignments Uladzimir Bely
2023-06-13  6:27 ` Uladzimir Bely [this message]
2023-06-15  5:13   ` [PATCH v3 00/10] Move testsuite hacks to separate layer Jan Kiszka

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=f7d3118146f8cf27bd861d13e48e71f23d2d7975.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.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