From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, lidaoxun25@mails.ucas.ac.cn
Subject: RE: [RFC,bluetooth-next] Bluetooth: hci_event: Use General Bonding for ATS2851
Date: Thu, 10 Sep 2026 12:04:04 -0700 (PDT) [thread overview]
Message-ID: <6aa2ff24.8f0cbdd2.15d40d.b644@mx.google.com> (raw)
In-Reply-To: <20260820140547.1148128-1-lidaoxun25@mails.ucas.ac.cn>
[-- Attachment #1: Type: text/plain, Size: 2436 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/1149156/
---Test result---
Test Summary:
CheckPatch PASS 0.95 seconds
VerifyFixes PASS 0.05 seconds
VerifySignedoff PASS 0.05 seconds
GitLint PASS 0.19 seconds
SubjectPrefix PASS 0.05 seconds
BuildKernel PASS 29.31 seconds
CheckAllWarning PASS 33.12 seconds
CheckSparse WARNING 35.81 seconds
BuildKernel32 PASS 28.48 seconds
CheckKernelLLVM PASS 34.06 seconds
TestRunnerSetup PASS 768.63 seconds
TestRunner_l2cap-tester PASS 43.81 seconds
TestRunner_iso-tester PASS 90.08 seconds
TestRunner_bnep-tester PASS 13.12 seconds
TestRunner_mgmt-tester FAIL 146.72 seconds
TestRunner_rfcomm-tester PASS 16.81 seconds
TestRunner_sco-tester PASS 22.33 seconds
TestRunner_ioctl-tester PASS 17.92 seconds
TestRunner_mesh-tester FAIL 18.73 seconds
TestRunner_smp-tester PASS 15.48 seconds
TestRunner_userchan-tester PASS 13.10 seconds
TestRunner_6lowpan-tester PASS 16.01 seconds
IncrementalBuild PASS 27.04 seconds
Details
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 501, Passed: 496 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.148 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.385 seconds
Mesh - Send cancel - 2 Timed out 1.998 seconds
https://github.com/bluez/bluetooth-next/pull/738
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-10 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 14:05 [RFC PATCH bluetooth-next] Bluetooth: hci_event: Use General Bonding for ATS2851 Li Daoxun
2026-08-20 15:15 ` [RFC,bluetooth-next] " bluez.test.bot
2026-09-10 19:04 ` bluez.test.bot [this message]
2026-09-10 19:58 ` [RFC PATCH bluetooth-next] " Luiz Augusto von Dentz
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=6aa2ff24.8f0cbdd2.15d40d.b644@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=lidaoxun25@mails.ucas.ac.cn \
--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 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.