| commit | c20d4d702f13e6bd4e4c8757989bed62a75e2cfa | |
| author | Jeff King <peff@peff.net> | |
| Tue, 24 Jan 2017 13:27:49 +0000 (24 08:27 -0500) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 25 Jan 2017 20:32:32 +0000 (25 12:32 -0800) | ||
| tree | f03fd31ea3b690eadf21e768f8c98481d4c22875 | treesnapshot (tar.gz zip) |
| parent | c2d17b3b6ef42b20b9da294a7a920491b907c503 | commitdiff |
t1450: use "mv -f" within loose object directory
The loose objects are created with mode 0444. That doesn't
prevent them being overwritten by rename(), but some
versions of "mv" will be extra careful and prompt the user,
even without "-i".
Reportedly macOS does this, at least in the Travis builds.
The prompt reads from /dev/null, defaulting to "no", and the
object isn't moved. Then to make matters even more
interesting, it still returns "0" and the rest of the test
proceeds, but with a broken setup.
We can work around it by using "mv -f" to override the
prompt. This should work as it's already used in t5504 for
the same purpose.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The loose objects are created with mode 0444. That doesn't
prevent them being overwritten by rename(), but some
versions of "mv" will be extra careful and prompt the user,
even without "-i".
Reportedly macOS does this, at least in the Travis builds.
The prompt reads from /dev/null, defaulting to "no", and the
object isn't moved. Then to make matters even more
interesting, it still returns "0" and the rest of the test
proceeds, but with a broken setup.
We can work around it by using "mv -f" to override the
prompt. This should work as it's already used in t5504 for
the same purpose.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t1450-fsck.sh | diffblobblamehistory |