aboutsummaryrefslogtreecommitdiff
path: root/libflash
diff options
context:
space:
mode:
authorOliver O'Halloran <oohall@gmail.com>2020-06-12 12:24:49 +1000
committerOliver O'Halloran <oohall@gmail.com>2020-06-17 21:18:45 +1000
commit028442e6573eabbc2ebc6499f92fcf5ace856553 (patch)
tree00342fd86d7d2be71d343e5b6d468aa15473e844 /libflash
parent09b4be2c46214746149f9f11f235a3ae0c6b16cc (diff)
downloadskiboot-028442e6573eabbc2ebc6499f92fcf5ace856553.zip
skiboot-028442e6573eabbc2ebc6499f92fcf5ace856553.tar.gz
skiboot-028442e6573eabbc2ebc6499f92fcf5ace856553.tar.bz2
test: Do gcov builds as a seperate pass
We only really use the gcov output when doing the coverage report as a part of the "docs" CI builds. It's useful for development to just run the unit tests so make sure the "check" and "coverage" targets are seperate. This also speeds up our CI builds since those jobs are already doing a seperate GCOV pass so building and running the GCOV binaries during the check pass is redundant. Signed-off-by: Oliver O'Halloran <oohall@gmail.com>
Diffstat (limited to 'libflash')
-rw-r--r--libflash/test/Makefile.check2
1 files changed, 1 insertions, 1 deletions
diff --git a/libflash/test/Makefile.check b/libflash/test/Makefile.check
index 1e55237..4dbd7ee 100644
--- a/libflash/test/Makefile.check
+++ b/libflash/test/Makefile.check
@@ -33,7 +33,7 @@ check_PROGRAMS = \
TEST_FLAGS = -D__TEST__ -MMD -MP
.PHONY: libflash-check libflash-coverage
-libflash-check: $(check_PROGRAMS:%=%-check) $(CORE_TEST:%=%-gcov-run)
+libflash-check: $(check_PROGRAMS:%=%-check)
libflash-coverage: $(check_PROGRAMS:%=%-gcov-run)
clean: libflash-test-clean
check: libflash-check