summaryrefslogtreecommitdiff
path: root/t
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2016-12-19 14:45:35 -0800
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-12-19 14:45:35 -0800
commit95713ff4fb858c4f2e7c339cfc503c0cf152e071 (patch)
tree988d8503fff22d5ddcc2d21afb88e05e5f295350 /t
parentMerge branch 'jk/xdiff-drop-xdl-fast-hash' (diff)
parentlockfile: LOCK_REPORT_ON_ERROR (diff)
downloadtgif-95713ff4fb858c4f2e7c339cfc503c0cf152e071.tar.xz
Merge branch 'jc/lock-report-on-error'
Git 2.11 had a minor regression in "merge --ff-only" that competed with another process that simultanously attempted to update the index. We used to explain what went wrong with an error message, but the new code silently failed. The error message has been resurrected. * jc/lock-report-on-error: lockfile: LOCK_REPORT_ON_ERROR hold_locked_index(): align error handling with hold_lockfile_for_update() wt-status: implement opportunisitc index update correctly
Diffstat (limited to 't')
-rw-r--r--t/helper/test-scrap-cache-tree.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/t/helper/test-scrap-cache-tree.c b/t/helper/test-scrap-cache-tree.c
index 27fe0405b8..d2a63bea43 100644
--- a/t/helper/test-scrap-cache-tree.c
+++ b/t/helper/test-scrap-cache-tree.c
@@ -8,7 +8,7 @@ static struct lock_file index_lock;
int cmd_main(int ac, const char **av)
{
setup_git_directory();
- hold_locked_index(&index_lock, 1);
+ hold_locked_index(&index_lock, LOCK_DIE_ON_ERROR);
if (read_cache() < 0)
die("unable to read index file");
active_cache_tree = NULL;