From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Guillaume Maudoux <layus.on@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: [RFC PATCH] tests: fix PATH for GIT_TEST_INSTALLED tests
Date: Sat, 14 Apr 2018 14:30:38 +0200 (DST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1804141423530.234@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz> (raw)
In-Reply-To: <20180414003338.27091-1-layus.on@gail.com>
Hi Guillaume,
On Sat, 14 Apr 2018, Guillaume Maudoux wrote:
> From: Guillaume Maudoux <layus.on@gmail.com>
>
> When running tests on an existing git installation with
> GIT_TEST_INSTALLED (as described in t/README), the test helpers are
> missing in the PATH.
>
> This fixes the test suite in a way that allows all the tests to pass.
>
> Signed-off-by: Guillaume Maudoux <layus.on@gmail.com>
> ---
>
> This is more a bug report than a real patch. The issue is described
> above and this patch does solve it. I however think that someone with
> more knowledge should refactor all that chunck of code that was last
> changed in 2010.
>
> In particular, it seems that the GIT_TEST_INSTALLED path does not use
> bin-wrappers at all. This may imply that --with-dashes also breaks
> tests.
>
> t/test-lib.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git t/test-lib.sh t/test-lib.sh
> index 7740d511d..0d51261f7 100644
> --- t/test-lib.sh
> +++ t/test-lib.sh
> @@ -923,7 +923,7 @@ elif test -n "$GIT_TEST_INSTALLED"
> then
> GIT_EXEC_PATH=$($GIT_TEST_INSTALLED/git --exec-path) ||
> error "Cannot run git from $GIT_TEST_INSTALLED."
> - PATH=$GIT_TEST_INSTALLED:$GIT_BUILD_DIR:$PATH
> + PATH=$GIT_TEST_INSTALLED:$GIT_BUILD_DIR/t/helper:$GIT_BUILD_DIR:$PATH
> GIT_EXEC_PATH=${GIT_TEST_EXEC_PATH:-$GIT_EXEC_PATH}
> else # normal case, use ../bin-wrappers only unless $with_dashes:
> git_bin_dir="$GIT_BUILD_DIR/bin-wrappers"
This is essentially identical to what we have in
http://github.com/git-for-windows/git/commit/e408b7517d
So: ACK.
You might also want to go a bit further and let the test suite run with
GIT_TEST_INSTALLED when Git has not actually be built, but only the test
helpers. I started something along those lines here:
http://github.com/git-for-windows/git/commit/a80f047abc5
I always meant to come back to polish those patches and submit them to the
Git mailing list, so: thank you for getting the ball rolling.
FWIW my use case is that I want to test a "MinGit" package, i.e. a subset
of Git for Windows intended to cater to third-party applications requiring
Git functionality (but not requiring any interactive parts of it).
What is your use case?
Ciao,
Johannes
next prev parent reply other threads:[~2018-04-14 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-14 0:33 [RFC PATCH] tests: fix PATH for GIT_TEST_INSTALLED tests Guillaume Maudoux
2018-04-14 12:30 ` Johannes Schindelin [this message]
2018-04-14 19:36 ` Guillaume Maudoux (Layus)
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.1804141423530.234@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=layus.on@gmail.com \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).