Run unit tests under valgrind.

Run a separate build for the unit tests under Valgrind.  They take long
enough that running in parallel with the other Valgrind tests helps.

diff --git a/.github/configs b/.github/configs
index 87c7a6dc213a2ddb84e6c422840abf420fc6cefb..62dbe879511031bf1ef7bc27288d7762a6746e25 100755 (executable)
--- a/.github/configs
+++ b/.github/configs
@@ -84,6 +84,9 @@ case "$config" in
            valgrind-4)
                LTESTS="${tests4}"
                ;;
+           valgrind-unit)
+               TEST_TARGET="unit USE_VALGRIND=1"
+               ;;
        esac
        ;;
     *)

diff --git a/.github/workflows/c-cpp.yml b/.github/workflows/c-cpp.yml
index a712af7c2189f0e91d57a066c18bbcd7ae2e7b38..c4ae28434305a1f4fcd9109f15723298cb1df53a 100644 (file)
--- a/.github/workflows/c-cpp.yml
+++ b/.github/workflows/c-cpp.yml
@@ -22,6 +22,7 @@ jobs:
           - { os: ubuntu-20.04, configs: valgrind-2 }
           - { os: ubuntu-20.04, configs: valgrind-3 }
           - { os: ubuntu-20.04, configs: valgrind-4 }
+          - { os: ubuntu-20.04, configs: valgrind-unit }
           - { os: ubuntu-20.04, configs: pam }
           - { os: ubuntu-20.04, configs: kitchensink }
           - { os: ubuntu-20.04, configs: hardenedmalloc }