| commit | c3e23dc117beae7e89e81aed28b0e082a14d672e | |
| author | Michael Haggerty <mhagger@alum.mit.edu> | |
| Tue, 2 Jun 2015 15:57:25 +0000 (2 17:57 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 2 Jun 2015 20:09:04 +0000 (2 13:09 -0700) | ||
| tree | 150cbeba9e2d9fa2aec3c31d222b3616f9fd0e74 | treesnapshot (tar.gz zip) |
| parent | 9a3d637541a5b6fcd84b6f5fa057e597d1696460 | commitdiff |
t6301: new tests of for-each-ref error handling
Add tests that for-each-ref correctly reports broken loose reference
files and references that point at missing objects. In fact, two of
these tests fail, because (1) NULL_SHA1 is not recognized as an
invalid reference value, and (2) for-each-ref doesn't respect
REF_ISBROKEN. Fixes to come.
Note that when for-each-ref is run with a --format option that doesn't
require the object to be looked up, then we should still notice if a
loose reference file is corrupt or contains NULL_SHA1, but we don't
notice if it points at a missing object because we don't do an object
lookup. This is OK.
Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Add tests that for-each-ref correctly reports broken loose reference
files and references that point at missing objects. In fact, two of
these tests fail, because (1) NULL_SHA1 is not recognized as an
invalid reference value, and (2) for-each-ref doesn't respect
REF_ISBROKEN. Fixes to come.
Note that when for-each-ref is run with a --format option that doesn't
require the object to be looked up, then we should still notice if a
loose reference file is corrupt or contains NULL_SHA1, but we don't
notice if it points at a missing object because we don't do an object
lookup. This is OK.
Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t6301-for-each-ref-errors.sh | [new file with mode: 0755] | blob |