From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, tcrawford@system76.com
Subject: RE: Bluetooth: btusb: Add MT7921e device 13d3:3576
Date: Wed, 08 Jan 2025 12:32:58 -0800 (PST) [thread overview]
Message-ID: <677ee0fa.050a0220.38c6a7.bcbc@mx.google.com> (raw)
In-Reply-To: <20250108200140.29719-1-tcrawford@system76.com>
[-- Attachment #1: Type: text/plain, Size: 2293 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=923499
---Test result---
Test Summary:
CheckPatch PENDING 0.27 seconds
GitLint PENDING 0.19 seconds
SubjectPrefix PASS 0.11 seconds
BuildKernel PASS 25.10 seconds
CheckAllWarning PASS 27.29 seconds
CheckSparse PASS 31.58 seconds
BuildKernel32 PASS 24.58 seconds
TestRunnerSetup PASS 434.92 seconds
TestRunner_l2cap-tester PASS 22.46 seconds
TestRunner_iso-tester PASS 31.54 seconds
TestRunner_bnep-tester PASS 4.77 seconds
TestRunner_mgmt-tester FAIL 120.08 seconds
TestRunner_rfcomm-tester PASS 7.66 seconds
TestRunner_sco-tester PASS 9.35 seconds
TestRunner_ioctl-tester PASS 8.10 seconds
TestRunner_mesh-tester FAIL 6.17 seconds
TestRunner_smp-tester PASS 6.92 seconds
TestRunner_userchan-tester PASS 5.02 seconds
IncrementalBuild PENDING 0.80 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 1 (Add to RL) Failed 0.146 seconds
LL Privacy - Set Flags 3 (2 Devices to RL) Failed 0.195 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.107 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-01-08 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 20:01 [PATCH] Bluetooth: btusb: Add MT7921e device 13d3:3576 Tim Crawford
2025-01-08 20:32 ` bluez.test.bot [this message]
2025-01-09 16:17 ` patchwork-bot+bluetooth
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=677ee0fa.050a0220.38c6a7.bcbc@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=tcrawford@system76.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 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.