qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>, qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Niek Linnenbank" <nieklinnenbank@gmail.com>,
	"Joel Stanley" <joel@jms.id.au>
Subject: Re: [PATCH 0/2] Convert the BananaPi and OrangePi Avacodo tests
Date: Tue, 29 Oct 2024 17:50:48 +0100	[thread overview]
Message-ID: <c95b7e5f-0345-4648-bae7-285ecde8dfd8@redhat.com> (raw)
In-Reply-To: <c5ff463d-c5fb-4d00-95fc-f3c3ce9178d5@linaro.org>

On 29/10/2024 17.31, Pierrick Bouvier wrote:
> Hi Thomas,
> 
> On 10/29/24 02:24, Thomas Huth wrote:
>> Some of the URLs in the Avocado tests stopped working since the
>> original assets have been removed from the servers or moved location,
>> see:
>>
>>   https://lore.kernel.org/qemu-devel/CACPK8Xc=jsz5iT_WR7s- 
>> rcu1cRzryiK+-0o=6vUK_D_qMMrP3A@mail.gmail.com/
>>
>> Since we are currently in progress of converting the Avocado tests
>> to the new functional framework, this is a good opportunity to convert
>> these tests and adjust the URLs (and hashsums) along the way to make
>> these tests work again.
>>
>> Thomas Huth (2):
>>    tests/functional: Convert BananaPi tests to the functional framework
>>    tests/functional: Convert the OrangePi tests to the functional
>>      framework
>>
>>   MAINTAINERS                           |   1 +
>>   tests/avocado/boot_linux_console.py   | 411 --------------------------
>>   tests/functional/meson.build          |   4 +
>>   tests/functional/qemu_test/utils.py   |  21 ++
>>   tests/functional/test_arm_bpim2u.py   | 206 +++++++++++++
>>   tests/functional/test_arm_orangepi.py | 270 +++++++++++++++++
>>   6 files changed, 502 insertions(+), 411 deletions(-)
>>   create mode 100755 tests/functional/test_arm_bpim2u.py
>>   create mode 100755 tests/functional/test_arm_orangepi.py
>>
> 
> I have a general question regarding tests in QEMU.
> Is the current goal to convert all avocado tests to functional ones, and 
> then remove avocado from codebase?

Yes, I think that's the best way to move forward. It's weird to have two 
test runners in QEMU for the tests, and since we're already using the meson 
test runner for almost everything else, we should continue this transition.

  Thomas



  reply	other threads:[~2024-10-29 16:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29  9:24 [PATCH 0/2] Convert the BananaPi and OrangePi Avacodo tests Thomas Huth
2024-10-29  9:24 ` [PATCH 1/2] tests/functional: Convert BananaPi tests to the functional framework Thomas Huth
2024-10-29  9:24 ` [PATCH 2/2] tests/functional: Convert the OrangePi " Thomas Huth
2024-10-29 16:31 ` [PATCH 0/2] Convert the BananaPi and OrangePi Avacodo tests Pierrick Bouvier
2024-10-29 16:50   ` Thomas Huth [this message]
2024-10-29 16:54     ` Pierrick Bouvier

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=c95b7e5f-0345-4648-bae7-285ecde8dfd8@redhat.com \
    --to=thuth@redhat.com \
    --cc=joel@jms.id.au \
    --cc=nieklinnenbank@gmail.com \
    --cc=philmd@linaro.org \
    --cc=pierrick.bouvier@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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).