| Subject: | 4-push.t fails with new versions of Git (1.7.0+) |
t/4-push.t ..
1..3
Initialized empty shared Git repository in /home/jhe/src/dist-zilla-
plugin-git/t/push/.git/
Initialized empty shared Git repository in /tmp/WI3e310KCI/push/.git/
reading configuration using Dist::Zilla::Config::Finder
initializing plugin FakeRelease (Dist::Zilla::Plugin::FakeRelease)
initializing plugin Git::Commit (Dist::Zilla::Plugin::Git::Commit)
initializing plugin Git::Tag (Dist::Zilla::Plugin::Git::Tag)
initializing plugin Git::Push (Dist::Zilla::Plugin::Git::Push)
beginning to build Foo
writing Foo in Foo-1.23
writing archive to Foo-1.23.tar.gz
[FakeRelease] Fake realase happening (nothing was really done)
error: refusing to update checked out branch: refs/heads/master
error: By default, updating the current branch in a non-bare repository
error: is denied, because it will make the index and work tree
inconsistent
error: with what you pushed, and will require 'git reset --hard' to
match
error: the work tree to HEAD.
error:
error: You can set 'receive.denyCurrentBranch' configuration variable to
error: 'ignore' or 'warn' in the remote repository to allow pushing into
error: its current branch; however, this is not recommended unless you
error: arranged to update its work tree to match what you pushed in some
error: other way.
error:
error: To squelch this message and still keep the default behaviour, set
error: 'receive.denyCurrentBranch' configuration variable to 'refuse'.
To /tmp/WI3e310KCI/push
! [remote rejected] HEAD -> master (branch is currently checked out)
error: failed to push some refs to '/tmp/WI3e310KCI/push'
# Looks like your test exited with 1 before it could output anything.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 3/3 subtests
Test Summary Report
-------------------
t/4-push.t (Wstat: 256 Tests: 0 Failed: 0)
Non-zero exit status: 1
Parse errors: Bad plan. You planned 3 tests but ran 0.
Files=1, Tests=0, 1 wallclock secs ( 0.03 usr 0.01 sys + 0.84 cusr
0.17 csys = 1.05 CPU)
Result: FAIL
The repository created in /tmp should probably be a bare repository to
avoid this issue.