| commit | 2fca19fbb524d028bff0467762186e641aa3351a | |
| author | Nicolas Pitre <nico@fluxnic.net> | |
| Thu, 4 Feb 2010 03:48:26 +0000 (3 22:48 -0500) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 4 Feb 2010 04:38:47 +0000 (3 20:38 -0800) | ||
| tree | 75b57158a8e6667d4e3466f09ab1bc00baf8c914 | treesnapshot (tar.gz zip) |
| parent | 57017b3e1554b169f3db52a7f8da4e359d043ca8 | commitdiff |
fix multiple issues with t5300
First of all, trying to run 'git verify-pack' on packs produced by
the tests using pack.packSizeLimit always failed. After lots of digging
and head scratching, it turns out that the preceeding test simulating
a SHA1 collision did leave the repository quite confused, impacting
subsequent tests.
So let's move that destructive test last, and add tests to run
verify-pack on the output from those packSizeLimit tests to catch such
goofage.
Finally, group those packSizeLimit tests together.
Signed-off-by: Nicolas Pitre <nico@fluxnic.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
First of all, trying to run 'git verify-pack' on packs produced by
the tests using pack.packSizeLimit always failed. After lots of digging
and head scratching, it turns out that the preceeding test simulating
a SHA1 collision did leave the repository quite confused, impacting
subsequent tests.
So let's move that destructive test last, and add tests to run
verify-pack on the output from those packSizeLimit tests to catch such
goofage.
Finally, group those packSizeLimit tests together.
Signed-off-by: Nicolas Pitre <nico@fluxnic.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t5300-pack-object.sh | diffblobblamehistory |