From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, enghitalo@gmail.com
Subject: RE: Test links completing after their connection was aborted
Date: Thu, 08 Oct 2026 19:28:36 -0700 (PDT) [thread overview]
Message-ID: <6ac85154.7d74b517.15ed2.14f1@mx.google.com> (raw)
In-Reply-To: <20261008215756.2710812-2-enghitalo@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1444 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/1181897/
---Test result---
Test Summary:
CheckPatch PASS 0.69 seconds
GitLint FAIL 0.43 seconds
BuildEll PASS 19.21 seconds
BluezMake PASS 394.48 seconds
CheckSmatch WARNING 290.89 seconds
bluezmakeextell PASS 92.90 seconds
TestFunctional PASS 1153.65 seconds
IncrementalBuild PASS 385.57 seconds
ScanBuild PASS 1121.13 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,2/2] tools/l2cap-tester: Add tests closing the socket before the link is up
1: T1 Title exceeds max length (82>80): "[BlueZ,2/2] tools/l2cap-tester: Add tests closing the socket before the link is up"
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
tools/sco-tester.c: note: in included file:./lib/bluetooth/bluetooth.h:232:15: warning: array of flexible structures./lib/bluetooth/bluetooth.h:237:31: warning: array of flexible structures
https://github.com/bluez/bluez/pull/2639
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-09 2:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 21:57 [PATCH BlueZ 0/2] Test links completing after their connection was aborted Hitalo Souza
2026-10-08 21:57 ` [PATCH BlueZ 1/2] tools/sco-tester: Add test closing the socket before the link is up Hitalo Souza
2026-10-09 2:28 ` bluez.test.bot [this message]
2026-10-08 21:57 ` [PATCH BlueZ 2/2] tools/l2cap-tester: Add tests " Hitalo Souza
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=6ac85154.7d74b517.15ed2.14f1@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=enghitalo@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