All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Willian Rampazzo <willianr@redhat.com>,
	qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
	Wainer dos Santos Moschetta <wainersm@redhat.com>,
	Cleber Rosa <crosa@redhat.com>
Subject: Re: [PATCH v3] tests/acceptance: Add a test with the Fedora 31 kernel and initrd
Date: Mon, 21 Dec 2020 14:44:50 +0100	[thread overview]
Message-ID: <20201221144450.3e5fce49.cohuck@redhat.com> (raw)
In-Reply-To: <20201221133254.4178703-1-thuth@redhat.com>

On Mon, 21 Dec 2020 14:32:54 +0100
Thomas Huth <thuth@redhat.com> wrote:

> This initrd contains a virtio-net and a virtio-gpu kernel module,
> so we can check that we can set a MAC address for the network device
> and whether we can hot-plug and -unplug a virtio-crypto device.
> But the most interesting part is maybe that we can also successfully
> write some stuff into the emulated framebuffer of the virtio-gpu
> device and make sure that we can read back that data from a screenshot.
> 
> Reviewed-by: Wainer dos Santos Moschetta <wainersm@redhat.com> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  v3:
>  - Remove unused "import re"
>  - Use lscss to test for devnos
>  - Improve tmpfile handling (thanks Wainer!)
> 
>  tests/acceptance/machine_s390_ccw_virtio.py | 110 ++++++++++++++++++++
>  1 file changed, 110 insertions(+)

(...)

> +        # Some tests to see whether the CLI options have been considered:
> +        self.log.info("Test whether QEMU CLI options have been considered")
> +        exec_command_and_wait_for_pattern(self, 'lspci',
> +                             '0007:00:00.0 Class 0200: Device 1af4:1000')
> +        exec_command_and_wait_for_pattern(self,
> +                             'cat /sys/class/net/enP7p0s0/address',
> +                             '02:ca:fe:fa:ce:12')
> +        exec_command_and_wait_for_pattern(self, 'lscss', '0.1.9876')
> +        self.wait_for_console_pattern('0.2.5432')

This looks a bit odd... maybe do 'lscss -d 0.1.9876' and 'lscss -d
0.2.5432' and wait for the respective devnos to be printed?

(I'm not entirely sure about the wait_for_console_pattern semantics
here... can the 0.2.5432 line have been printed already before we start
waiting, and would that be a problem? Might be better to play it safe.)

(...)



  reply	other threads:[~2020-12-21 13:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-21 13:32 [PATCH v3] tests/acceptance: Add a test with the Fedora 31 kernel and initrd Thomas Huth
2020-12-21 13:44 ` Cornelia Huck [this message]
2020-12-21 13:46   ` Thomas Huth
2020-12-21 13:48     ` Cornelia Huck

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=20201221144450.3e5fce49.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=crosa@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@redhat.com \
    --cc=willianr@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.