glcpp-test: don't return failure if valgrind tests aren't run
authorMatt Turner <mattst88@gmail.com>
Sun, 29 Jan 2012 03:08:39 +0000 (22:08 -0500)
committerMatt Turner <mattst88@gmail.com>
Tue, 31 Jan 2012 02:09:57 +0000 (21:09 -0500)
commit82060adcde88eb57cc0a3b71d23f003f5637986f
treebaa625d053989eaa0aa86bcea48246b2abfeb96e
parent9947656168d09f9019600fccc42ca8e0de49b83a
glcpp-test: don't return failure if valgrind tests aren't run

Success was (tests-passed AND valgrind-tests-passed) but this meant that
if the valgrind tests weren't run it would be considered a failure.

The logic is now (tests-passed AND (!valgrind OR valgrind-tests-passed))
which lets us return success if the valgrind tests aren't run.

Reviewed-by: Eric Anholt <eric@anholt.net>
Tested-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Matt Turner <mattst88@gmail.com>
src/glsl/glcpp/tests/glcpp-test