From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zzzccc427@gmail.com
Subject: RE: [v2] Bluetooth: hci_debugfs: serialize force_bredr_smp writes
Date: Fri, 03 Jul 2026 03:10:47 -0700 (PDT) [thread overview]
Message-ID: <6a478aa7.99af2db9.114264.42e7@mx.google.com> (raw)
In-Reply-To: <20260703081431.922054-1-zzzccc427@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2737 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=1120995
---Test result---
Test Summary:
CheckPatch PASS 0.77 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.13 seconds
GitLint PASS 0.32 seconds
SubjectPrefix PASS 0.12 seconds
BuildKernel PASS 26.35 seconds
CheckAllWarning PASS 29.85 seconds
CheckSparse PASS 28.57 seconds
BuildKernel32 PASS 25.65 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 494.82 seconds
TestRunner_l2cap-tester FAIL 58.69 seconds
TestRunner_iso-tester PASS 82.99 seconds
TestRunner_bnep-tester PASS 18.60 seconds
TestRunner_mgmt-tester FAIL 210.72 seconds
TestRunner_rfcomm-tester PASS 24.85 seconds
TestRunner_sco-tester PASS 31.78 seconds
TestRunner_ioctl-tester PASS 26.08 seconds
TestRunner_mesh-tester FAIL 30.43 seconds
TestRunner_smp-tester PASS 23.14 seconds
TestRunner_userchan-tester PASS 19.72 seconds
TestRunner_6lowpan-tester PASS 22.52 seconds
IncrementalBuild PASS 24.93 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: 94 (97.9%), Failed: 2, Not Run: 0
Failed Test Cases
L2CAP BR/EDR Server - Set PHY 1M Failed 0.258 seconds
L2CAP BR/EDR Server - Set PHY 3M Failed 0.253 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.242 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.748 seconds
Mesh - Send cancel - 2 Timed out 1.990 seconds
https://github.com/bluez/bluetooth-next/pull/391
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-07-03 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 8:14 [PATCH v2] Bluetooth: hci_debugfs: serialize force_bredr_smp writes Cen Zhang
2026-07-03 10:10 ` 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=6a478aa7.99af2db9.114264.42e7@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