From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [1/2] Bluetooth: L2CAP: avoid maybe-return-locked and add locking annotations
Date: Sun, 12 Jul 2026 07:41:36 -0700 (PDT) [thread overview]
Message-ID: <6a53a7a0.dab7d853.28539d.7fe6@mx.google.com> (raw)
In-Reply-To: <9a718ecfbeb46077d8100dcb687e1ab6073986f6.1783860121.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 3341 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=1126083
---Test result---
Test Summary:
CheckPatch PASS 1.84 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.13 seconds
GitLint FAIL 0.67 seconds
SubjectPrefix PASS 0.26 seconds
BuildKernel PASS 25.93 seconds
CheckAllWarning PASS 28.09 seconds
CheckSparse PASS 26.96 seconds
BuildKernel32 PASS 25.12 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 464.52 seconds
TestRunner_l2cap-tester FAIL 59.28 seconds
TestRunner_iso-tester PASS 85.82 seconds
TestRunner_bnep-tester PASS 19.07 seconds
TestRunner_mgmt-tester FAIL 213.90 seconds
TestRunner_rfcomm-tester PASS 26.06 seconds
TestRunner_sco-tester PASS 32.35 seconds
TestRunner_ioctl-tester PASS 26.44 seconds
TestRunner_mesh-tester FAIL 26.05 seconds
TestRunner_smp-tester PASS 23.08 seconds
TestRunner_userchan-tester PASS 19.71 seconds
TestRunner_6lowpan-tester PASS 22.91 seconds
IncrementalBuild PASS 25.30 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[1/2] Bluetooth: L2CAP: avoid maybe-return-locked and add locking annotations
16: B2 Line has trailing whitespace: " "
20: B2 Line has trailing whitespace: " "
21: B1 Line exceeds max length (154>80): " net/bluetooth/smp.c:589:2: warning: calling function 'l2cap_chan_send' requires holding mutex 'conn->smp->lock' exclusively [-Wthread-safety-analysis]"
25: B1 Line exceeds max length (153>80): " net/bluetooth/6lowpan.c:455:8: warning: calling function 'l2cap_chan_send' requires holding mutex 'chan->lock' exclusively [-Wthread-safety-analysis]"
28: B2 Line has trailing whitespace: " "
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Total: 96, Passed: 95 (99.0%), Failed: 1, Not Run: 0
Failed Test Cases
L2CAP BR/EDR Server - Set PHY 2M Failed 0.252 seconds
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.244 seconds
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 2.622 seconds
Mesh - Send cancel - 2 Timed out 1.989 seconds
https://github.com/bluez/bluetooth-next/pull/426
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-07-12 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 12:42 [PATCH 1/2] Bluetooth: L2CAP: avoid maybe-return-locked and add locking annotations Pauli Virtanen
2026-07-12 12:42 ` [PATCH 2/2] Bluetooth: enable context analysis for headers Pauli Virtanen
2026-07-13 17:16 ` Bart Van Assche
2026-07-12 14:41 ` bluez.test.bot [this message]
2026-07-13 17:15 ` [PATCH 1/2] Bluetooth: L2CAP: avoid maybe-return-locked and add locking annotations Bart Van Assche
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=6a53a7a0.dab7d853.28539d.7fe6@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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