From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, oss@fourdim.xyz
Subject: RE: [v4,1/2] Bluetooth: hci_conn: Fix null ptr deref in hci_abort_conn()
Date: Fri, 12 Jun 2026 11:32:43 -0700 (PDT) [thread overview]
Message-ID: <6a2c50cb.b7d808bf.7f055.c42c@mx.google.com> (raw)
In-Reply-To: <20260612161753.3140707-1-oss@fourdim.xyz>
[-- Attachment #1: Type: text/plain, Size: 2794 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=1110757
---Test result---
Test Summary:
CheckPatch PASS 2.09 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.13 seconds
GitLint PASS 0.64 seconds
SubjectPrefix PASS 0.24 seconds
BuildKernel PASS 31.25 seconds
CheckAllWarning PASS 29.22 seconds
CheckSparse PASS 27.09 seconds
BuildKernel32 PASS 24.86 seconds
TestRunnerSetup PASS 539.28 seconds
TestRunner_l2cap-tester PASS 59.68 seconds
TestRunner_iso-tester PASS 85.37 seconds
TestRunner_bnep-tester PASS 18.81 seconds
TestRunner_mgmt-tester FAIL 211.24 seconds
TestRunner_rfcomm-tester PASS 25.31 seconds
TestRunner_sco-tester PASS 32.96 seconds
TestRunner_ioctl-tester PASS 26.06 seconds
TestRunner_mesh-tester FAIL 25.94 seconds
TestRunner_smp-tester PASS 23.50 seconds
TestRunner_userchan-tester PASS 20.60 seconds
TestRunner_6lowpan-tester FAIL 46.95 seconds
IncrementalBuild PASS 42.35 seconds
Details
##############################
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.247 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.773 seconds
Mesh - Send cancel - 2 Timed out 1.990 seconds
##############################
Test: TestRunner_6lowpan-tester - FAIL
Desc: Run 6lowpan-tester with test-runner
Output:
Total: 8, Passed: 3 (37.5%), Failed: 5, Not Run: 0
Failed Test Cases
Client Connect - Disconnect Timed out 5.128 seconds
Client Recv Dgram - Success Timed out 4.988 seconds
Client Recv Raw - Success Timed out 4.994 seconds
Client Recv IPHC Dgram - Success Timed out 4.996 seconds
Client Recv IPHC Raw - Success Timed out 4.994 seconds
https://github.com/bluez/bluetooth-next/pull/311
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-06-12 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 16:16 [PATCH v4 1/2] Bluetooth: hci_conn: Fix null ptr deref in hci_abort_conn() Siwei Zhang
2026-06-12 16:16 ` [PATCH v4 2/2] Bluetooth: hci_sync: Remove unused hci_cmd_sync_dequeue_once() Siwei Zhang
2026-06-12 18:32 ` 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=6a2c50cb.b7d808bf.7f055.c42c@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=oss@fourdim.xyz \
/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.