From: Lars Schneider <larsxschneider@gmail.com>
To: Jeremy Huddleston Sequoia <jeremyhu@macports.org>
Cc: git@vger.kernel.org
Subject: Re: 2.9.2 test failures on macOS
Date: Wed, 3 Aug 2016 12:18:37 +0200 [thread overview]
Message-ID: <88BA92D6-305F-4B23-ABD2-55A6145F22D9@gmail.com> (raw)
In-Reply-To: <C4207508-629B-41DF-8E89-CDD1989BCF2E@macports.org>
> On 03 Aug 2016, at 09:35, Jeremy Huddleston Sequoia <jeremyhu@macports.org> wrote:
>
> I have two test failures to report in git 2.9.2 on macOS:
>
>
> t3210-pack-refs.sh has not changed between 2.8.4 and 2.9.2. This test passed fine with 2.8.4, but it now fails with 2.9.2 at:
>
> not ok 26 - retry acquiring packed-refs.lock
> #
> # LOCK=.git/packed-refs.lock &&
> # >"$LOCK" &&
> # test_when_finished "wait; rm -f $LOCK" &&
> # {
> # ( sleep 1 ; rm -f $LOCK ) &
> # } &&
> # git -c core.packedrefstimeout=3000 pack-refs --all --prune
> #
>
> ===
>
> t3700-add.sh recently added the 'git add --chmod=-x stages an executable file with -x' test. This test passes when run as a normal user but fails when run as root:
>
> $ ./t3700-add.sh
> ...
> # passed all 40 test(s)
> 1..40
>
> $ sudo ./t3700-add.sh
> ...
> not ok 39 - git add --chmod=-x stages an executable file with -x
> #
> # echo foo >xfoo1 &&
> # chmod 755 xfoo1 &&
> # git add --chmod=-x xfoo1 &&
> # case "$(git ls-files --stage xfoo1)" in
> # 100644" "*xfoo1) echo pass;;
> # *) echo fail; git ls-files --stage xfoo1; (exit 1);;
> # esac
> #
> # failed 1 among 40 test(s)
> 1..40
>
What OS version do you use? Can you run `sw_vers` in your terminal and share the result?
Thanks,
Lars
next prev parent reply other threads:[~2016-08-03 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 7:35 2.9.2 test failures on macOS Jeremy Huddleston Sequoia
2016-08-03 10:18 ` Lars Schneider [this message]
2016-08-03 14:35 ` Johannes Schindelin
2016-08-03 16:08 ` Jeremy Huddleston Sequoia
2016-08-03 15:58 ` Junio C Hamano
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=88BA92D6-305F-4B23-ABD2-55A6145F22D9@gmail.com \
--to=larsxschneider@gmail.com \
--cc=git@vger.kernel.org \
--cc=jeremyhu@macports.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.
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).