b2ddccd90d
The printf(1) command, like it's C cousin, takes a format string as its first argument. If a shell variable is passed as the first argument, it will be interpreted as a format string; this can lead to surprising behavior and can cause the test suite to fail if we accidentally insert a format string character into the variable. Modify all the places in the individual tests that we use a plain quoted variable as the format string by running the following Ruby one-liner: ruby -i -pe '$_.gsub!(/printf "\$/, %q(printf "%s" "$))' t/t-*.sh Avoid modifying the test helpers, as there are places (such as calc_oid) where we want to pass text containing escapes (such as "\n") and have those be properly interpreted by printf(1).
30 lines
573 B
Bash
Executable File
30 lines
573 B
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
. "$(dirname "$0")/testlib.sh"
|
|
|
|
begin_test "progress meter displays positive progress"
|
|
(
|
|
set -e
|
|
|
|
reponame="progress-meter"
|
|
setup_remote_repo "$reponame"
|
|
clone_repo "$reponame" "$reponame"
|
|
|
|
git lfs track "*.dat"
|
|
git add .gitattributes
|
|
git commit -m "initial commit"
|
|
|
|
for i in `seq 1 128`; do
|
|
printf "%s" "$i" > "$i.dat"
|
|
done
|
|
|
|
git add *.dat
|
|
git commit -m "add many objects"
|
|
|
|
git push origin master 2>&1 | tee push.log
|
|
[ "0" -eq "${PIPESTATUS[0]}" ]
|
|
|
|
grep "Uploading LFS objects: 100% (128/128), 276 B" push.log
|
|
)
|
|
end_test
|