From: Philipp Gesang Date: Mon, 14 Aug 2017 09:54:17 +0000 (+0200) Subject: adjust the expectations about checksum mismatches with non-authenticated recover... X-Git-Tag: v2.2~7^2~73 X-Git-Url: http://developer.intra2net.com/git/?a=commitdiff_plain;h=14895f4b7bea135f62fa5ccccb85d62135019938;p=python-delta-tar adjust the expectations about checksum mismatches with non-authenticated recover modes --- diff --git a/testing/test_recover.py b/testing/test_recover.py index 9e1c0b1..8378afc 100644 --- a/testing/test_recover.py +++ b/testing/test_recover.py @@ -426,6 +426,9 @@ class RecoverCorruptTrailingDataSingleTest (RecoverCorruptTrailingDataTestBase): VOLUMES = 1 class RecoverCorruptTrailingDataMultiTest (RecoverCorruptTrailingDataTestBase): + # the last object in first archive has extra bytes somewhere in the + # middle because tar itself performs no data checksumming. + MISMATCHES = 1 VOLUMES = 3 @@ -443,6 +446,12 @@ class RecoverCorruptTrailingDataGZSingleTest (RecoverCorruptTrailingDataGZTestBa class RecoverCorruptTrailingDataGZMultiTest (RecoverCorruptTrailingDataGZTestBase): VOLUMES = 3 + # the last file of the first volume will only contain the data of the + # second part which is contained in the second volume. this happens + # because the CRC32 is wrong for the first part so it gets discarded, then + # the object is recreated from the first header of the second volume, + # containing only the remainder of the data. + MISMATCHES = 1 class RecoverCorruptTrailingDataGZAESTestBase (RecoverTest):