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.
This commit is contained in:
Darren Tucker 2021-04-08 13:31:08 +10:00
parent 80032102d0
commit 19e5344627
2 changed files with 4 additions and 0 deletions

3
.github/configs vendored
View File

@ -84,6 +84,9 @@ case "$config" in
valgrind-4) valgrind-4)
LTESTS="${tests4}" LTESTS="${tests4}"
;; ;;
valgrind-unit)
TEST_TARGET="unit USE_VALGRIND=1"
;;
esac esac
;; ;;
*) *)

View File

@ -22,6 +22,7 @@ jobs:
- { os: ubuntu-20.04, configs: valgrind-2 } - { os: ubuntu-20.04, configs: valgrind-2 }
- { os: ubuntu-20.04, configs: valgrind-3 } - { os: ubuntu-20.04, configs: valgrind-3 }
- { os: ubuntu-20.04, configs: valgrind-4 } - { 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: pam }
- { os: ubuntu-20.04, configs: kitchensink } - { os: ubuntu-20.04, configs: kitchensink }
- { os: ubuntu-20.04, configs: hardenedmalloc } - { os: ubuntu-20.04, configs: hardenedmalloc }