Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
MIME-Version: 1.0
References: <20220412120945.28862-1-vasyl.vavrychuk@opensynergy.com> <6255804f.1c69fb81.50dda.e99b@mx.google.com>
In-Reply-To: <6255804f.1c69fb81.50dda.e99b@mx.google.com>
From:   Vasyl Vavrychuk <vvavrychuk@gmail.com>
Date:   Tue, 12 Apr 2022 21:26:40 +0300
Message-ID: <CAGj4m+413TdHZFTpFZS3yV60+uakMw-Y9BkCg4khTWgQpA+sCg@mail.gmail.com>
Subject: Re: [RFC] Bluetooth: core: Allow bind HCI socket user channel when
 HCI is UP.
To:     linux-bluetooth@vger.kernel.org
Cc:     Marcel Holtmann <marcel@holtmann.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

CI reported userchan-tester failure since it is expected old
behaviour: that bind to user channel should fail when device is
powered up.

I can update https://github.com/bluez/bluez/blob/master/tools/userchan-test=
er.c
by removing test cases:
* User channel open - Failed
* User channel open - Power Toggle Success

On Tue, Apr 12, 2022 at 4:36 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=3D631=
489
>
> ---Test result---
>
> Test Summary:
> CheckPatch                    FAIL      1.67 seconds
> GitLint                       FAIL      1.02 seconds
> SubjectPrefix                 PASS      0.82 seconds
> BuildKernel                   PASS      30.11 seconds
> BuildKernel32                 PASS      27.80 seconds
> Incremental Build with patchesPASS      39.08 seconds
> TestRunner: Setup             PASS      471.62 seconds
> TestRunner: l2cap-tester      PASS      16.22 seconds
> TestRunner: bnep-tester       PASS      6.26 seconds
> TestRunner: mgmt-tester       PASS      106.06 seconds
> TestRunner: rfcomm-tester     PASS      8.22 seconds
> TestRunner: sco-tester        PASS      7.99 seconds
> TestRunner: smp-tester        PASS      7.98 seconds
> TestRunner: userchan-tester   FAIL      6.66 seconds
>
> Details
> ##############################
> Test: CheckPatch - FAIL - 1.67 seconds
> Run checkpatch.pl script with rule in .checkpatch.conf
> [RFC] Bluetooth: core: Allow bind HCI socket user channel when HCI is UP.=
\WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: email address mismatc=
h: 'From: Vasyl Vavrychuk <vvavrychuk@gmail.com>' !=3D 'Signed-off-by: Vasy=
l Vavrychuk <vasyl.vavrychuk@opensynergy.com>'
>
> total: 0 errors, 1 warnings, 0 checks, 10 lines checked
>
> NOTE: For some of the reported defects, checkpatch may be able to
>       mechanically convert to the typical style using --fix or --fix-inpl=
ace.
>
> /github/workspace/src/12810739.patch has style problems, please review.
>
> NOTE: Ignored message types: UNKNOWN_COMMIT_ID
>
> NOTE: If any of the errors are false positives, please report
>       them to the maintainer, see CHECKPATCH in MAINTAINERS.
>
>
> ##############################
> Test: GitLint - FAIL - 1.02 seconds
> Run gitlint with rule in .gitlint
> [RFC] Bluetooth: core: Allow bind HCI socket user channel when HCI is UP.
> 1: T3 Title has trailing punctuation (.): "[RFC] Bluetooth: core: Allow b=
ind HCI socket user channel when HCI is UP."
>
>
> ##############################
> Test: TestRunner: userchan-tester - FAIL - 6.66 seconds
> Run test-runner with userchan-tester
> Total: 4, Passed: 3 (75.0%), Failed: 1, Not Run: 0
>
> Failed Test Cases
> User channel open - Failed                           Failed       0.082 s=
econds
>
>
>
> ---
> Regards,
> Linux Bluetooth
>