From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>, patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2 for-3.1 0/4] configure: symlink directories, not wildcarded files
Date: Fri, 2 Nov 2018 18:41:44 +0100 [thread overview]
Message-ID: <64c84ad5-614d-58c8-29a5-86df6d851161@redhat.com> (raw)
In-Reply-To: <20181102115239.22485-1-peter.maydell@linaro.org>
On 2/11/18 12:52, Peter Maydell wrote:
> This patchset fixes a problem with our build infrastructure
> that meant that MST's recent 'pci, pc, virtio' pullreq failed
> tests.
>
> Currently our configure script has a wildcard loop that creates
> symlinks for every data file in tests/acpi-test-data from the
> source tree to the build tree. However, if a new data file is
> added in git, there is nothing that causes configure to be rerun,
> and so it is not available in the build tree, which can cause
> test failures.
>
> In v1 of this patchset I addressed this by changing configure
> to make tests/acpi-test-data itself a symlink. Unfortunately
> this has an awkward consequence that if we did that and
> a developer switched git branches from one after that change
> to one before it then configure would end up trashing all
> the test files by making them symlinks to themselves.
> So instead in v2, we move all the data files to the tests/data/
> directory. tests/data/ is already symlinked as a directory,
> so there is no problem for bisection.
>
> Patch 1 does that for tests/acpi-test-data.
> Patch 2 does that for tests/hex-loader-check-data.
> Patch 3 is a cleanup, renaming a variable and adding
> documentation so that it's clearer that symlinking can
> be used for directories and that wildcarding files is bad.
> Patch 4 rolls some ad-hoc symlinking into the common loop.
>
> We do still use wildcarding to construct a list of files in
> pc-bios to be symlinked; we get away with this because we don't
> in practice add new BIOS images often and if we do there's also
> usually a change that means configure is rerun anyway. We can't
> just symlink all of pc-bios into the build tree because it
> contains other things than just generated binaries. There
> might be scope for fixing this, but I wanted to get this fix out.
>
> thanks
> -- PMM
>
> Peter Maydell (4):
> tests: Move tests/acpi-test-data/ to tests/data/acpi/
> tests: Move tests/hex-loader-check-data/ to tests/data/hex-loader/
> configure: Rename FILES variable to LINKS
> configure: Use LINKS loop for all build tree symlinks
I left one comment about when using rebuild-expected-aml.sh
in out-of-tree builds. Anyway for the series:
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
prev parent reply other threads:[~2018-11-02 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 11:52 [Qemu-devel] [PATCH v2 for-3.1 0/4] configure: symlink directories, not wildcarded files Peter Maydell
2018-11-02 11:52 ` [Qemu-devel] [PATCH v2 for-3.1 1/4] tests: Move tests/acpi-test-data/ to tests/data/acpi/ Peter Maydell
2018-11-02 17:38 ` Philippe Mathieu-Daudé
2018-11-02 17:42 ` Peter Maydell
2018-11-02 18:00 ` Philippe Mathieu-Daudé
2018-11-02 11:52 ` [Qemu-devel] [PATCH v2 for-3.1 2/4] tests: Move tests/hex-loader-check-data/ to tests/data/hex-loader/ Peter Maydell
2018-11-02 11:52 ` [Qemu-devel] [PATCH v2 for-3.1 3/4] configure: Rename FILES variable to LINKS Peter Maydell
2018-11-02 11:52 ` [Qemu-devel] [PATCH v2 for-3.1 4/4] configure: Use LINKS loop for all build tree symlinks Peter Maydell
2018-11-02 17:41 ` Philippe Mathieu-Daudé [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=64c84ad5-614d-58c8-29a5-86df6d851161@redhat.com \
--to=philmd@redhat.com \
--cc=mst@redhat.com \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--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).