From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, jun.miao@windriver.com
Subject: RE: [v2] Bluetooth: btusb: Fix a unspported condition to set debug features
Date: Fri, 09 Jul 2021 21:10:04 -0700 (PDT) [thread overview]
Message-ID: <60e91d9c.1c69fb81.621c0.74db@mx.google.com> (raw)
In-Reply-To: <20210710030136.1567673-1-jun.miao@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 3598 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=513365
---Test result---
Test Summary:
CheckPatch FAIL 0.52 seconds
GitLint FAIL 0.13 seconds
BuildKernel PASS 610.96 seconds
TestRunner: Setup PASS 406.62 seconds
TestRunner: l2cap-tester PASS 2.89 seconds
TestRunner: bnep-tester PASS 2.12 seconds
TestRunner: mgmt-tester PASS 31.82 seconds
TestRunner: rfcomm-tester PASS 2.31 seconds
TestRunner: sco-tester PASS 2.24 seconds
TestRunner: smp-tester FAIL 2.31 seconds
TestRunner: userchan-tester PASS 2.16 seconds
Details
##############################
Test: CheckPatch - FAIL - 0.52 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
Bluetooth: btusb: Fix a unspported condition to set debug features
WARNING: Unknown commit id 'c453b10c2b28', maybe rebased or not pulled?
#11:
Fixes: c453b10c2b28 ("Bluetooth: btusb: Configure Intel debug feature based on available support")
total: 0 errors, 1 warnings, 30 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
"[PATCH] Bluetooth: btusb: Fix a unspported condition to set debug" has style problems, please review.
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL - 0.13 seconds
Run gitlint with rule in .gitlint
Bluetooth: btusb: Fix a unspported condition to set debug features
7: B1 Line exceeds max length (98>80): "Fixes: c453b10c2b28 ("Bluetooth: btusb: Configure Intel debug feature based on available support")"
##############################
Test: BuildKernel - PASS - 610.96 seconds
Build Kernel with minimal configuration supports Bluetooth
##############################
Test: TestRunner: Setup - PASS - 406.62 seconds
Setup environment for running Test Runner
##############################
Test: TestRunner: l2cap-tester - PASS - 2.89 seconds
Run test-runner with l2cap-tester
Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: bnep-tester - PASS - 2.12 seconds
Run test-runner with bnep-tester
Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: mgmt-tester - PASS - 31.82 seconds
Run test-runner with mgmt-tester
Total: 446, Passed: 443 (99.3%), Failed: 0, Not Run: 3
##############################
Test: TestRunner: rfcomm-tester - PASS - 2.31 seconds
Run test-runner with rfcomm-tester
Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: sco-tester - PASS - 2.24 seconds
Run test-runner with sco-tester
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: smp-tester - FAIL - 2.31 seconds
Run test-runner with smp-tester
Total: 8, Passed: 7 (87.5%), Failed: 1, Not Run: 0
Failed Test Cases
SMP Client - SC Request 2 Failed 0.024 seconds
##############################
Test: TestRunner: userchan-tester - PASS - 2.16 seconds
Run test-runner with userchan-tester
Total: 3, Passed: 3 (100.0%), Failed: 0, Not Run: 0
---
Regards,
Linux Bluetooth
[-- Attachment #2: l2cap-tester.log --]
[-- Type: application/octet-stream, Size: 44350 bytes --]
[-- Attachment #3: bnep-tester.log --]
[-- Type: application/octet-stream, Size: 3557 bytes --]
[-- Attachment #4: mgmt-tester.log --]
[-- Type: application/octet-stream, Size: 614404 bytes --]
[-- Attachment #5: rfcomm-tester.log --]
[-- Type: application/octet-stream, Size: 11677 bytes --]
[-- Attachment #6: sco-tester.log --]
[-- Type: application/octet-stream, Size: 9912 bytes --]
[-- Attachment #7: smp-tester.log --]
[-- Type: application/octet-stream, Size: 11705 bytes --]
[-- Attachment #8: userchan-tester.log --]
[-- Type: application/octet-stream, Size: 5453 bytes --]
next prev parent reply other threads:[~2021-07-10 4:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 3:01 [PATCH] [v2] Bluetooth: btusb: Fix a unspported condition to set debug features Jun Miao
2021-07-10 4:10 ` bluez.test.bot [this message]
2021-07-13 2:40 ` Joseph Hwang
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=60e91d9c.1c69fb81.621c0.74db@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=jun.miao@windriver.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.