 8fbb03a180
			
		
	
	8fbb03a180
	
	
	
		
			
			When trying to find a good spot for testing clone with submodules, I got confused where to add a new test file. There are both tests in t560* as well as t57* both testing the clone command. t/README claims the second digit is to indicate the command, which is inconsistent to the current naming structure. Rename all t57* tests to be in t56* to follow the pattern of the digits as laid out in t/README. It would have been less work to rename t56* => t57* because there are less files, but the tests in t56* look more basic and I assumed the higher the last digits the more complicated niche details are tested, so with the patch now it looks more in order to me. Signed-off-by: Stefan Beller <sbeller@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
		
			
				
	
	
		
			75 lines
		
	
	
		
			2.0 KiB
		
	
	
	
		
			Bash
		
	
	
		
			Executable File
		
	
	
	
	
			
		
		
	
	
			75 lines
		
	
	
		
			2.0 KiB
		
	
	
	
		
			Bash
		
	
	
		
			Executable File
		
	
	
	
	
| #!/bin/sh
 | |
| 
 | |
| test_description='some bundle related tests'
 | |
| . ./test-lib.sh
 | |
| 
 | |
| test_expect_success 'setup' '
 | |
| 	test_commit initial &&
 | |
| 	test_tick &&
 | |
| 	git tag -m tag tag &&
 | |
| 	test_commit second &&
 | |
| 	test_commit third &&
 | |
| 	git tag -d initial &&
 | |
| 	git tag -d second &&
 | |
| 	git tag -d third
 | |
| '
 | |
| 
 | |
| test_expect_success 'annotated tags can be excluded by rev-list options' '
 | |
| 	git bundle create bundle --all --since=7.Apr.2005.15:14:00.-0700 &&
 | |
| 	git ls-remote bundle > output &&
 | |
| 	grep tag output &&
 | |
| 	git bundle create bundle --all --since=7.Apr.2005.15:16:00.-0700 &&
 | |
| 	git ls-remote bundle > output &&
 | |
| 	! grep tag output
 | |
| '
 | |
| 
 | |
| test_expect_success 'die if bundle file cannot be created' '
 | |
| 	mkdir adir &&
 | |
| 	test_must_fail git bundle create adir --all
 | |
| '
 | |
| 
 | |
| test_expect_failure 'bundle --stdin' '
 | |
| 	echo master | git bundle create stdin-bundle.bdl --stdin &&
 | |
| 	git ls-remote stdin-bundle.bdl >output &&
 | |
| 	grep master output
 | |
| '
 | |
| 
 | |
| test_expect_failure 'bundle --stdin <rev-list options>' '
 | |
| 	echo master | git bundle create hybrid-bundle.bdl --stdin tag &&
 | |
| 	git ls-remote hybrid-bundle.bdl >output &&
 | |
| 	grep master output
 | |
| '
 | |
| 
 | |
| test_expect_success 'empty bundle file is rejected' '
 | |
| 	: >empty-bundle &&
 | |
| 	test_must_fail git fetch empty-bundle
 | |
| '
 | |
| 
 | |
| # This triggers a bug in older versions where the resulting line (with
 | |
| # --pretty=oneline) was longer than a 1024-char buffer.
 | |
| test_expect_success 'ridiculously long subject in boundary' '
 | |
| 	: >file4 &&
 | |
| 	test_tick &&
 | |
| 	git add file4 &&
 | |
| 	printf "%01200d\n" 0 | git commit -F - &&
 | |
| 	test_commit fifth &&
 | |
| 	git bundle create long-subject-bundle.bdl HEAD^..HEAD &&
 | |
| 	git bundle list-heads long-subject-bundle.bdl >heads &&
 | |
| 	test -s heads &&
 | |
| 	git fetch long-subject-bundle.bdl &&
 | |
| 	sed -n "/^-/{p;q;}" long-subject-bundle.bdl >boundary &&
 | |
| 	grep "^-[0-9a-f]\\{40\\} " boundary
 | |
| '
 | |
| 
 | |
| test_expect_success 'prerequisites with an empty commit message' '
 | |
| 	: >file1 &&
 | |
| 	git add file1 &&
 | |
| 	test_tick &&
 | |
| 	git commit --allow-empty-message -m "" &&
 | |
| 	test_commit file2 &&
 | |
| 	git bundle create bundle HEAD^.. &&
 | |
| 	git bundle verify bundle
 | |
| '
 | |
| 
 | |
| test_done
 |