From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
pbonzini@redhat.com, "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH 1/3] archive-source.sh: Drop submodule code
Date: Wed, 4 Apr 2018 09:23:31 +0100 [thread overview]
Message-ID: <20180404082331.GD3186@redhat.com> (raw)
In-Reply-To: <20180404025201.11921-2-famz@redhat.com>
On Wed, Apr 04, 2018 at 10:51:59AM +0800, Fam Zheng wrote:
> ./configure and make now take care of submodules, we only need to clone
> the top tree.
If you don't include the submodules in the tar.gz archive, then the
test system needs to be able to clone them from qemu.org, which
requires networking.
The VM tests have networking by default, but the docker tests do
not have networking - you need to opt-in by setting NETWORK=1
make variable. So AFAICT, this will break docker tests.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> scripts/archive-source.sh | 47 ++++-------------------------------------------
> 1 file changed, 4 insertions(+), 43 deletions(-)
>
> diff --git a/scripts/archive-source.sh b/scripts/archive-source.sh
> index 4e63774f9a..d53774d507 100755
> --- a/scripts/archive-source.sh
> +++ b/scripts/archive-source.sh
> @@ -18,51 +18,12 @@ if test $# -lt 1; then
> error "Usage: $0 <output tarball>"
> fi
>
> -tar_file=`realpath "$1"`
> -list_file="${tar_file}.list"
> -vroot_dir="${tar_file}.vroot"
> +tar_file="$1"
> +list_file="$1.list"
>
> -# We want a predictable list of submodules for builds, that is
> -# independent of what the developer currently has initialized
> -# in their checkout, because the build environment is completely
> -# different to the host OS.
> -submodules="dtc ui/keycodemapdb"
> +trap "status=$?; rm -f \"$list_file\"; exit \$status" 0 1 2 3 15
>
> -trap "status=$?; rm -rf \"$list_file\" \"$vroot_dir\"; exit \$status" 0 1 2 3 15
> -
> -if git diff-index --quiet HEAD -- &>/dev/null
> -then
> - HEAD=HEAD
> -else
> - HEAD=`git stash create`
> -fi
> -git clone --shared . "$vroot_dir"
> -test $? -ne 0 && error "failed to clone into '$vroot_dir'"
> -
> -cd "$vroot_dir"
> -test $? -ne 0 && error "failed to change into '$vroot_dir'"
> -
> -git checkout $HEAD
> -test $? -ne 0 && error "failed to checkout $HEAD revision"
> -
> -for sm in $submodules; do
> - git submodule update --init $sm
> - test $? -ne 0 && error "failed to init submodule $sm"
> -done
> -
> -if test -n "$submodules"; then
> - {
> - git ls-files || error "git ls-files failed"
> - for sm in $submodules; do
> - (cd $sm; git ls-files) | sed "s:^:$sm/:"
> - if test "${PIPESTATUS[*]}" != "0 0"; then
> - error "git ls-files in submodule $sm failed"
> - fi
> - done
> - } | grep -x -v $(for sm in $submodules; do echo "-e $sm"; done) > "$list_file"
> -else
> - git ls-files > "$list_file"
> -fi
> +( git ls-files && echo '.git' ) > "$list_file"
>
> if test $? -ne 0; then
> error "failed to generate list file"
> --
> 2.14.3
>
>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-04-04 8:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 2:51 [Qemu-devel] [PATCH 0/3] Add a CentOS test image to run docker tests Fam Zheng
2018-04-04 2:51 ` [Qemu-devel] [PATCH 1/3] archive-source.sh: Drop submodule code Fam Zheng
2018-04-04 8:23 ` Daniel P. Berrangé [this message]
2018-04-04 9:07 ` Fam Zheng
2018-04-04 9:24 ` Daniel P. Berrangé
2018-04-04 9:37 ` Fam Zheng
2018-04-04 2:52 ` [Qemu-devel] [PATCH 2/3] tests: Add an option for snapshot (default: off) Fam Zheng
2018-04-04 2:52 ` [Qemu-devel] [PATCH 3/3] tests: Add centos VM testing Fam Zheng
2018-04-04 3:01 ` [Qemu-devel] [PATCH 0/3] Add a CentOS test image to run docker tests no-reply
2018-04-04 3:04 ` no-reply
2018-04-04 5:03 ` Peter Xu
2018-04-04 6:56 ` Peter Xu
2018-04-04 8:19 ` Daniel P. Berrangé
2018-04-04 8:24 ` Fam Zheng
2018-04-06 16:47 ` Paolo Bonzini
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=20180404082331.GD3186@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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 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).