From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, khidarlaminehamdi@gmail.com
Subject: RE: Don't probe LE Audio profiles on unpaired devices
Date: Wed, 18 Nov 2026 12:06:56 -0800 (PST) [thread overview]
Message-ID: <6afe0560.1caeda21.38a6e9.21fa@mx.google.com> (raw)
In-Reply-To: <20261118141438.308232-2-khidarlaminehamdi@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/series/1215085/
---Test result---
Test Summary:
CheckPatch PASS 0.97 seconds
GitLint PASS 0.65 seconds
BuildEll PASS 17.87 seconds
BluezMake PASS 265.62 seconds
MakeCheck PASS 3.56 seconds
MakeDistcheck PASS 136.21 seconds
CheckValgrind PASS 144.07 seconds
CheckSmatch PASS 245.57 seconds
bluezmakeextell PASS 90.92 seconds
TestFunctional FAIL 1168.70 seconds
IncrementalBuild PASS 276.67 seconds
ScanBuild PASS 959.21 seconds
Details
##############################
Test: TestFunctional - FAIL
Desc: Run test-functional
Output:
FAIL functional.test_bap::test_bass_past_earbuds_transport_acquire[hosts11-vm3]: AssertionError: Failed to acquire: org.bluez.Error.Failed
https://github.com/bluez/bluez/pull/2845
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-11-18 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 14:14 [PATCH BlueZ 0/2] Don't probe LE Audio profiles on unpaired devices AuthenticSm1les
2026-11-18 14:14 ` [PATCH BlueZ 1/2] profile: Add paired_only flag AuthenticSm1les
2026-11-18 15:04 ` Luiz Augusto von Dentz
2026-11-18 20:06 ` bluez.test.bot [this message]
2026-11-18 14:14 ` [PATCH BlueZ 2/2] audio: Mark LE Audio client profiles paired_only AuthenticSm1les
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=6afe0560.1caeda21.38a6e9.21fa@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=khidarlaminehamdi@gmail.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