> On 24 Jan 2017, at 01:18, Junio C Hamano <gits...@pobox.com> wrote: > > * jk/fsck-connectivity-check-fix (2017-01-17) 6 commits > (merged to 'next' on 2017-01-23 at e8e9b76b84) > + fsck: check HAS_OBJ more consistently > + fsck: do not fallback "git fsck <bogus>" to "git fsck" > + fsck: tighten error-checks of "git fsck <head>" > + fsck: prepare dummy objects for --connectivity-check > + fsck: report trees as dangling > + t1450: clean up sub-objects in duplicate-entry test > > "git fsck --connectivity-check" was not working at all. > > Will merge to 'master'.
"fsck: prepare dummy objects for --connectivity-check" seems to make t1450-fsck.sh fail on macOS with TravisCI: Initialized empty Git repository in /Users/travis/build/git/git/t/trash directory.t1450-fsck/connectivity-only/.git/ [master (root-commit) 86520b7] empty Author: A U Thor <aut...@example.com> 2 files changed, 1 insertion(+) create mode 100644 empty create mode 100644 empty.t override r--r--r-- travis/staff for .git/objects/e6/9de29bb2d1d6434b8b29ae775ad8c2e48c5391? (y/n [n]) not overwritten dangling blob c21c9352f7526e9576892a6631e0e8cf1fccd34d test_must_fail: command succeeded: git fsck --strict not ok 58 - fsck --connectivity-only More test output: https://travis-ci.org/git/git/jobs/194663620 For some reason I am not able to replicate that behavior on my local macOS machine. I found the commit using bisect on TravisCI: https://api.travis-ci.org/jobs/194746454/log.txt?deansi=true Any idea what might be wrong? - Lars
