From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, chharry@google.com
Subject: RE: Bluetooth: Add driver command BTUSB_DRV_CMD_SWITCH_ALT_SETTING
Date: Tue, 01 Apr 2025 07:33:14 -0700 (PDT) [thread overview]
Message-ID: <67ebf92a.050a0220.19b15e.730f@mx.google.com> (raw)
In-Reply-To: <20250401134424.3725875-1-chharry@google.com>
[-- Attachment #1: Type: text/plain, Size: 2218 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=948951
---Test result---
Test Summary:
CheckPatch PENDING 0.40 seconds
GitLint PENDING 0.26 seconds
SubjectPrefix PASS 0.11 seconds
BuildKernel PASS 24.01 seconds
CheckAllWarning PASS 26.43 seconds
CheckSparse PASS 30.05 seconds
BuildKernel32 PASS 24.08 seconds
TestRunnerSetup PASS 428.46 seconds
TestRunner_l2cap-tester FAIL 44.90 seconds
TestRunner_iso-tester PASS 34.68 seconds
TestRunner_bnep-tester PASS 4.73 seconds
TestRunner_mgmt-tester FAIL 119.51 seconds
TestRunner_rfcomm-tester PASS 7.76 seconds
TestRunner_sco-tester PASS 12.47 seconds
TestRunner_ioctl-tester PASS 12.65 seconds
TestRunner_mesh-tester PASS 6.04 seconds
TestRunner_smp-tester PASS 7.09 seconds
TestRunner_userchan-tester PASS 4.93 seconds
IncrementalBuild PENDING 0.50 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Total: 62, Passed: 61 (98.4%), Failed: 1, Not Run: 0
Failed Test Cases
L2CAP LE Client - Close socket 2 Timed out 23.647 seconds
##############################
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 - Set Device Flag 1 (Device Privacy) Failed 0.154 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-01 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 13:44 [PATCH] Bluetooth: Add driver command BTUSB_DRV_CMD_SWITCH_ALT_SETTING Hsin-chen Chuang
2025-04-01 14:33 ` bluez.test.bot [this message]
2025-04-01 15:02 ` Luiz Augusto von Dentz
2025-04-01 15:26 ` Hsin-chen Chuang
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=67ebf92a.050a0220.19b15e.730f@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 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.