From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pvbozhko@salutedevices.com
Subject: RE: audio/avrcp: Add AvrcpVersion config option
Date: Wed, 23 Sep 2026 03:47:49 -0700 (PDT) [thread overview]
Message-ID: <6ab3ae55.2fe18630.18fe47.04b5@mx.google.com> (raw)
In-Reply-To: <20260923091827.4496-2-pvbozhko@salutedevices.com>
[-- Attachment #1: Type: text/plain, Size: 1410 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/1172081/
---Test result---
Test Summary:
CheckPatch PASS 0.44 seconds
GitLint PASS 0.29 seconds
BuildEll PASS 14.88 seconds
BluezMake PASS 262.58 seconds
MakeCheck PASS 2.86 seconds
MakeDistcheck PASS 112.36 seconds
CheckValgrind PASS 117.33 seconds
CheckSmatch WARNING 191.58 seconds
bluezmakeextell PASS 71.86 seconds
TestFunctional FAIL 903.64 seconds
IncrementalBuild PASS 259.41 seconds
ScanBuild PASS 760.61 seconds
Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
src/main.c: note: in included file (through src/device.h):
##############################
Test: TestFunctional - FAIL
Desc: Run test-functional
Output:
FAIL functional.test_bap::test_bass_past_transport_acquire[hosts8-vm2]: AssertionError: Failed to acquire: org.bluez.Error.Failed
https://github.com/bluez/bluez/pull/2571
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-23 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 9:18 [PATCH BlueZ v2 0/1] audio/avrcp: Add AvrcpVersion config option Pavel Bozhko
2026-09-23 9:18 ` [PATCH BlueZ v2 1/1] " Pavel Bozhko
2026-09-23 10:47 ` bluez.test.bot [this message]
2026-10-08 16:54 ` bluez.test.bot
-- strict thread matches above, loose matches on Subject: below --
2026-09-22 15:00 [PATCH BlueZ 1/1] " Pavel Bozhko
2026-09-22 16:34 ` bluez.test.bot
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=6ab3ae55.2fe18630.18fe47.04b5@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pvbozhko@salutedevices.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox