From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zzzccc427@gmail.com
Subject: RE: Bluetooth: 6lowpan: hold L2CAP conn across debugfs control
Date: Tue, 23 Jun 2026 10:58:32 -0700 (PDT) [thread overview]
Message-ID: <6a3ac948.87f7828a.1cf5fe.7d21@mx.google.com> (raw)
In-Reply-To: <20260623161259.2175870-1-zzzccc427@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1557 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=1115490
---Test result---
Test Summary:
CheckPatch PASS 1.39 seconds
VerifyFixes PASS 0.23 seconds
VerifySignedoff PASS 0.24 seconds
GitLint PASS 0.56 seconds
SubjectPrefix PASS 0.26 seconds
BuildKernel PASS 27.06 seconds
CheckAllWarning PASS 30.15 seconds
CheckSparse PASS 28.73 seconds
BuildKernel32 PASS 26.22 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 578.67 seconds
TestRunner_l2cap-tester FAIL 59.26 seconds
TestRunner_6lowpan-tester PASS 22.98 seconds
IncrementalBuild PASS 26.09 seconds
Details
##############################
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.253 seconds
https://github.com/bluez/bluetooth-next/pull/341
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-06-23 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 16:12 [PATCH] Bluetooth: 6lowpan: hold L2CAP conn across debugfs control Cen Zhang
2026-06-23 17:58 ` bluez.test.bot [this message]
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=6a3ac948.87f7828a.1cf5fe.7d21@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=zzzccc427@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox