author | Shawn O. Pearce <spearce@spearce.org> | |
Tue, 4 Mar 2008 01:09:31 +0000 (20:09 -0500) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Tue, 4 Mar 2008 02:26:23 +0000 (18:26 -0800) | ||
commit | be7bae0d4821462c50c5b82633edb372fe971e9e | |
tree | 6c229a44fb2c4646e70c6c529ea0de12bb1f3f59 | tree | snapshot |
parent | 3167d7256505cdeace5293bc67f0d16657a9277e | commit | diff |
Don't allow git-describe failures to go unnoticed in t6120
If git-describe fails we never execute the test_expect_success,
so we never actually test for failure. This is horribly wrong.
We need to always run the test case, but the test case is only
supposed to succeed if the prior git-describe returned 0.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
If git-describe fails we never execute the test_expect_success,
so we never actually test for failure. This is horribly wrong.
We need to always run the test case, but the test case is only
supposed to succeed if the prior git-describe returned 0.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/t6120-describe.sh | diff | blob | history |