From: "An, Tedd" <tedd.an@intel.com>
To: "luiz.dentz@gmail.com" <luiz.dentz@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: Bluetooth: HCI: Fix Set Extended (Scan Response) Data
Date: Tue, 8 Jun 2021 20:25:07 +0000 [thread overview]
Message-ID: <17f6995513da12fe72404ff19ac684477b92bbb3.camel@intel.com> (raw)
In-Reply-To: <CABBYNZ+yuNRGU4m68GRGd0exodb-0hwkLaYQ8gCE+NPi4bq0Fw@mail.gmail.com>
Hi Luiz,
On Tue, 2021-06-08 at 12:57 -0700, Luiz Augusto von Dentz wrote:
> Hi Tedd,
>
> On Tue, Jun 8, 2021 at 12:42 PM <bluez.test.bot@gmail.com> wrote:
> > 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=496525
> >
> > ---Test result---
> >
> > Test Summary:
> > CheckPatch PASS 1.03 seconds
> > GitLint PASS 0.10 seconds
> > BuildKernel PASS 512.94 seconds
> > TestRunner: Setup PASS 336.29 seconds
> > TestRunner: l2cap-tester PASS 2.59 seconds
> > TestRunner: bnep-tester PASS 1.87 seconds
> > TestRunner: mgmt-tester FAIL 29.48 seconds
> > TestRunner: rfcomm-tester PASS 2.03 seconds
> > TestRunner: sco-tester PASS 1.99 seconds
> > TestRunner: smp-tester PASS 2.06 seconds
> > TestRunner: userchan-tester PASS 1.88 seconds
> >
> > Details
> > ##############################
> > Test: CheckPatch - PASS - 1.03 seconds
> > Run checkpatch.pl script with rule in .checkpatch.conf
> >
> >
> > ##############################
> > Test: GitLint - PASS - 0.10 seconds
> > Run gitlint with rule in .gitlint
> >
> >
> > ##############################
> > Test: BuildKernel - PASS - 512.94 seconds
> > Build Kernel with minimal configuration supports Bluetooth
> >
> >
> > ##############################
> > Test: TestRunner: Setup - PASS - 336.29 seconds
> > Setup environment for running Test Runner
> >
> >
> > ##############################
> > Test: TestRunner: l2cap-tester - PASS - 2.59 seconds
> > Run test-runner with l2cap-tester
> > Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0
> >
> > ##############################
> > Test: TestRunner: bnep-tester - PASS - 1.87 seconds
> > Run test-runner with bnep-tester
> > Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0
> >
> > ##############################
> > Test: TestRunner: mgmt-tester - FAIL - 29.48 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.015 seconds
> > Add Ext Advertising - Success 2 (!Powered, Add Adv Inst) Failed 0.021 seconds
> > Add Ext Advertising - Success 5 (Set Adv off override) Failed 0.024 seconds
> > Add Ext Advertising - Success 6 (Scan Rsp Dta, Adv ok) Failed 0.019 seconds
> > Add Ext Advertising - Success 7 (Scan Rsp Dta, Scan ok) Failed 0.016 seconds
> > Add Ext Advertising - Success 9 (General Discov Flag) Failed 0.020 seconds
> > Add Ext Advertising - Success 10 (Limited Discov Flag) Failed 0.017 seconds
> > Add Ext Advertising - Success 11 (Managed Flags) Failed 0.023 seconds
> > Add Ext Advertising - Success 12 (TX Power Flag) Failed 0.017 seconds
> > Add Ext Advertising - Success 20 (Add Adv override) Failed 0.018 seconds
> > Add Ext Advertising - Success (Name is null) Failed 0.015 seconds
> > Add Ext Advertising - Success (Complete name) Failed 0.024 seconds
> > Add Ext Advertising - Success (Shortened name) Failed 0.024 seconds
> > Add Ext Advertising - Success (Short name) Failed 0.018 seconds
> > Add Ext Advertising - Success (Name + data) Failed 0.023 seconds
> > Add Ext Advertising - Success (Name+data+appear) Failed 0.025 seconds
> > Ext Adv MGMT - AD Data (5.0) Success Failed 0.022 seconds
> > Ext Adv MGMT - AD Scan Response (5.0) Success Failed 0.020 seconds
>
> We will probably need to fix these once the patch is merged, it looks
> like they are always expecting 31 bytes of data but the extended
> version this is variable size.
>
I will check if I can fix it even before merging this patch.
> > ##############################
> > Test: TestRunner: rfcomm-tester - PASS - 2.03 seconds
> > Run test-runner with rfcomm-tester
> > Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0
> >
> > ##############################
> > Test: TestRunner: sco-tester - PASS - 1.99 seconds
> > Run test-runner with sco-tester
> > Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
> >
> > ##############################
> > Test: TestRunner: smp-tester - PASS - 2.06 seconds
> > Run test-runner with smp-tester
> > Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
> >
> > ##############################
> > Test: TestRunner: userchan-tester - PASS - 1.88 seconds
> > Run test-runner with userchan-tester
> > Total: 3, Passed: 3 (100.0%), Failed: 0, Not Run: 0
> >
> >
> >
> > ---
> > Regards,
> > Linux Bluetooth
> >
>
>
Regards,
Tedd
next prev parent reply other threads:[~2021-06-08 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 18:44 [PATCH] Bluetooth: HCI: Fix Set Extended (Scan Response) Data Luiz Augusto von Dentz
2021-06-08 19:42 ` bluez.test.bot
2021-06-08 19:57 ` Luiz Augusto von Dentz
2021-06-08 20:25 ` An, Tedd [this message]
2021-06-09 4:52 ` [PATCH] " Marcel Holtmann
2021-06-09 17:10 ` Luiz Augusto von Dentz
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=17f6995513da12fe72404ff19ac684477b92bbb3.camel@intel.com \
--to=tedd.an@intel.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