From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 0d00bd: build: Fix coverage target failing with stale .gcd...
Date: Mon, 28 Sep 2026 14:31:43 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1175582/000000-fe7cbf@github.com> (raw)
Branch: refs/heads/1175582
Home: https://github.com/bluez/bluez
Commit: 0d00bd2195b854115525139ed79f5b502f5b71ac
https://github.com/bluez/bluez/commit/0d00bd2195b854115525139ed79f5b502f5b71ac
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-09-28 (Mon, 28 Sep 2026)
Changed paths:
M Makefile.am
Log Message:
-----------
build: Fix coverage target failing with stale .gcda files
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
Commit: fe7cbf16897aad7458db1f9afab4099ae596e4db
https://github.com/bluez/bluez/commit/fe7cbf16897aad7458db1f9afab4099ae596e4db
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-09-28 (Mon, 28 Sep 2026)
Changed paths:
M Makefile.tools
M tools/test-runner.c
Log Message:
-----------
test-runner: Share build directory writable on coverage builds
The root filesystem is shared read-only with the guest so gcov is not
able to write the .gcda files of binaries run by test-runner, e.g. by
the functional tests. Share the build directory writable over 9p and
mount it over the read-only one when coverage is enabled.
Assisted-by: Claude:claude-opus-5.5
Compare: https://github.com/bluez/bluez/compare/0d00bd2195b8%5E...fe7cbf16897a
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-28 21:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1175582/000000-fe7cbf@github.com \
--to=noreply@github.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