ntdb: catch any valgrind errors in test
authorRusty Russell <rusty@rustcorp.com.au>
Mon, 18 Jun 2012 13:00:27 +0000 (22:30 +0930)
committerRusty Russell <rusty@rustcorp.com.au>
Tue, 19 Jun 2012 03:38:06 +0000 (05:38 +0200)
We need --error-exitcode=, otherwise valgrind errors don't cause the
test to fail.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
lib/ntdb/wscript

index e6feb14f12522736424816fb81af7f98a2694a6b..aab42456c5e76076000484682fa01fe85d7b645c 100644 (file)
@@ -231,7 +231,7 @@ def testonly(ctx):
             os.symlink(os.path.abspath(os.path.join(env.cwd, 'test')), link)
 
         if Options.options.VALGRIND:
-            os.environ['VALGRIND'] = 'valgrind -q --num-callers=30'
+            os.environ['VALGRIND'] = 'valgrind -q --num-callers=30 --error-exitcode=11'
         if Options.options.VALGRINDLOG is not None:
             os.environ['VALGRIND'] += ' --log-file=%s' % Options.options.VALGRINDLOG