Fix a bug in dc extended register command tests
The bug was that the test failed under Valgrind because it saw `gxpR` as the command. Signed-off-by: Gavin D. Howard <[email protected]>
This commit is contained in:
parent
1f2ab5e46e
commit
37e3d2ad7e
|
@ -308,14 +308,14 @@ else
|
|||
|
||||
printf '0\n' > "$ext_reg_res"
|
||||
|
||||
"$exe" -e "gxpR" "$@" 2> /dev/null > "$ext_reg_out"
|
||||
"$exe" "$@" -e "gxpR" 2> /dev/null > "$ext_reg_out"
|
||||
err="$?"
|
||||
|
||||
checktest "$d" "$err" "Extended register command" "$ext_reg_out" "$ext_reg_res"
|
||||
|
||||
printf '1\n' > "$ext_reg_res"
|
||||
|
||||
"$exe" -x -e "gxpR" "$@" 2> /dev/null > "$ext_reg_out"
|
||||
"$exe" "$@" -x -e "gxpR" 2> /dev/null > "$ext_reg_out"
|
||||
err="$?"
|
||||
|
||||
checktest "$d" "$err" "Extended register command" "$ext_reg_out" "$ext_reg_res"
|
||||
|
|
Loadingâ¦
Reference in New Issue