From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Jan Keromnes <janx@linux.com>, git@vger.kernel.org
Subject: Re: [regression] `make profile-install` fails in 2.10.1
Date: Wed, 19 Oct 2016 15:30:44 -0700 [thread overview]
Message-ID: <xmqqd1iwj7jf.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqqh988j7oo.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Wed, 19 Oct 2016 15:27:35 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Ouch. Thanks for a reminder. How about doing this for now?
And the hack I used to quickly test it looks like this:
$ cd t
$ GIT_I_AM_INSANE=Yes sh ./t3700-add.sh
We may want a more general
GIT_OVERRIDE_PREREQ='!SANITY,!POSIXPERM,MINGW' make test
or something like that, though.
t/test-lib.sh | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/t/test-lib.sh b/t/test-lib.sh
index 0055ebba46..9c5bcd9d1d 100644
--- a/t/test-lib.sh
+++ b/t/test-lib.sh
@@ -89,6 +89,7 @@ unset VISUAL EMAIL LANGUAGE COLUMNS $("$PERL_PATH" -e '
UNZIP
PERF_
CURL_VERBOSE
+ I_AM_INSANE
));
my @vars = grep(/^GIT_/ && !/^GIT_($ok)/o, @env);
print join("\n", @vars);
@@ -1081,6 +1082,12 @@ test_lazy_prereq NOT_ROOT '
# containing directory doesn't have read or execute permissions.
test_lazy_prereq SANITY '
+
+ if test -n "$GIT_I_AM_INSANE"
+ then
+ return 1
+ fi &&
+
mkdir SANETESTD.1 SANETESTD.2 &&
chmod +w SANETESTD.1 SANETESTD.2 &&
next prev parent reply other threads:[~2016-10-19 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 11:15 [regression] `make profile-install` fails in 2.10.1 Jan Keromnes
2016-10-19 21:05 ` Jeff King
2016-10-19 22:27 ` Junio C Hamano
2016-10-19 22:30 ` Junio C Hamano [this message]
2016-10-19 22:38 ` Jeff King
2016-10-20 16:23 ` Junio C Hamano
2016-10-19 22:37 ` Jeff King
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=xmqqd1iwj7jf.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=janx@linux.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).