From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, n05ec@lzu.edu.cn
Subject: RE: [1/1] Bluetooth: hci_sync: reject oversized Broadcast Announcement prepend
Date: Fri, 29 May 2026 05:29:00 -0700 (PDT) [thread overview]
Message-ID: <6a19868c.d9dd1dc9.10cdc0.d453@mx.google.com> (raw)
In-Reply-To: <9089784d08f1afd038b4ce0df1fb89904f4879ee.1779634468.git.xuyq21@lenovo.com>
[-- Attachment #1: Type: text/plain, Size: 3369 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=1102742
---Test result---
Test Summary:
CheckPatch FAIL 0.73 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.13 seconds
GitLint PASS 0.33 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 25.45 seconds
CheckAllWarning PASS 28.02 seconds
CheckSparse PASS 26.96 seconds
BuildKernel32 PASS 24.84 seconds
TestRunnerSetup PASS 525.00 seconds
TestRunner_l2cap-tester PASS 58.33 seconds
TestRunner_iso-tester PASS 78.65 seconds
TestRunner_bnep-tester PASS 18.91 seconds
TestRunner_mgmt-tester FAIL 209.39 seconds
TestRunner_rfcomm-tester PASS 25.43 seconds
TestRunner_sco-tester PASS 32.59 seconds
TestRunner_ioctl-tester PASS 25.65 seconds
TestRunner_mesh-tester FAIL 26.60 seconds
TestRunner_smp-tester PASS 23.35 seconds
TestRunner_userchan-tester PASS 19.80 seconds
TestRunner_6lowpan-tester PASS 22.87 seconds
IncrementalBuild PASS 23.48 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[1/1] Bluetooth: hci_sync: reject oversized Broadcast Announcement prepend
WARNING: Reported-by: should be immediately followed by Closes: with a URL to the report
#89:
Reported-by: Yuan Tan <yuantan098@gmail.com>
Reported-by: Zhengchuan Liang <zcliangcn@gmail.com>
WARNING: Reported-by: should be immediately followed by Closes: with a URL to the report
#90:
Reported-by: Zhengchuan Liang <zcliangcn@gmail.com>
Reported-by: Xin Liu <bird@lzu.edu.cn>
WARNING: Reported-by: should be immediately followed by Closes: with a URL to the report
#91:
Reported-by: Xin Liu <bird@lzu.edu.cn>
Assisted-by: Codex:GPT-5.4
total: 0 errors, 3 warnings, 0 checks, 11 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/patch/14600598.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
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.238 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.580 seconds
Mesh - Send cancel - 2 Timed out 1.989 seconds
https://github.com/bluez/bluetooth-next/pull/254
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-05-29 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1779634468.git.xuyq21@lenovo.com>
2026-05-29 8:54 ` [PATCH 1/1] Bluetooth: hci_sync: reject oversized Broadcast Announcement prepend Ren Wei
2026-05-29 12:29 ` bluez.test.bot [this message]
2026-05-29 15:50 ` patchwork-bot+bluetooth
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=6a19868c.d9dd1dc9.10cdc0.d453@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=n05ec@lzu.edu.cn \
/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