reftable: consistently treat BISECT_EXPECTED_REV as a reference
While Git uses update_ref()
to write to BISECT_EXPECTED_REV
, it doesn't read back the reference via the refdb. This causes breakage with the reftable backend e.g. in the following testcase in t6030:
test_expect_success 'bad merge base when good and bad are siblings' '
git bisect start "$HASH7" HEAD > my_bisect_log.txt &&
test_grep "merge base must be tested" my_bisect_log.txt &&
grep $HASH4 my_bisect_log.txt &&
test_must_fail git bisect bad > my_bisect_log.txt 2>&1 &&
test_pause -a &&
test_grep "merge base $HASH4 is bad" my_bisect_log.txt &&
test_grep "fixed between $HASH4 and \[$SIDE_HASH7\]" my_bisect_log.txt &&
git bisect reset
'
Edited by Patrick Steinhardt