qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Stefan Weil <sw@weilnetz.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] w32: Support tests (make check)
Date: Sat, 25 Feb 2012 17:52:17 +0100	[thread overview]
Message-ID: <4F4911C1.4020009@suse.de> (raw)
In-Reply-To: <4F490EA7.3000702@weilnetz.de>

Am 25.02.2012 17:39, schrieb Stefan Weil:
> Am 25.02.2012 17:31, schrieb Andreas Färber:
>> Am 22.02.2012 20:48, schrieb Stefan Weil:
>>> Adding $(EXESUF) is needed to make those tests work on w32 hosts, too.
>>>
>>> v2:
>>> Rebased, added new tests, tests sorted alphabetically.
>>>
>>> Signed-off-by: Stefan Weil <sw@weilnetz.de>
>>> ---
>>> tests/Makefile | 38 +++++++++++++++++++++++---------------
>>> 1 files changed, 23 insertions(+), 15 deletions(-)
>>>
>>> diff --git a/tests/Makefile b/tests/Makefile
>>> index 74b29dc..09f2b13 100644
>>> --- a/tests/Makefile
>>> +++ b/tests/Makefile
>>> @@ -1,16 +1,24 @@
>>> -CHECKS = check-qdict check-qfloat check-qint check-qstring check-qlist
>>> -CHECKS += check-qjson test-qmp-output-visitor test-qmp-input-visitor
>>> -CHECKS += test-string-input-visitor test-string-output-visitor
>>> test-coroutine
>>> +CHECKS = check-qdict$(EXESUF)
>>> +CHECKS += check-qfloat$(EXESUF)
>>> +CHECKS += check-qint$(EXESUF)
>>> +CHECKS += check-qjson$(EXESUF)
>>> +CHECKS += check-qlist$(EXESUF)
>>> +CHECKS += check-qstring$(EXESUF)
>>> +CHECKS += test-coroutine$(EXESUF)
>>> +CHECKS += test-qmp-input-visitor$(EXESUF)
>>> +CHECKS += test-qmp-output-visitor$(EXESUF)
>>> +CHECKS += test-string-input-visitor$(EXESUF)
>>> +CHECKS += test-string-output-visitor$(EXESUF)
>>
>> Cute. (one-per-line allows to easily comment individual ones out)
>>
>> Some lines below were already way over 80 chars, so
>>
>> Reviewed-by: Andreas Färber <afaerber@suse.de>
>>
>> Andreas
> 
> And as long as they remain sorted, they also reduce the risk
> of merge conflicts:
> 
> When everybody just adds to the end,two different commits
> will always conflict.
> 
> They won't conflictif both commits add new lines at different
> locations.

I'd rather not strictly keep it in alphabetical order since having one
test pass might be a prerequisite for another test to be meaningful
(e.g., qfloat before pi). IMO we should have groups of tests, in which
we can order them alphabetically.
Anyway, my line of thinking was that no such interdependency is
documented here so it should be permissible to rearrange the order now.
The q* and the visitors are still together, input before output, so I
like it. We could add lines before test-coroutine and
test-qmp-input-visitors to group them by topic if we wanted, but the
list is still small, so no real need.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

      reply	other threads:[~2012-02-25 16:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 19:48 [Qemu-devel] [PATCH v2] w32: Support tests (make check) Stefan Weil
2012-02-25 16:31 ` Andreas Färber
2012-02-25 16:39   ` Stefan Weil
2012-02-25 16:52     ` Andreas Färber [this message]

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=4F4911C1.4020009@suse.de \
    --to=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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).