All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <amc96@cam.ac.uk>
To: Ian Jackson <iwj@xenproject.org>,
	Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 1/3] tools/tests: Drop obsolete running scripts
Date: Wed, 13 Jan 2021 13:15:06 +0000	[thread overview]
Message-ID: <f03ee65a-8b8a-57ac-0c78-0f9a356b2697@cam.ac.uk> (raw)
In-Reply-To: <24574.61324.543410.159952@mariner.uk.xensource.com>

On 13/01/2021 13:03, Ian Jackson wrote:
> Andrew Cooper writes ("[PATCH 1/3] tools/tests: Drop obsolete running scripts"):
>> The python unit tests were dropped in Xen 4.12 due to being obsolete, but the
>> scripts to run the tests were missed.  Clean up .gitignore as well
> I'm happy with this part.
>
>> Also drop the libxenctrl {C,LD}FLAGS adjustments in the Makefile.  This logic
>> isn't used, and isn't appropriate even in principle, as there are tests in
>> here which don't want to use libxenctrl.
> It's not clear to me that it's EBW to link all the tests to libxenctrl
> simply to make the build easier.
>
> In a later patch you add these settings back as part of a particular
> test target.
>
> I don't much mind it being done this way, and you've done the work, so
> I am giving this my ack, but I just wanted to register my qualm in
> case you had a second thought.

These lines aren't used, because this Makefile doesn't compile/link any
code.  They don't apply to subdirs.

More than half the remaining content in tests/ really are unit tests,
and must not be linked against libxc if they want to be run outside of
dom0 (e.g. the developers build box.)

> FTR, however, IMO the -DXC_WANT_COMPAT_DEVICEMODEL_API that you move
> to a specific test program in a later patch is something that ought
> not to be applied to all tests, so there doing it that way is
> necessary - thanks.
>
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>

Thanks,

~Andrew


  reply	other threads:[~2021-01-13 13:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13 12:34 [PATCH 0/3] Cleanup to tools/tests Andrew Cooper
2021-01-13 12:34 ` [PATCH 1/3] tools/tests: Drop obsolete running scripts Andrew Cooper
2021-01-13 13:03   ` Ian Jackson
2021-01-13 13:15     ` Andrew Cooper [this message]
2021-01-13 12:34 ` [PATCH 2/3] tools: Move xen-access from tests/ to misc/ Andrew Cooper
2021-01-13 13:03   ` Ian Jackson
2021-01-13 18:50   ` Tamas K Lengyel
2021-01-13 19:08     ` Andrew Cooper
2021-01-13 12:34 ` [PATCH 3/3] tools: Move memshrtool " Andrew Cooper
2021-01-13 13:01   ` Ian Jackson
2021-01-13 13:18     ` Andrew Cooper
2021-01-13 13:33       ` Ian Jackson

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=f03ee65a-8b8a-57ac-0c78-0f9a356b2697@cam.ac.uk \
    --to=amc96@cam.ac.uk \
    --cc=andrew.cooper3@citrix.com \
    --cc=iwj@xenproject.org \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.