From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, chharry@google.com
Subject: RE: [1/4] Bluetooth: Introduce HCI Driver protocol
Date: Fri, 11 Apr 2025 07:03:31 -0700 (PDT) [thread overview]
Message-ID: <67f92133.050a0220.218762.b40a@mx.google.com> (raw)
In-Reply-To: <20250411133330.171563-1-chharry@google.com>
[-- Attachment #1: Type: text/plain, Size: 2214 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=952530
---Test result---
Test Summary:
CheckPatch PENDING 0.30 seconds
GitLint PENDING 0.20 seconds
SubjectPrefix PASS 0.46 seconds
BuildKernel PASS 24.45 seconds
CheckAllWarning PASS 26.95 seconds
CheckSparse PASS 30.86 seconds
BuildKernel32 PASS 24.07 seconds
TestRunnerSetup PASS 460.92 seconds
TestRunner_l2cap-tester PASS 21.13 seconds
TestRunner_iso-tester PASS 36.61 seconds
TestRunner_bnep-tester PASS 7.18 seconds
TestRunner_mgmt-tester FAIL 119.99 seconds
TestRunner_rfcomm-tester PASS 7.91 seconds
TestRunner_sco-tester PASS 12.57 seconds
TestRunner_ioctl-tester PASS 8.32 seconds
TestRunner_mesh-tester FAIL 6.40 seconds
TestRunner_smp-tester PASS 7.24 seconds
TestRunner_userchan-tester PASS 5.04 seconds
IncrementalBuild PENDING 0.87 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 490, Passed: 485 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
LL Privacy - Add Device 3 (AL is full) Failed 0.193 seconds
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 9 (90.0%), Failed: 1, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 2 Failed 0.120 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-04-11 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 13:33 [PATCH 1/4] Bluetooth: Introduce HCI Driver protocol Hsin-chen Chuang
2025-04-11 13:33 ` [PATCH 2/4] Bluetooth: btusb: Add HCI Drv commands for configuring altsetting Hsin-chen Chuang
2025-04-11 13:33 ` [PATCH 3/4] Revert "Bluetooth: btusb: Configure altsetting for HCI_USER_CHANNEL" Hsin-chen Chuang
2025-04-11 13:33 ` [PATCH 4/4] Revert "Bluetooth: btusb: add sysfs attribute to control USB alt setting" Hsin-chen Chuang
2025-04-11 14:03 ` bluez.test.bot [this message]
2025-04-15 19:46 ` [PATCH 1/4] Bluetooth: Introduce HCI Driver protocol 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=67f92133.050a0220.218762.b40a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=chharry@google.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