From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v2] Bluetooth: HCI: Fix Set Extended (Scan Response) Data
Date: Wed, 09 Jun 2021 11:35:44 -0700 (PDT) [thread overview]
Message-ID: <60c10a00.1c69fb81.47c6c.52c6@mx.google.com> (raw)
In-Reply-To: <20210609180927.179265-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4735 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=497479
---Test result---
Test Summary:
CheckPatch FAIL 0.87 seconds
GitLint PASS 0.10 seconds
BuildKernel PASS 513.70 seconds
TestRunner: Setup PASS 360.47 seconds
TestRunner: l2cap-tester PASS 2.64 seconds
TestRunner: bnep-tester PASS 1.89 seconds
TestRunner: mgmt-tester FAIL 28.61 seconds
TestRunner: rfcomm-tester PASS 2.14 seconds
TestRunner: sco-tester PASS 2.01 seconds
TestRunner: smp-tester PASS 2.08 seconds
TestRunner: userchan-tester PASS 1.92 seconds
Details
##############################
Test: CheckPatch - FAIL - 0.87 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
Bluetooth: HCI: Fix Set Extended (Scan Response) Data
WARNING: Unknown commit id 'a0fb3726ba551', maybe rebased or not pulled?
#11:
Fixes: a0fb3726ba551 ("Bluetooth: Use Set ext adv/scan rsp data if
total: 0 errors, 1 warnings, 0 checks, 131 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: HCI: Fix Set Extended (Scan Response) Data" 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 - PASS - 0.10 seconds
Run gitlint with rule in .gitlint
##############################
Test: BuildKernel - PASS - 513.70 seconds
Build Kernel with minimal configuration supports Bluetooth
##############################
Test: TestRunner: Setup - PASS - 360.47 seconds
Setup environment for running Test Runner
##############################
Test: TestRunner: l2cap-tester - PASS - 2.64 seconds
Run test-runner with l2cap-tester
Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: bnep-tester - PASS - 1.89 seconds
Run test-runner with bnep-tester
Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: mgmt-tester - FAIL - 28.61 seconds
Run test-runner with mgmt-tester
Total: 446, Passed: 415 (93.0%), Failed: 18, Not Run: 13
Failed Test Cases
Add Ext Advertising - Success 1 (Powered, Add Adv Inst) Failed 0.016 seconds
Add Ext Advertising - Success 2 (!Powered, Add Adv Inst) Failed 0.014 seconds
Add Ext Advertising - Success 5 (Set Adv off override) Failed 0.022 seconds
Add Ext Advertising - Success 6 (Scan Rsp Dta, Adv ok) Failed 0.017 seconds
Add Ext Advertising - Success 7 (Scan Rsp Dta, Scan ok) Failed 0.017 seconds
Add Ext Advertising - Success 9 (General Discov Flag) Failed 0.022 seconds
Add Ext Advertising - Success 10 (Limited Discov Flag) Failed 0.024 seconds
Add Ext Advertising - Success 11 (Managed Flags) Failed 0.018 seconds
Add Ext Advertising - Success 12 (TX Power Flag) Failed 0.015 seconds
Add Ext Advertising - Success 20 (Add Adv override) Failed 0.027 seconds
Add Ext Advertising - Success (Name is null) Failed 0.015 seconds
Add Ext Advertising - Success (Complete name) Failed 0.015 seconds
Add Ext Advertising - Success (Shortened name) Failed 0.015 seconds
Add Ext Advertising - Success (Short name) Failed 0.016 seconds
Add Ext Advertising - Success (Name + data) Failed 0.015 seconds
Add Ext Advertising - Success (Name+data+appear) Failed 0.016 seconds
Ext Adv MGMT - AD Data (5.0) Success Failed 0.015 seconds
Ext Adv MGMT - AD Scan Response (5.0) Success Failed 0.015 seconds
##############################
Test: TestRunner: rfcomm-tester - PASS - 2.14 seconds
Run test-runner with rfcomm-tester
Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: sco-tester - PASS - 2.01 seconds
Run test-runner with sco-tester
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: smp-tester - PASS - 2.08 seconds
Run test-runner with smp-tester
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: userchan-tester - PASS - 1.92 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: 44349 bytes --]
[-- Attachment #3: bnep-tester.log --]
[-- Type: application/octet-stream, Size: 3556 bytes --]
[-- Attachment #4: mgmt-tester.log --]
[-- Type: application/octet-stream, Size: 608639 bytes --]
[-- Attachment #5: rfcomm-tester.log --]
[-- Type: application/octet-stream, Size: 11676 bytes --]
[-- Attachment #6: sco-tester.log --]
[-- Type: application/octet-stream, Size: 9911 bytes --]
[-- Attachment #7: smp-tester.log --]
[-- Type: application/octet-stream, Size: 11822 bytes --]
[-- Attachment #8: userchan-tester.log --]
[-- Type: application/octet-stream, Size: 5453 bytes --]
next prev parent reply other threads:[~2021-06-09 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 18:09 [PATCH v2] Bluetooth: HCI: Fix Set Extended (Scan Response) Data Luiz Augusto von Dentz
2021-06-09 18:35 ` bluez.test.bot [this message]
2021-06-09 19:23 ` Marcel Holtmann
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=60c10a00.1c69fb81.47c6c.52c6@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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