From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, sunliweis@126.com
Subject: RE: Bluetooth: btusb: Add new VID/PID 13d3/3584 for MT7922
Date: Tue, 13 May 2025 00:08:17 -0700 (PDT) [thread overview]
Message-ID: <6822efe1.170a0220.27b472.b195@mx.google.com> (raw)
In-Reply-To: <20250513061353.13521-2-sunliweis@126.com>
[-- Attachment #1: Type: text/plain, Size: 2029 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=962284
---Test result---
Test Summary:
CheckPatch PENDING 0.36 seconds
GitLint PENDING 0.34 seconds
SubjectPrefix PASS 0.07 seconds
BuildKernel PASS 25.78 seconds
CheckAllWarning PASS 27.90 seconds
CheckSparse PASS 31.67 seconds
BuildKernel32 PASS 25.25 seconds
TestRunnerSetup PASS 475.03 seconds
TestRunner_l2cap-tester PASS 22.87 seconds
TestRunner_iso-tester PASS 35.86 seconds
TestRunner_bnep-tester PASS 4.77 seconds
TestRunner_mgmt-tester FAIL 122.67 seconds
TestRunner_rfcomm-tester PASS 8.10 seconds
TestRunner_sco-tester PASS 14.32 seconds
TestRunner_ioctl-tester PASS 8.62 seconds
TestRunner_mesh-tester PASS 6.08 seconds
TestRunner_smp-tester PASS 7.22 seconds
TestRunner_userchan-tester PASS 5.13 seconds
IncrementalBuild PENDING 1.06 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: 484 (98.8%), Failed: 2, Not Run: 4
Failed Test Cases
LL Privacy - Set Flags 3 (2 Devices to RL) Failed 0.215 seconds
LL Privacy - Start Discovery 2 (Disable RL) Failed 0.197 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-05-13 7:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 6:13 [PATCH] Bluetooth: btusb: Add new VID/PID 13d3/3584 for MT7922 Liwei Sun
2025-05-13 7:08 ` bluez.test.bot [this message]
2025-05-15 17:10 ` patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2025-05-12 2:31 Liwei Sun
2025-05-12 3:00 ` bluez.test.bot
2025-04-30 23:50 [PATCH] " 青叶 西城
2025-05-01 1:14 ` 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=6822efe1.170a0220.27b472.b195@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sunliweis@126.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