From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Kyle J. McKay" <mackyle@gmail.com>,
"Torsten Bögershausen" <tboegi@web.de>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: t5539 broken under Mac OS X
Date: Thu, 15 Jan 2015 17:27:19 -0500 [thread overview]
Message-ID: <20150115222719.GA19021@peff.net> (raw)
In-Reply-To: <xmqqwq4n6b4c.fsf@gitster.dls.corp.google.com>
On Thu, Jan 15, 2015 at 12:29:39PM -0800, Junio C Hamano wrote:
> This should not be the final patch (I think it should become a lazy
> prereq as it does a lot more), but just for testing, how does this
> look?
>
> t/test-lib.sh | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/t/test-lib.sh b/t/test-lib.sh
> index bb1402d..cdafab5 100644
> --- a/t/test-lib.sh
> +++ b/t/test-lib.sh
> @@ -1033,7 +1033,16 @@ test_lazy_prereq USR_BIN_TIME '
>
> # When the tests are run as root, permission tests will report that
> # things are writable when they shouldn't be.
> -test -w / || test_set_prereq SANITY
> +if test_have_prereq POSIXPERM &&
> + ! test -w / &&
> + >sanitytest &&
> + chmod a= sanitytest &&
> + ! (>sanitytest) 2>/dev/null &&
> + chmod +w sanitytest &&
> + rm -f sanitytest
> +then
> + test_set_prereq SANITY
> +fi
The current scheme does not require POSIXPERM. Would this mean that
some platforms no longer runs SANITY tests (e.g., Windows)?
Many of the SANITY-marked tests already require both, but not all. And
certainly lib-httpd actually cares whether you are _truly_ root, not
about weird filesystem permissions. Should lib-httpd literally be
checking the output of `id` (though I can imagine that is anything but
portable)?
-Peff
next prev parent reply other threads:[~2015-01-15 22:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 15:39 t5539 broken under Mac OS X Torsten Bögershausen
2015-01-14 18:37 ` Junio C Hamano
2015-01-14 19:50 ` Torsten Bögershausen
2015-01-14 21:17 ` Jeff King
2015-01-15 5:48 ` Kyle J. McKay
2015-01-15 20:29 ` Junio C Hamano
2015-01-15 22:27 ` Jeff King [this message]
2015-01-15 22:39 ` Junio C Hamano
2015-01-15 23:57 ` Jeff King
2015-01-16 0:04 ` Junio C Hamano
2015-01-16 1:32 ` [PATCH] t/lib-httpd: switch SANITY check for NOT_ROOT Jeff King
2015-01-16 3:27 ` Kyle J. McKay
2015-01-16 3:34 ` Jeff King
2015-01-16 9:16 ` Jeff King
2015-01-16 18:32 ` Junio C Hamano
2015-01-16 19:02 ` Junio C Hamano
2015-01-17 23:35 ` Torsten Bögershausen
2015-01-21 22:33 ` Junio C Hamano
2015-01-22 21:51 ` Torsten Bögershausen
2015-01-22 22:07 ` Junio C Hamano
2015-01-23 6:00 ` Torsten Bögershausen
2015-02-12 22:36 ` Junio C Hamano
2015-02-14 8:36 ` [msysGit] " Torsten Bögershausen
2015-02-15 23:48 ` Junio C Hamano
2015-01-23 21:24 ` [msysGit] " Torsten Bögershausen
2015-01-23 23:02 ` Junio C Hamano
2015-01-24 9:41 ` [msysGit] " Johannes Schindelin
2015-01-16 18:38 ` Kyle J. McKay
2015-01-16 18:38 ` Kyle J. McKay
2015-01-16 20:04 ` Achim Gratz
2015-01-27 1:44 ` t5539 broken under Mac OS X Erik Faye-Lund
2015-01-27 2:51 ` Junio C Hamano
2015-01-27 16:35 ` Erik Faye-Lund
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=20150115222719.GA19021@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mackyle@gmail.com \
--cc=tboegi@web.de \
/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).