From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hao.qin@mediatek.com
Subject: RE: [1/1] Bluetooth: btusb: mediatek: add a recovery method for MT7922
Date: Thu, 14 Dec 2023 23:32:40 -0800 (PST) [thread overview]
Message-ID: <657c0118.0c0a0220.35d81.a98f@mx.google.com> (raw)
In-Reply-To: <20231215063714.7684-1-hao.qin@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 1698 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=810339
---Test result---
Test Summary:
CheckPatch PASS 0.68 seconds
GitLint PASS 0.68 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 27.89 seconds
CheckAllWarning PASS 30.45 seconds
CheckSparse PASS 35.75 seconds
CheckSmatch PASS 99.39 seconds
BuildKernel32 PASS 27.14 seconds
TestRunnerSetup PASS 424.70 seconds
TestRunner_l2cap-tester PASS 23.16 seconds
TestRunner_iso-tester PASS 51.26 seconds
TestRunner_bnep-tester PASS 6.98 seconds
TestRunner_mgmt-tester FAIL 164.58 seconds
TestRunner_rfcomm-tester PASS 10.89 seconds
TestRunner_sco-tester PASS 14.40 seconds
TestRunner_ioctl-tester PASS 11.99 seconds
TestRunner_mesh-tester PASS 8.82 seconds
TestRunner_smp-tester PASS 9.79 seconds
TestRunner_userchan-tester PASS 7.40 seconds
IncrementalBuild PASS 25.50 seconds
Details
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 497, Passed: 495 (99.6%), Failed: 1, Not Run: 1
Failed Test Cases
LL Privacy - Remove Device 4 (Disable Adv) Timed out 2.189 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-12-15 7:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 6:37 [PATCH 1/1] Bluetooth: btusb: mediatek: add a recovery method for MT7922 Hao Qin
2023-12-15 7:32 ` bluez.test.bot [this message]
2023-12-19 0:29 ` Sean Wang
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=657c0118.0c0a0220.35d81.a98f@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hao.qin@mediatek.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;
as well as URLs for NNTP newsgroup(s).