From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v3,1/5] emulator: Generate PA Sync Lost
Date: Fri, 07 Nov 2025 14:07:40 -0800 (PST) [thread overview]
Message-ID: <690e6dac.170a0220.9cfaa.0d4a@mx.google.com> (raw)
In-Reply-To: <20251107201827.1235953-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1753 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/project/bluetooth/list/?series=1021075
---Test result---
Test Summary:
CheckPatch PENDING 0.36 seconds
GitLint PENDING 0.39 seconds
BuildEll PASS 17.98 seconds
BluezMake PASS 4072.92 seconds
MakeCheck PASS 19.82 seconds
MakeDistcheck PASS 172.58 seconds
CheckValgrind PASS 231.19 seconds
CheckSmatch WARNING 275.80 seconds
bluezmakeextell PASS 121.99 seconds
IncrementalBuild PENDING 0.37 seconds
ScanBuild PASS 833.82 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
emulator/btdev.c:461:29: warning: Variable length array is used.emulator/bthost.c:699:28: warning: Variable length array is used.emulator/bthost.c:700:32: warning: Variable length array is used.emulator/bthost.c:917:28: warning: Variable length array is used.emulator/bthost.c:951:28: warning: Variable length array is used.emulator/bthost.c:952:32: warning: Variable length array is used.
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-11-07 22:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 20:18 [PATCH BlueZ v3 1/5] emulator: Generate PA Sync Lost Luiz Augusto von Dentz
2025-11-07 20:18 ` [PATCH BlueZ v3 2/5] bthost: Add support for terminating a BIG Luiz Augusto von Dentz
2025-11-07 20:18 ` [PATCH BlueZ v3 3/5] iso-tester: Add tests for checking proper handling of Sync Lost Luiz Augusto von Dentz
2025-11-07 20:18 ` [PATCH BlueZ v3 4/5] bass: Fix not cleaning up delegator properly Luiz Augusto von Dentz
2025-11-07 20:18 ` [PATCH BlueZ v3 5/5] btio: Fix endless loop if accept return -EBADFD Luiz Augusto von Dentz
2025-11-07 22:07 ` bluez.test.bot [this message]
2025-11-10 20:20 ` [PATCH BlueZ v3 1/5] emulator: Generate PA Sync Lost 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=690e6dac.170a0220.9cfaa.0d4a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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 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.