From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 0/5] mgmt-tester: fix test failures + avoid hidden skipping
Date: Mon, 21 Sep 2026 14:30:08 +0000 [thread overview]
Message-ID: <179000100813.3057876.13874076253271965313.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1789934710.git.pav@iki.fi>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 20 Sep 2026 23:35:08 +0300 you wrote:
> MGMT tests have one failure + 4 hidden failures:
>
> Load Link Keys - Invalid Parameters 3 Not Run
> Load Long Term Keys - Invalid Parameters 2 Not Run
> Load Long Term Keys - Invalid Parameters 3 Not Run
> Pair Device - Power off 1 Not Run
> Read Exp Feature - Success Failed
>
> [...]
Here is the summary with links:
- [BlueZ,1/5] mgmt-tester: ignore Debug feature in Read Exp Feature tests
(no matching commit)
- [BlueZ,2/5] mgmt-tester: Fix expected status for invalid key entries
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=216f85e77b92
- [BlueZ,3/5] mgmt-tester: mark Pair Device - Power off 1 as fail_tolerant
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=3450e588533d
- [BlueZ,4/5] mgmt-tester: Report unexpected status as test failure
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=9015ae322846
- [BlueZ,5/5] shared/tester: Count setup failures as test failures
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=86dfa8e3b7b3
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-21 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 20:35 [PATCH BlueZ 0/5] mgmt-tester: fix test failures + avoid hidden skipping Pauli Virtanen
2026-09-20 20:35 ` [PATCH BlueZ 1/5] mgmt-tester: ignore Debug feature in Read Exp Feature tests Pauli Virtanen
2026-09-20 23:02 ` mgmt-tester: fix test failures + avoid hidden skipping bluez.test.bot
2026-10-05 21:56 ` bluez.test.bot
2026-09-20 20:35 ` [PATCH BlueZ 2/5] mgmt-tester: Fix expected status for invalid key entries Pauli Virtanen
2026-09-20 20:35 ` [PATCH BlueZ 3/5] mgmt-tester: mark Pair Device - Power off 1 as fail_tolerant Pauli Virtanen
2026-09-20 20:35 ` [PATCH BlueZ 4/5] mgmt-tester: Report unexpected status as test failure Pauli Virtanen
2026-09-20 20:35 ` [PATCH BlueZ 5/5] shared/tester: Count setup failures as test failures Pauli Virtanen
2026-09-21 14:30 ` 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=179000100813.3057876.13874076253271965313.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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.