mirror of
https://github.com/git/git.git
synced 2024-10-30 05:47:53 +01:00
t5319: change invalid offset for SHA-256 compatibility
When using SHA-1, the existing value of the byte we use is 0x13, so writing the byte 0x07 serves to corrupt the test and verify that we detect corruption. However, when we use SHA-256, the value at that offset is already 0x07, so our "corruption" doesn't work and the test fails to detect it. To provide a value that is truly out of range, let's use 0xff, which is not likely to be a valid value as the high byte of a two-byte offset in a multi-pack index this small. Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
parent
1d86c8f0ce
commit
235d3cddb8
1 changed files with 2 additions and 2 deletions
|
@ -304,12 +304,12 @@ test_expect_success 'verify incorrect pack-int-id' '
|
||||||
'
|
'
|
||||||
|
|
||||||
test_expect_success 'verify incorrect offset' '
|
test_expect_success 'verify incorrect offset' '
|
||||||
corrupt_midx_and_verify $MIDX_BYTE_OFFSET "\07" $objdir \
|
corrupt_midx_and_verify $MIDX_BYTE_OFFSET "\377" $objdir \
|
||||||
"incorrect object offset"
|
"incorrect object offset"
|
||||||
'
|
'
|
||||||
|
|
||||||
test_expect_success 'git-fsck incorrect offset' '
|
test_expect_success 'git-fsck incorrect offset' '
|
||||||
corrupt_midx_and_verify $MIDX_BYTE_OFFSET "\07" $objdir \
|
corrupt_midx_and_verify $MIDX_BYTE_OFFSET "\377" $objdir \
|
||||||
"incorrect object offset" \
|
"incorrect object offset" \
|
||||||
"git -c core.multipackindex=true fsck"
|
"git -c core.multipackindex=true fsck"
|
||||||
'
|
'
|
||||||
|
|
Loading…
Reference in a new issue