public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <andrew.jones@linux.dev>
To: Jon Kohler <jon@nutanix.com>
Cc: Alexandru Elisei <alexandru.elisei@arm.com>,
	 Thomas Huth <thuth@redhat.com>,
	Nicholas Piggin <npiggin@gmail.com>,
	 Eric Auger <eric.auger@redhat.com>,
	Nina Schoetterl-Glausch <nsg@linux.ibm.com>,
	 "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [kvm-unit-tests PATCH] Makefile: add portable mode
Date: Mon, 13 Jan 2025 16:36:16 +0100	[thread overview]
Message-ID: <20250113-e645de551c7279ba77e4fb74@orel> (raw)
In-Reply-To: <806860A3-4538-4BC3-B6B9-FA5118990D78@nutanix.com>

On Mon, Jan 13, 2025 at 02:49:11PM +0000, Jon Kohler wrote:
> 
> 
> > On Jan 13, 2025, at 8:07 AM, Alexandru Elisei <alexandru.elisei@arm.com> wrote:
> > 
> > !-------------------------------------------------------------------|
> >  CAUTION: External Email
> > 
> > |-------------------------------------------------------------------!
> > 
> > Hi,
> > 
> > On Sun, Jan 05, 2025 at 10:57:23AM -0700, Jon Kohler wrote:
> >> Add a 'portable' mode that packages all relevant flat files and helper
> >> scripts into a tarball named 'kut-portable.tar.gz'.
> >> 
> >> This mode is useful for compiling tests on one machine and running them
> >> on another without needing to clone the entire repository. It allows
> >> the runner scripts and unit test configurations to remain local to the
> >> machine under test.
> > 
> > Have you tried make standalone? You can then copy the tests directory, or even a
> > particular test.
> 
> Yes, standalone does not work when copying tests from one host to another. The
> use case for portable mode is to be able to compile within one environment and
> test in completely separate environment. I was not able to accomplish that with
> standalone mode by itself.
>

standalone scripts should be portable. If they're missing something, then
we should fix that. Also 'make install' should include everything
necessary, otherwise it should be fixed. Then, we could consider adding
another target like 'make package' which would do 'make install' to a
temporary directory and tar/gzip or whatever the installation into a
package.

Thanks,
drew

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-05 17:57 [kvm-unit-tests PATCH] Makefile: add portable mode Jon Kohler
2025-01-13 13:07 ` Alexandru Elisei
2025-01-13 14:49   ` Jon Kohler
2025-01-13 15:36     ` Andrew Jones [this message]
2025-01-13 20:53       ` Jon Kohler
2025-01-14  9:20         ` Andrew Jones

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=20250113-e645de551c7279ba77e4fb74@orel \
    --to=andrew.jones@linux.dev \
    --cc=alexandru.elisei@arm.com \
    --cc=eric.auger@redhat.com \
    --cc=jon@nutanix.com \
    --cc=kvm@vger.kernel.org \
    --cc=npiggin@gmail.com \
    --cc=nsg@linux.ibm.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