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).
37 lines
706 B
Bash
Executable File
37 lines
706 B
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
. "$(dirname "$0")/testlib.sh"
|
|
|
|
begin_test "transfer queue rejects unknown OIDs"
|
|
(
|
|
set -e
|
|
|
|
reponame="unknown-oids"
|
|
setup_remote_repo "$reponame"
|
|
clone_repo "$reponame" "$reponame"
|
|
|
|
git lfs track "*.dat"
|
|
git add .gitattributes
|
|
git commit -m "initial commit"
|
|
|
|
contents="unknown-oid"
|
|
printf "%s" "$contents" > a.dat
|
|
|
|
git add a.dat
|
|
git commit -m "add objects"
|
|
|
|
set +e
|
|
git push origin master 2>&1 | tee push.log
|
|
res="${PIPESTATUS[0]}"
|
|
set -e
|
|
|
|
refute_server_object "$reponame" "$(calc_oid "$contents")"
|
|
if [ "0" -eq "$res" ]; then
|
|
echo "push successful?"
|
|
exit 1
|
|
fi
|
|
|
|
grep "\[unknown-oid\] The server returned an unknown OID." push.log
|
|
)
|
|
end_test
|