From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kevin@simpleble.org
Subject: RE: [v3] Bluetooth: MGMT: Fix discovery stuck after a failed Stop Discovery
Date: Tue, 27 Oct 2026 17:40:28 -0700 (PDT) [thread overview]
Message-ID: <6ae1447c.31957b85.6547a.458e@mx.google.com> (raw)
In-Reply-To: <20261027210057.44347-1-kevin@simpleble.org>
[-- Attachment #1: Type: text/plain, Size: 2083 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/1194926/
---Test result---
Test Summary:
CheckPatch PASS 0.86 seconds
VerifyFixes PASS 0.11 seconds
VerifySignedoff PASS 0.11 seconds
GitLint PASS 0.29 seconds
SubjectPrefix PASS 0.10 seconds
BuildKernel PASS 19.69 seconds
CheckAllWarning PASS 23.75 seconds
CheckSparse WARNING 24.59 seconds
BuildKernel32 PASS 25.35 seconds
CheckKernelLLVM PASS 23.24 seconds
TestRunnerSetup PASS 425.00 seconds
TestRunner_l2cap-tester PASS 12.94 seconds
TestRunner_iso-tester PASS 8.87 seconds
TestRunner_bnep-tester PASS 2.77 seconds
TestRunner_mgmt-tester FAIL 81.10 seconds
TestRunner_rfcomm-tester PASS 3.98 seconds
TestRunner_sco-tester PASS 4.98 seconds
TestRunner_ioctl-tester PASS 4.03 seconds
TestRunner_mesh-tester PASS 5.01 seconds
TestRunner_smp-tester PASS 3.88 seconds
TestRunner_userchan-tester PASS 2.80 seconds
TestRunner_6lowpan-tester PASS 10.21 seconds
IncrementalBuild PASS 18.48 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: 515, Passed: 514 (99.8%), Failed: 1, Not Run: 0
Failed Test Cases
LL Privacy - Add Device 2 (2 Devices to AL) Failed 0.022 seconds
https://github.com/bluez/bluetooth-next/pull/1012
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-10-28 0:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 21:00 [PATCH v3] Bluetooth: MGMT: Fix discovery stuck after a failed Stop Discovery Kevin Dewald
2026-10-28 0:40 ` 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=6ae1447c.31957b85.6547a.458e@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=kevin@simpleble.org \
--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.