From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, sean.wang@mediatek.com
Subject: RE: Bluetooth: btmtksdio: Add in-band wakeup support
Date: Thu, 09 Jun 2022 19:58:51 -0700 (PDT) [thread overview]
Message-ID: <62a2b36b.1c69fb81.3185b.c6ff@mx.google.com> (raw)
In-Reply-To: <742cdffcf110e1601257207fb2b0d3f426d4008c.1654819586.git.objelf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1458 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=649029
---Test result---
Test Summary:
CheckPatch PASS 0.94 seconds
GitLint PASS 0.58 seconds
SubjectPrefix PASS 0.40 seconds
BuildKernel PASS 31.50 seconds
BuildKernel32 PASS 27.88 seconds
Incremental Build with patchesPASS 38.46 seconds
TestRunner: Setup PASS 476.73 seconds
TestRunner: l2cap-tester PASS 17.07 seconds
TestRunner: bnep-tester PASS 5.76 seconds
TestRunner: mgmt-tester FAIL 104.69 seconds
TestRunner: rfcomm-tester PASS 9.32 seconds
TestRunner: sco-tester PASS 8.97 seconds
TestRunner: smp-tester PASS 9.20 seconds
TestRunner: userchan-tester PASS 6.01 seconds
Details
##############################
Test: TestRunner: mgmt-tester - FAIL - 104.69 seconds
Run test-runner with mgmt-tester
Total: 493, Passed: 491 (99.6%), Failed: 2, Not Run: 0
Failed Test Cases
Add Advertising - Success (Name+data+appear) Timed out 2.360 seconds
Add Ext Advertising - Success (Name+data+appear) Timed out 2.572 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-06-10 2:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 0:17 [PATCH] Bluetooth: btmtksdio: Add in-band wakeup support sean.wang
2022-06-10 2:58 ` bluez.test.bot [this message]
2022-06-10 7:16 ` Paul Menzel
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=62a2b36b.1c69fb81.3185b.c6ff@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sean.wang@mediatek.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