From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, guanwentao@uniontech.com
Subject: RE: Bluetooth: HCI: Add definition of hci_rp_remote_name_req_cancel
Date: Mon, 17 Mar 2025 09:36:31 -0700 (PDT) [thread overview]
Message-ID: <67d84f8f.620a0220.a1752.d102@mx.google.com> (raw)
In-Reply-To: <20250317154715.15023-1-guanwentao@uniontech.com>
[-- Attachment #1: Type: text/plain, Size: 2636 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=944728
---Test result---
Test Summary:
CheckPatch PENDING 0.36 seconds
GitLint PENDING 0.23 seconds
SubjectPrefix PASS 0.07 seconds
BuildKernel PASS 25.25 seconds
CheckAllWarning PASS 27.58 seconds
CheckSparse WARNING 30.98 seconds
BuildKernel32 PASS 24.69 seconds
TestRunnerSetup PASS 440.96 seconds
TestRunner_l2cap-tester PASS 21.11 seconds
TestRunner_iso-tester PASS 37.47 seconds
TestRunner_bnep-tester PASS 4.98 seconds
TestRunner_mgmt-tester FAIL 122.05 seconds
TestRunner_rfcomm-tester PASS 7.91 seconds
TestRunner_sco-tester PASS 12.39 seconds
TestRunner_ioctl-tester PASS 8.20 seconds
TestRunner_mesh-tester FAIL 6.30 seconds
TestRunner_smp-tester PASS 7.19 seconds
TestRunner_userchan-tester PASS 5.09 seconds
IncrementalBuild PENDING 1.02 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
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: 490, Passed: 484 (98.8%), Failed: 2, Not Run: 4
Failed Test Cases
LL Privacy - Set Flags 3 (2 Devices to RL) Failed 0.186 seconds
LL Privacy - Set Device Flag 1 (Device Privacy) Failed 0.154 seconds
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
BUG: KASAN: slab-use-after-free in run_timer_softirq+0x76f/0x7d0
WARNING: CPU: 0 PID: 35 at kernel/workqueue.c:2257 __queue_work+0x687/0xb40
Total: 10, Passed: 9 (90.0%), Failed: 1, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Failed 0.112 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-03-17 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 15:47 [PATCH] Bluetooth: HCI: Add definition of hci_rp_remote_name_req_cancel Wentao Guan
2025-03-17 16:36 ` bluez.test.bot [this message]
2025-03-17 17:47 ` Luiz Augusto von Dentz
2025-03-17 18:15 ` Wentao Guan
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=67d84f8f.620a0220.a1752.d102@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=guanwentao@uniontech.com \
--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.