All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc: Shyh-In Hwang <josephsih@chromium.org>
Subject: Re: [v9,1/5] Bluetooth: btusb: disable Intel link statistics telemetry events
Date: Mon, 16 Aug 2021 10:49:39 -0700	[thread overview]
Message-ID: <CABBYNZLcEctR6=ovTK_CABqkKgU8UCKQQ30VsVsAJkdEA+xY0A@mail.gmail.com> (raw)
In-Reply-To: <61191554.1c69fb81.89ead.b7d9@mx.google.com>

Hi Joseph,

On Sun, Aug 15, 2021 at 6:25 AM <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=531683
>
> ---Test result---
>
> Test Summary:
> CheckPatch                    PASS      2.92 seconds
> GitLint                       PASS      0.61 seconds
> BuildKernel                   PASS      598.41 seconds
> TestRunner: Setup             PASS      394.12 seconds
> TestRunner: l2cap-tester      PASS      2.89 seconds
> TestRunner: bnep-tester       PASS      2.07 seconds
> TestRunner: mgmt-tester       FAIL      30.94 seconds
> TestRunner: rfcomm-tester     PASS      2.31 seconds
> TestRunner: sco-tester        PASS      2.20 seconds
> TestRunner: smp-tester        FAIL      2.27 seconds
> TestRunner: userchan-tester   PASS      2.09 seconds
>
> Details
> ##############################
> Test: CheckPatch - PASS - 2.92 seconds
> Run checkpatch.pl script with rule in .checkpatch.conf
>
>
> ##############################
> Test: GitLint - PASS - 0.61 seconds
> Run gitlint with rule in .gitlint
>
>
> ##############################
> Test: BuildKernel - PASS - 598.41 seconds
> Build Kernel with minimal configuration supports Bluetooth
>
>
> ##############################
> Test: TestRunner: Setup - PASS - 394.12 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.07 seconds
> Run test-runner with bnep-tester
> Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0
>
> ##############################
> Test: TestRunner: mgmt-tester - FAIL - 30.94 seconds
> Run test-runner with mgmt-tester
> Total: 448, Passed: 444 (99.1%), Failed: 1, Not Run: 3
>
> Failed Test Cases
> Read Exp Feature - Success                           Failed       0.012 seconds

Looks like there is a regression on mgmt-tester:

Read Exp Feature - Success - run
  Sending Read Experimental Features Information (0x0049)
  Test condition added, total 1
  Read Experimental Features Information (0x0049): Success (0x00)
  Invalid cmd response parameter size
Read Exp Feature - Success - test failed

>
> ##############################
> 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.20 seconds
> Run test-runner with sco-tester
> Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
>
> ##############################
> Test: TestRunner: smp-tester - FAIL - 2.27 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.09 seconds
> Run test-runner with userchan-tester
> Total: 3, Passed: 3 (100.0%), Failed: 0, Not Run: 0
>
>
>
> ---
> Regards,
> Linux Bluetooth
>


-- 
Luiz Augusto von Dentz

  reply	other threads:[~2021-08-16 17:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-15 12:17 [PATCH v9 1/5] Bluetooth: btusb: disable Intel link statistics telemetry events Joseph Hwang
2021-08-15 12:17 ` [PATCH v9 2/5] Bluetooth: btintel: support " Joseph Hwang
2021-08-15 12:17 ` [PATCH v9 3/5] Bluetooth: refactor set_exp_feature with a feature table Joseph Hwang
2021-08-15 12:17 ` [PATCH v9 4/5] Bluetooth: Support the quality report events Joseph Hwang
2021-08-15 12:17 ` [PATCH v9 5/5] Bluetooth: set quality report callback for Intel Joseph Hwang
2021-08-15 13:23 ` [v9,1/5] Bluetooth: btusb: disable Intel link statistics telemetry events bluez.test.bot
2021-08-16 17:49   ` Luiz Augusto von Dentz [this message]
2021-08-17  9:54     ` Joseph Hwang
2021-08-18  5:49       ` Joseph Hwang
2021-08-19 18:04         ` Luiz Augusto von Dentz
2021-08-20  5:27           ` Joseph Hwang
2021-08-26  0:02             ` Joseph Hwang
2021-08-27 17:05               ` 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='CABBYNZLcEctR6=ovTK_CABqkKgU8UCKQQ30VsVsAJkdEA+xY0A@mail.gmail.com' \
    --to=luiz.dentz@gmail.com \
    --cc=josephsih@chromium.org \
    --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.