From: "Cédric Le Goater" <clg@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Steven Lee" <steven_lee@aspeedtech.com>,
"Troy Lee" <leetroy@gmail.com>,
"Jamin Lin" <jamin_lin@aspeedtech.com>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Joel Stanley" <joel@jms.id.au>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH 1/7] tests/functional: Introduce a specific test for ast1030 SoC
Date: Mon, 9 Dec 2024 07:47:35 +0100 [thread overview]
Message-ID: <b4c2869f-859e-4c16-8161-b1b48cb253f5@redhat.com> (raw)
In-Reply-To: <743c8876-91eb-46ae-a3ea-4bee0ddb4e89@redhat.com>
On 12/6/24 14:48, Thomas Huth wrote:
> On 06/12/2024 14.11, Cédric Le Goater wrote:
>> This simply moves the ast1030 tests to a new test file. No changes.
>>
>> Signed-off-by: Cédric Le Goater <clg@redhat.com>
>> ---
>> tests/functional/meson.build | 2 +
>> tests/functional/test_arm_aspeed.py | 64 ----------------
>> tests/functional/test_arm_aspeed_ast1030.py | 81 +++++++++++++++++++++
>> 3 files changed, 83 insertions(+), 64 deletions(-)
>> create mode 100644 tests/functional/test_arm_aspeed_ast1030.py
>>
>> diff --git a/tests/functional/meson.build b/tests/functional/meson.build
>> index d6d2c0196c76..ef593d4b9928 100644
>> --- a/tests/functional/meson.build
>> +++ b/tests/functional/meson.build
>> @@ -18,6 +18,7 @@ test_timeouts = {
>> 'aarch64_tuxrun' : 240,
>> 'aarch64_virt' : 720,
>> 'acpi_bits' : 420,
>> + 'arm_aspeed_ast1030' : 10,
>
> We've got a default timeout of 90 seconds (see the end of meson.build) ... no need to set a smaller one, so I think you could simply drop this line.
OK. I will drop this change before applying.
>
> With that line removed:
> Reviewed-by: Thomas Huth <thuth@redhat.com>
>
Thanks,
C.
next prev parent reply other threads:[~2024-12-09 6:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 13:11 [PATCH 0/7] tests/functional: Split aspeed tests Cédric Le Goater
2024-12-06 13:11 ` [PATCH 1/7] tests/functional: Introduce a specific test for ast1030 SoC Cédric Le Goater
2024-12-06 13:48 ` Thomas Huth
2024-12-09 6:47 ` Cédric Le Goater [this message]
2024-12-06 13:11 ` [PATCH 2/7] tests/functional: Introduce a specific test for palmetto-bmc machine Cédric Le Goater
2024-12-06 13:52 ` Thomas Huth
2024-12-06 13:11 ` [PATCH 3/7] tests/functional: Introduce a specific test for romulus-bmc machine Cédric Le Goater
2024-12-06 13:59 ` Thomas Huth
2024-12-06 13:11 ` [PATCH 4/7] tests/functional: Introduce a specific test for ast2500 SoC Cédric Le Goater
2024-12-06 14:01 ` Thomas Huth
2024-12-06 13:11 ` [PATCH 5/7] tests/functional: Introduce a specific test for ast2600 SoC Cédric Le Goater
2024-12-06 14:04 ` Thomas Huth
2024-12-06 13:11 ` [PATCH 6/7] tests/functional: Introduce a specific test for rainier-bmc machine Cédric Le Goater
2024-12-09 11:59 ` Thomas Huth
2024-12-06 13:11 ` [PATCH 7/7] tests/functional: Move debian boot test from avocado Cédric Le Goater
2024-12-06 14:12 ` Thomas Huth
2024-12-09 13:43 ` [PATCH 0/7] tests/functional: Split aspeed tests Cédric Le Goater
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=b4c2869f-859e-4c16-8161-b1b48cb253f5@redhat.com \
--to=clg@redhat.com \
--cc=andrew@codeconstruct.com.au \
--cc=jamin_lin@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=leetroy@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=steven_lee@aspeedtech.com \
--cc=thuth@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).