From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v1 1/2] build: Fix coverage target failing with stale .gcda files
Date: Tue, 29 Sep 2026 15:20:16 +0000 [thread overview]
Message-ID: <179069521602.987606.1397475380776965493.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260928204732.1265535-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 28 Sep 2026 16:47:30 -0400 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [BlueZ,v1,1/2] build: Fix coverage target failing with stale .gcda files
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8814ac26fe65
- [BlueZ,v1,2/2] test-runner: Share build directory writable on coverage builds
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=86713777f91a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-29 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 20:47 [PATCH BlueZ v1 1/2] build: Fix coverage target failing with stale .gcda files Luiz Augusto von Dentz
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 ` patchwork-bot+bluetooth [this message]
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=179069521602.987606.1397475380776965493.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.