From: patchwork-bot+bluetooth@kernel.org
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [BlueZ PATCH v1 0/3] Unit tests speed-up
Date: Fri, 09 Jan 2026 22:40:06 +0000 [thread overview]
Message-ID: <176799840679.418288.11899668269970851996.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260109093602.1224918-1-hadess@hadess.net>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 9 Jan 2026 10:28:59 +0100 you wrote:
> With those small changes, as well as running tests concurrently using
> meson, I was able to make the whole test suite run in less than 4
> seconds on my desktop system, with a baseline of 50 seconds for "make
> -j8 check" under the autotools.
>
> make -j8 check: 50 seconds
> meson before changes: 13 seconds
> meson after changes: 3.6 seconds
>
> [...]
Here is the summary with links:
- [BlueZ,v1,1/3] unit: Speed up unit-avdtp test
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=51d93aca7afa
- [BlueZ,v1,2/3] unit: Speed up unit-gobex-transfer test
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=027e29c34225
- [BlueZ,v1,3/3] unit: Speed up unit-ringbuf test
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=00e5c016145a
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-01-09 22:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 9:28 [BlueZ PATCH v1 0/3] Unit tests speed-up Bastien Nocera
2026-01-09 9:29 ` [BlueZ PATCH v1 1/3] unit: Speed up unit-avdtp test Bastien Nocera
2026-01-09 10:26 ` Unit tests speed-up bluez.test.bot
2026-01-09 12:13 ` Bastien Nocera
2026-01-09 9:29 ` [BlueZ PATCH v1 2/3] unit: Speed up unit-gobex-transfer test Bastien Nocera
2026-01-09 9:29 ` [BlueZ PATCH v1 3/3] unit: Speed up unit-ringbuf test Bastien Nocera
2026-01-09 22:40 ` 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=176799840679.418288.11899668269970851996.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=hadess@hadess.net \
--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