From: Pauli Virtanen <pav@iki.fi>
To: linux-bluetooth@vger.kernel.org
Cc: Pauli Virtanen <pav@iki.fi>
Subject: [PATCH BlueZ 0/5] mgmt-tester: fix test failures + avoid hidden skipping
Date: Sun, 20 Sep 2026 23:35:08 +0300 [thread overview]
Message-ID: <cover.1789934710.git.pav@iki.fi> (raw)
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
These fail because:
- Invalid Parameters: change in MGMT semantics in 2024, test wasn't
updated
- Pair Device - Power off 1: race between MGMT and ioctl, let's just
ignore, it is not deterministic
- Read Exp Feature - Success: simple test issue vs. Debug extension
Fix these, and make it reports failures correctly.
Adjust the test machinery reporting of setup failures, to avoid some
additional paths to "Not Run" reporting.
LLM used for triage + fixing issues, except where it needed manual
cleanup for simpler solution. I reviewed all commits.
Assisted-by: opencode:qwen3.8-next-flash
Pauli Virtanen (5):
mgmt-tester: ignore Debug feature in Read Exp Feature tests
mgmt-tester: Fix expected status for invalid key entries
mgmt-tester: mark Pair Device - Power off 1 as fail_tolerant
mgmt-tester: Report unexpected status as test failure
shared/tester: Count setup failures as test failures
src/shared/tester.c | 3 +
test/functional/test_kernel_testers.py | 2 -
tools/mgmt-tester.c | 137 ++++++++++++++++++++-----
3 files changed, 115 insertions(+), 27 deletions(-)
--
2.55.0
next reply other threads:[~2026-09-20 20:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 20:35 Pauli Virtanen [this message]
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 ` [PATCH BlueZ 0/5] mgmt-tester: fix test failures + avoid hidden skipping 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=cover.1789934710.git.pav@iki.fi \
--to=pav@iki.fi \
--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 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.