Guard setup with test_expect_success Signed-off-by: Tom Grennan <tmgrennan@xxxxxxxxx> --- t/t5512-ls-remote.sh | 10 ++++++---- 1 files changed, 6 insertions(+), 4 deletions(-) diff --git a/t/t5512-ls-remote.sh b/t/t5512-ls-remote.sh index 5c546c9..811dcc3 100755 --- a/t/t5512-ls-remote.sh +++ b/t/t5512-ls-remote.sh @@ -102,11 +102,13 @@ test_expect_success 'use branch.<name>.remote if possible' ' ' -cat >exp <<EOF -fatal: 'refs*master' does not appear to be a git repository -fatal: The remote end hung up unexpectedly -EOF test_expect_success 'confuses pattern as remote when no remote specified' ' + '" + cat >exp <<-EOF + fatal: 'refs*master' does not appear to be a git repository + fatal: The remote end hung up unexpectedly + EOF + "' # # Do not expect "git ls-remote <pattern>" to work; ls-remote, correctly, # confuses <pattern> for <remote>. Although ugly, this behaviour is akin -- 1.7.8 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html