public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com, Uladzimir Bely <ubely@ilbers.de>
Subject: Re: [PATCH v2 3/4] CI: install qemu-system when qemu testing is requested
Date: Tue, 24 Jan 2023 22:53:50 +0200	[thread overview]
Message-ID: <c8bb48ba-c096-f483-386b-cb18da350e4b@ilbers.de> (raw)
In-Reply-To: <20230123095159.7d7b3c0a@md1za8fc.ad001.siemens.net>

23/01/2023 10:51, Henning Schild wrote:
> Right. I will switch this over to testing for "qemu-system-x86_64" but
> still install "all qemus" with the meta package "qemu-system".
>
> Or maybe "test -f /usr/share/doc/qemu-system/copyright" to check for
> that meta-package.
>
> Strictly speaking we do not need all of the qemus, but maintaining the
> list of our arches seems too much effort.
>
> Henning

Hello, I've just send '[PATCH v2 00/15] Add developers test' with this 
commit
fixed inside. This is how I see test cases splitting between developers and
maintainers.


  reply	other threads:[~2023-01-24 20:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 23:59 [PATCH v2 0/4] CI rework of gitlab fast job Henning Schild
2023-01-12 23:59 ` [PATCH v2 1/4] CI: move to avocado to 99.0 Henning Schild
2023-01-12 23:59 ` [PATCH v2 2/4] CI: fix shell coding style Henning Schild
2023-01-12 23:59 ` [PATCH v2 3/4] CI: install qemu-system when qemu testing is requested Henning Schild
2023-01-14 20:15   ` Uladzimir Bely
2023-01-23  8:51     ` Henning Schild
2023-01-24 20:53       ` Anton Mikanovich [this message]
2023-01-12 23:59 ` [PATCH v2 4/4] testsuite: remove tests from "fast" set Henning Schild

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=c8bb48ba-c096-f483-386b-cb18da350e4b@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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