74d2f5695d
The top-level &&-chain checker built into t/test-lib.sh causes tests to
magically exit with code 117 if the &&-chain is broken. However, it has
the shortcoming that the magic does not work within `{...}` groups,
`(...)` subshells, `$(...)` substitutions, or within bodies of compound
statements, such as `if`, `for`, `while`, `case`, etc. `chainlint.sed`
partly fills in the gap by catching broken &&-chains in `(...)`
subshells, but bugs can still lurk behind broken &&-chains in the other
cases.
Fix broken &&-chains in compound statements in order to reduce the
number of possible lurking bugs.
Signed-off-by: Eric Sunshine <sunshine@sunshineco.com>
Reviewed-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
30 lines
579 B
Bash
Executable File
30 lines
579 B
Bash
Executable File
#!/bin/sh
|
|
|
|
test_description="Tests performance of writing the index"
|
|
|
|
. ./perf-lib.sh
|
|
|
|
test_perf_default_repo
|
|
|
|
test_expect_success "setup repo" '
|
|
if git rev-parse --verify refs/heads/p0006-ballast^{commit}
|
|
then
|
|
echo Assuming synthetic repo from many-files.sh &&
|
|
git config --local core.sparsecheckout 1 &&
|
|
cat >.git/info/sparse-checkout <<-EOF
|
|
/*
|
|
!ballast/*
|
|
EOF
|
|
else
|
|
echo Assuming non-synthetic repo...
|
|
fi &&
|
|
nr_files=$(git ls-files | wc -l)
|
|
'
|
|
|
|
count=3
|
|
test_perf "write_locked_index $count times ($nr_files files)" "
|
|
test-tool write-cache $count
|
|
"
|
|
|
|
test_done
|