From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, chandrashekar.devegowda@intel.com
Subject: RE: [v1,1/2] Bluetooth: hci_core: Add reset_type parameter to hdev->reset() callback
Date: Thu, 11 Jun 2026 22:36:59 -0700 (PDT) [thread overview]
Message-ID: <6a2b9afb.e1c1f991.2297f8.3751@mx.google.com> (raw)
In-Reply-To: <20260612012832.2395034-1-chandrashekar.devegowda@intel.com>
[-- 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=1110374
---Test result---
Test Summary:
CheckPatch PASS 3.16 seconds
VerifyFixes PASS 0.07 seconds
VerifySignedoff PASS 0.07 seconds
GitLint PASS 0.40 seconds
SubjectPrefix PASS 0.12 seconds
BuildKernel PASS 26.77 seconds
CheckAllWarning PASS 29.45 seconds
CheckSparse PASS 28.09 seconds
BuildKernel32 PASS 28.65 seconds
TestRunnerSetup PASS 578.26 seconds
TestRunner_l2cap-tester PASS 64.11 seconds
TestRunner_iso-tester PASS 76.12 seconds
TestRunner_bnep-tester PASS 18.76 seconds
TestRunner_mgmt-tester FAIL 212.36 seconds
TestRunner_rfcomm-tester PASS 25.63 seconds
TestRunner_sco-tester PASS 31.99 seconds
TestRunner_ioctl-tester PASS 25.87 seconds
TestRunner_mesh-tester FAIL 25.83 seconds
TestRunner_smp-tester PASS 22.87 seconds
TestRunner_userchan-tester PASS 19.36 seconds
TestRunner_6lowpan-tester FAIL 45.83 seconds
IncrementalBuild PASS 26.05 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.244 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.657 seconds
Mesh - Send cancel - 2 Timed out 2.001 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.240 seconds
Client Recv Dgram - Success Timed out 4.987 seconds
Client Recv Raw - Success Timed out 5.009 seconds
Client Recv IPHC Dgram - Success Timed out 4.986 seconds
Client Recv IPHC Raw - Success Timed out 4.997 seconds
https://github.com/bluez/bluetooth-next/pull/306
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-06-12 5:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 1:28 [PATCH v1 1/2] Bluetooth: hci_core: Add reset_type parameter to hdev->reset() callback Chandrashekar Devegowda
2026-06-12 1:28 ` [PATCH v1 2/2] Bluetooth: btintel_pcie: Fix TOCTOU race in reset path Chandrashekar Devegowda
2026-06-12 11:56 ` kernel test robot
2026-06-12 5:36 ` bluez.test.bot [this message]
2026-06-12 14:08 ` [PATCH v1 1/2] Bluetooth: hci_core: Add reset_type parameter to hdev->reset() callback Luiz Augusto von Dentz
2026-06-12 14:28 ` Bjorn Helgaas
2026-06-12 14:43 ` 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=6a2b9afb.e1c1f991.2297f8.3751@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=chandrashekar.devegowda@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox