From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ v1 1/2] build: Fix coverage target failing with stale .gcda files
Date: Mon, 28 Sep 2026 16:47:30 -0400 [thread overview]
Message-ID: <20260928204732.1265535-1-luiz.dentz@gmail.com> (raw)
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Coverage data from a previous build is not overwritten by 'make check'
for binaries that are not run by it, causing geninfo to fail with a
stamp mismatch once the objects are rebuilt. Zero the counters before
running the tests and mark the targets as phony since coverage/ is also
the output directory.
Assisted-by: Claude:claude-opus-5.5
---
Makefile.am | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/Makefile.am b/Makefile.am
index 53a3a15c3f8b..24760ab08687 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -999,7 +999,11 @@ if COVERAGE
@lcov --directory $(top_builddir) --zerocounters
$(RM) -r coverage $(top_builddir)/coverage.info
-coverage: check
+.PHONY: coverage clean-coverage
+
+coverage:
+ @lcov --directory $(top_builddir) --zerocounters
+ $(AM_V_at)$(MAKE) $(AM_MAKEFLAGS) check
@lcov --compat-libtool --directory $(top_builddir) --capture \
--output-file $(top_builddir)/coverage.info
$(AM_V_at)$(MKDIR_P) coverage
--
2.55.0
next reply other threads:[~2026-09-28 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 20:47 Luiz Augusto von Dentz [this message]
2026-09-28 20:47 ` [PATCH BlueZ v1 2/2] test-runner: Share build directory writable on coverage builds Luiz Augusto von Dentz
2026-09-28 22:37 ` [BlueZ,v1,1/2] build: Fix coverage target failing with stale .gcda files bluez.test.bot
2026-09-29 15:20 ` [PATCH BlueZ v1 1/2] " patchwork-bot+bluetooth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260928204732.1265535-1-luiz.dentz@gmail.com \
--to=luiz.dentz@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox