From: Anthony PERARD <anthony@xenproject.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Subject: Re: [PATCH 2/3] tools/tests: Install tests into $(LIBEXEC)/tests
Date: Mon, 26 May 2025 18:56:55 +0200 [thread overview]
Message-ID: <aDSdVx116mXNKJr5@l14> (raw)
In-Reply-To: <20250520205239.203253-3-andrew.cooper3@citrix.com>
On Tue, May 20, 2025 at 09:52:38PM +0100, Andrew Cooper wrote:
> $(LIBEXEC_BIN) is a dumping ground of many things. Separate the "clearly
> tests" from everything else so we can clean up how they're run in CI.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Anthony PERARD <anthony.perard@vates.tech>
Thanks,
--
Anthony PERARD
next prev parent reply other threads:[~2025-05-26 16:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 20:52 [PATCH 0/3] CI: Improvements to *-tools-test-* jobs Andrew Cooper
2025-05-20 20:52 ` [PATCH 1/3] tools/tests: Drop depriv-fd-checker Andrew Cooper
2025-05-26 16:42 ` Anthony PERARD
2025-05-28 0:07 ` Stefano Stabellini
2025-05-20 20:52 ` [PATCH 2/3] tools/tests: Install tests into $(LIBEXEC)/tests Andrew Cooper
2025-05-26 16:56 ` Anthony PERARD [this message]
2025-05-28 0:07 ` Stefano Stabellini
2025-05-20 20:52 ` [PATCH 3/3] CI: Drop custom handling of tools/tests Andrew Cooper
2025-05-26 16:45 ` Andrew Cooper
2025-05-26 17:22 ` Anthony PERARD
2025-05-26 17:31 ` Andrew Cooper
2025-05-28 0:16 ` Stefano Stabellini
2025-05-28 0:18 ` Andrew Cooper
2025-05-21 0:10 ` [PATCH 0/3] CI: Improvements to *-tools-test-* jobs dmkhn
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=aDSdVx116mXNKJr5@l14 \
--to=anthony@xenproject.org \
--cc=andrew.cooper3@citrix.com \
--cc=marmarek@invisiblethingslab.com \
--cc=sstabellini@kernel.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.