From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Eduardo Habkost <ehabkost@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Wainer dos Santos Moschetta <wainersm@redhat.com>,
qemu-arm@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
Cleber Rosa <crosa@redhat.com>
Subject: Re: [PATCH 1/2] tests/acceptance: Extract boot_integratorcp() from test_integratorcp()
Date: Sat, 1 Feb 2020 08:06:16 +0100 [thread overview]
Message-ID: <c13e2bf5-2373-f33e-1aea-824c46b9f3cf@redhat.com> (raw)
In-Reply-To: <20200131211102.29612-2-f4bug@amsat.org>
On 31/01/2020 22.11, Philippe Mathieu-Daudé wrote:
> As we want to re-use this code, extract it as a new function.
> Since we are using the PL011 serial console, add a Avocado tag
> to ease filtering of tests.
>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> tests/acceptance/machine_arm_integratorcp.py | 16 ++++++++++------
> 1 file changed, 10 insertions(+), 6 deletions(-)
>
> diff --git a/tests/acceptance/machine_arm_integratorcp.py b/tests/acceptance/machine_arm_integratorcp.py
> index 4f9ab40f2f..748819916d 100644
> --- a/tests/acceptance/machine_arm_integratorcp.py
> +++ b/tests/acceptance/machine_arm_integratorcp.py
> @@ -19,12 +19,7 @@ class IntegratorMachine(Test):
>
> timeout = 90
>
> - @skipUnless(os.getenv('AVOCADO_ALLOW_UNTRUSTED_CODE'), 'untrusted code')
> - def test_integratorcp(self):
> - """
> - :avocado: tags=arch:arm
> - :avocado: tags=machine:integratorcp
> - """
> + def boot_integratorcp(self):
> kernel_url = ('https://github.com/zayac/qemu-arm/raw/master/'
> 'arm-test/kernel/zImage.integrator')
> kernel_hash = '0d7adba893c503267c946a3cbdc63b4b54f25468'
> @@ -40,4 +35,13 @@ class IntegratorMachine(Test):
> '-initrd', initrd_path,
> '-append', 'printk.time=0 console=ttyAMA0')
I wonder whether you might want to move the "console=ttyAMA0" to the
test_integratorcp(), too, to get the text in the framebuffer in the
second test instead?
> self.vm.launch()
> +
> + @skipUnless(os.getenv('AVOCADO_ALLOW_UNTRUSTED_CODE'), 'untrusted code')
> + def test_integratorcp(self):
> + """
> + :avocado: tags=arch:arm
> + :avocado: tags=machine:integratorcp
> + :avocado: tags=device:pl011
> + """
> + self.boot_integratorcp()
> wait_for_console_pattern(self, 'Log in as root')
>
Anyway, patch looks fine,
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2020-02-01 7:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 21:11 [PATCH 0/2] tests/acceptance/integratorcp: Verify Tux is displayed on framebuffer Philippe Mathieu-Daudé
2020-01-31 21:11 ` [PATCH 1/2] tests/acceptance: Extract boot_integratorcp() from test_integratorcp() Philippe Mathieu-Daudé
2020-02-01 7:06 ` Thomas Huth [this message]
2020-02-11 10:08 ` Philippe Mathieu-Daudé
2020-02-03 14:00 ` Wainer dos Santos Moschetta
2020-01-31 21:11 ` [PATCH 2/2] tests/acceptance/integratorcp: Verify Tux is displayed on framebuffer Philippe Mathieu-Daudé
2020-02-01 7:24 ` Thomas Huth
2020-02-03 14:05 ` Wainer dos Santos Moschetta
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=c13e2bf5-2373-f33e-1aea-824c46b9f3cf@redhat.com \
--to=thuth@redhat.com \
--cc=crosa@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).