From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zijun.hu@oss.qualcomm.com
Subject: RE: Bluetooth: btusb: Preparation for upcoming Qualcomm QCC2072 support
Date: Mon, 13 Jul 2026 06:11:51 -0700 (PDT) [thread overview]
Message-ID: <6a54e417.043ad0dd.13e2bf.3ef4@mx.google.com> (raw)
In-Reply-To: <20260713-btusb_prep_qcc2072-v2-1-bbcb651285f2@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 2389 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=1126612
---Test result---
Test Summary:
CheckPatch PASS 4.00 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.14 seconds
GitLint PASS 2.22 seconds
SubjectPrefix PASS 0.65 seconds
BuildKernel PASS 25.07 seconds
CheckAllWarning PASS 28.29 seconds
CheckSparse PASS 27.40 seconds
BuildKernel32 PASS 24.96 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 459.28 seconds
TestRunner_l2cap-tester PASS 57.49 seconds
TestRunner_iso-tester PASS 94.91 seconds
TestRunner_bnep-tester PASS 20.86 seconds
TestRunner_mgmt-tester FAIL 221.58 seconds
TestRunner_rfcomm-tester PASS 26.04 seconds
TestRunner_sco-tester PASS 32.42 seconds
TestRunner_ioctl-tester PASS 25.98 seconds
TestRunner_mesh-tester FAIL 25.96 seconds
TestRunner_smp-tester PASS 23.13 seconds
TestRunner_userchan-tester PASS 20.10 seconds
TestRunner_6lowpan-tester PASS 22.83 seconds
IncrementalBuild PASS 48.79 seconds
Details
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
##############################
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.239 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.605 seconds
Mesh - Send cancel - 2 Timed out 1.987 seconds
https://github.com/bluez/bluetooth-next/pull/430
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-07-13 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 12:01 [PATCH v2 0/5] Bluetooth: btusb: Preparation for upcoming Qualcomm QCC2072 support Zijun Hu
2026-07-13 12:01 ` [PATCH v2 1/5] Bluetooth: coredump: Introduce and apply hci_devcd_state_name() Zijun Hu
2026-07-13 13:11 ` bluez.test.bot [this message]
2026-07-13 12:01 ` [PATCH v2 2/5] Bluetooth: coredump: Allow drivers to pad dump header to fixed size Zijun Hu
2026-07-13 12:01 ` [PATCH v2 3/5] Bluetooth: btusb: Add an indirect recv_intr() hook to btusb_data Zijun Hu
2026-07-13 12:01 ` [PATCH v2 4/5] Bluetooth: btusb: Make btusb_recv_{event,acl}() take struct hci_dev * Zijun Hu
2026-07-13 12:01 ` [PATCH v2 5/5] Bluetooth: btusb: Add a simple static btusb_prepare_reset() Zijun Hu
-- strict thread matches above, loose matches on Subject: below --
2026-07-09 6:14 [PATCH 1/6] Bluetooth: coredump: Introduce and apply hci_devcd_state_name() Zijun Hu
2026-07-09 9:29 ` Bluetooth: btusb: Preparation for upcoming Qualcomm QCC2072 support bluez.test.bot
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=6a54e417.043ad0dd.13e2bf.3ef4@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=zijun.hu@oss.qualcomm.com \
/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