qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, qemu-arm@nongnu.org,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Cleber Rosa" <crosa@redhat.com>
Subject: Re: [PATCH] tests/acceptance: Add boot tests for some of the QEMU advent calendar images
Date: Mon, 27 Jan 2020 11:38:11 +0100	[thread overview]
Message-ID: <168c4f7b-fda5-2d9f-15b8-7100d5b0974d@redhat.com> (raw)
In-Reply-To: <4d5fe645-0652-893f-4e6b-2929849d3cdc@amsat.org>

On 25/01/2020 19.38, Philippe Mathieu-Daudé wrote:
> On 1/25/20 5:43 PM, Thomas Huth wrote:
>> On 24/01/2020 22.28, Wainer dos Santos Moschetta wrote:
>>>
>>> On 1/24/20 3:03 PM, Thomas Huth wrote:
>>>> The 2018 edition of the QEMU advent calendar 2018 featured Linux images
>>>> for various non-x86 machines. We can use them for a boot tests in our
>>>> acceptance test suite.
> 
> Excellent idea!
> 
>>>>
>>>> Let's also make sure that we build the corresponding machines in Travis,
>>>> and while we're there, drop the superfluous --python parameter (python3
>>>> is now the only supported version anyway).
> 
> I'd rather see this change as another commit.

I thought so, too, often it is good to separate stuff into separate
commits, but in this case, it's not source code but just the CI yml
file, and the change is really trivial, so it rather sounds like
superfluous churn to me in this case to do it in a separate patch...

>>> Yes, please, removal of --python was in my wish list.
>>>
>>>>
>>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>>> ---
>>>>   .travis.yml                            |  2 +-
>>>>   tests/acceptance/boot_linux_console.py | 96 ++++++++++++++++++++++++++
>>>>   2 files changed, 97 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/.travis.yml b/.travis.yml
>>>> index 6c1038a0f1..73ca12c921 100644
>>>> --- a/.travis.yml
>>>> +++ b/.travis.yml
>>>> @@ -268,7 +268,7 @@ matrix:
>>>>         # Acceptance (Functional) tests
>>>>       - env:
>>>> -        - CONFIG="--python=/usr/bin/python3
>>>> --target-list=x86_64-softmmu,mips-softmmu,mips64el-softmmu,aarch64-softmmu,arm-softmmu,s390x-softmmu,alpha-softmmu,ppc-softmmu,ppc64-softmmu,m68k-softmmu,sparc-softmmu"
>>>>
>>>> +        -
>>>> CONFIG="--target-list=aarch64-softmmu,alpha-softmmu,arm-softmmu,m68k-softmmu,microblaze-softmmu,mips-softmmu,mips64el-softmmu,nios2-softmmu,or1k-softmmu,ppc-softmmu,ppc64-softmmu,s390x-softmmu,sparc-softmmu,x86_64-softmmu,xtensa-softmmu"
>>>>
>>>
>>>
>>> Perhaps use MAIN_SOFTMMU_TARGETS in only append the other targets, like:
>>>
>>> --target-list=${MAIN_SOFTMMU_TARGETS},alpha-softmmu,sparc-softmmu,....
>>
>> Not sure ... while it is a nice way to shorten the line here, it adds a
>> dependency to that variable ... and MAIN_SOFTMMU_TARGETS has been changed
>> a couple of times during the course of time, so we might risk to lose
>> some testing coverage here in case someone removes a target from
>> MAIN_SOFTMMU_TARGETS but forgets to add it here again...? I think we
>> should better use the explicit list here instead.
> 
> Maybe related: "Split enterprise vs. hobbyist acceptance test job"
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg644683.html

I guess naming/splitting is hard in this case ... many targets contain
both, "enterprise" and "hobbyist" machines ... and as long as the Travis
job runs reasonably fast, it's also not really necessary to split it.
The only real ugliness is the very long line - I haven't found a way yet
to correctly wrap this in the YML file to multiple lines .... does
anybody know how to do this in YML?

> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org>

Thanks!

 Thomas



  reply	other threads:[~2020-01-27 10:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24 17:03 [PATCH] tests/acceptance: Add boot tests for some of the QEMU advent calendar images Thomas Huth
2020-01-24 19:14 ` Liam Merwick
2020-01-24 21:28 ` Wainer dos Santos Moschetta
2020-01-25 16:43   ` Thomas Huth
2020-01-25 18:38     ` Philippe Mathieu-Daudé
2020-01-27 10:38       ` Thomas Huth [this message]
2020-01-27 14:05         ` Wainer dos Santos Moschetta
2020-01-27 14:10           ` Thomas Huth
2020-01-27 13:22     ` Wainer dos Santos Moschetta
2020-01-27 17:31 ` Wainer dos Santos Moschetta
2020-01-29 14:49   ` Thomas Huth
2020-01-29 17:48     ` BALATON Zoltan
2020-01-30  8:16       ` Thomas Huth
2020-01-30 14:12 ` Wainer dos Santos Moschetta
2020-01-30 23:10 ` Philippe Mathieu-Daudé

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=168c4f7b-fda5-2d9f-15b8-7100d5b0974d@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=crosa@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).