test: do run the util tests under valgrind
authorPeter Hutterer <peter.hutterer@who-t.net>
Fri, 6 Sep 2019 00:31:49 +0000 (10:31 +1000)
committerPeter Hutterer <peter.hutterer@who-t.net>
Wed, 11 Sep 2019 02:21:44 +0000 (12:21 +1000)
These tests include string parsers, definitely want those to run under
valgrind to detect OOB reads and writes.

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
test/test-utils.c

index 0cde5aa53f387fcd4849308d9d638ef62f9de5de..9f13f2e512ce42f2be8a6e9047c94f1b91bde928 100644 (file)
@@ -1068,12 +1068,6 @@ int main(int argc, char **argv)
        Suite *s;
        SRunner *sr;
 
-        /* when running under valgrind we're using nofork mode, so a signal
-         * raised by a test will fail in valgrind. There's nothing to
-         * memcheck here anyway, so just skip the valgrind test */
-        if (RUNNING_ON_VALGRIND)
-            return 77;
-
        s = litest_utils_suite();
         sr = srunner_create(s);