t5516-fetch-push.sh fails with current master (74301d6)

[Øyvind A . Holm]

When building from current master (74301d6, "Sync with maint",
2015-10-20), test #75 in t5516-fetch-push.sh fails:

*** t5516-fetch-push.sh ***
ok 1 - setup
ok 2 - fetch without wildcard
[Snip 70 lines]
ok 73 - fetch exact SHA1
ok 74 - shallow fetch reachable SHA1 (but not a ref), allowtipsha1inwant=true
not ok 75 - deny fetch unreachable SHA1, allowtipsha1inwant=true
#
# mk_empty testrepo &&
# (
# cd testrepo &&
# git config uploadpack.allowtipsha1inwant $configallowtipsha1inwant &&
# git commit --allow-empty -m foo &&
# git commit --allow-empty -m bar &&
# git commit --allow-empty -m xyz
# ) &&
# SHA1_1=$(git --git-dir=testrepo/.git rev-parse HEAD^^) &&
# SHA1_2=$(git --git-dir=testrepo/.git rev-parse HEAD^) &&
# SHA1_3=$(git --git-dir=testrepo/.git rev-parse HEAD) &&
# (
# cd testrepo &&
# git reset --hard $SHA1_2 &&
# git cat-file commit $SHA1_1 &&
# git cat-file commit $SHA1_3
# ) &&
# mk_empty shallow &&
# (
# cd shallow &&
# test_must_fail git fetch ../testrepo/.git $SHA1_3 &&
# test_must_fail git fetch ../testrepo/.git $SHA1_1 &&
# git --git-dir=../testrepo/.git config
uploadpack.allowreachablesha1inwant true &&
# git fetch ../testrepo/.git $SHA1_1 &&
# git cat-file commit $SHA1_1 &&
# test_must_fail git cat-file commit $SHA1_2 &&
# git fetch ../testrepo/.git $SHA1_2 &&
# git cat-file commit $SHA1_2 &&
# test_must_fail git fetch ../testrepo/.git $SHA1_3
# )
#
ok 76 - shallow fetch reachable SHA1 (but not a ref), allowtipsha1inwant=false
ok 77 - deny fetch unreachable SHA1, allowtipsha1inwant=false
ok 78 - fetch follows tags by default
ok 79 - pushing a specific ref applies remote.$name.push as refmap
ok 80 - with no remote.$name.push, it is not used as refmap
ok 81 - with no remote.$name.push, upstream mapping is used
ok 82 - push does not follow tags by default
ok 83 - push --follow-tag only pushes relevant tags
ok 84 - push --no-thin must produce non-thin pack
ok 85 - pushing a tag pushes the tagged object
ok 86 - push into bare respects core.logallrefupdates
ok 87 - fetch into bare respects core.logallrefupdates
ok 88 - receive.denyCurrentBranch = updateInstead
ok 89 - updateInstead with push-to-checkout hook
# failed 1 among 89 test(s)
1..89
make[2]: *** [t5516-fetch-push.sh] Error 1
make[2]: Leaving directory `/home/sunny/src/other/git/build-git/t'
make[1]: *** [test] Error 2
make[1]: Leaving directory `/home/sunny/src/other/git/build-git/t'
make: *** [test] Error 2

(Removed indents to reduce email wrapping)

OS: Debian GNU/Linux 7.9 (wheezy)
gcc (Debian 4.7.2-5) 4.7.2

Regards,
Øyvind
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: t5516-fetch-push.sh fails with current master (74301d6)

[Øyvind A . Holm]

On 21 October 2015 at 03:40, Øyvind A. Holm  wrote:
> When building from current master (74301d6, "Sync with maint",
> 2015-10-20), test #75 in t5516-fetch-push.sh fails

If it's of any value, the contents from
t/trash\ directory.t5516-fetch-push/ can be downloaded from
.

Regards,
Øyvind
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: t5516-fetch-push.sh fails with current master (74301d6)

[Øyvind A . Holm]

On 21 October 2015 at 04:01, Øyvind A. Holm  wrote:
> On 21 October 2015 at 03:40, Øyvind A. Holm  wrote:
> > When building from current master (74301d6, "Sync with maint",
> > 2015-10-20), test #75 in t5516-fetch-push.sh fails

Hm, seems as I'm unable to reproduce the failure. That's strange, I have
an automated build script I've been using for years, so the build
environment is unchanged from the previous builds. I'll investigate this
a bit and come back if there's anything newsworthy. In the meantime,
sorry about the noise.

Regards,
Øyvind
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html