linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ayush.garg@samsung.com
Subject: RE: Bluetooth: Support for LE Set Preferred PHY
Date: Thu, 22 Jul 2021 00:20:14 -0700 (PDT)	[thread overview]
Message-ID: <60f91c2e.1c69fb81.4bb63.f27b@mx.google.com> (raw)
In-Reply-To: <20210722053843.6691-2-ayush.garg@samsung.com>

[-- Attachment #1: Type: text/plain, Size: 5848 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=519481

---Test result---

Test Summary:
CheckPatch                    PASS      3.62 seconds
GitLint                       FAIL      0.49 seconds
BuildKernel                   PASS      675.81 seconds
TestRunner: Setup             PASS      439.04 seconds
TestRunner: l2cap-tester      PASS      3.18 seconds
TestRunner: bnep-tester       PASS      2.18 seconds
TestRunner: mgmt-tester       PASS      34.44 seconds
TestRunner: rfcomm-tester     PASS      2.46 seconds
TestRunner: sco-tester        PASS      2.34 seconds
TestRunner: smp-tester        FAIL      2.54 seconds
TestRunner: userchan-tester   PASS      2.24 seconds

Details
##############################
Test: CheckPatch - PASS - 3.62 seconds
Run checkpatch.pl script with rule in .checkpatch.conf


##############################
Test: GitLint - FAIL - 0.49 seconds
Run gitlint with rule in .gitlint
Bluetooth: Fix incorrect parsing of LE_PHY params
8: B3 Line contains hard tab characters (\t): "	  LE PHY Update Complete (0x0c)"
9: B3 Line contains hard tab characters (\t): "		Status: Success (0x00)"
10: B3 Line contains hard tab characters (\t): "		Handle: 0"
11: B3 Line contains hard tab characters (\t): "		TX PHY: LE Coded (0x03)"
12: B3 Line contains hard tab characters (\t): "		RX PHY: LE Coded (0x03)"

Bluetooth: Implement BT_PHY setsocket option
7: B3 Line contains hard tab characters (\t): "		Handle: 0"
8: B3 Line contains hard tab characters (\t): "		All PHYs preference: 0x00"
9: B3 Line contains hard tab characters (\t): "		TX PHYs preference: 0x02"
10: B3 Line contains hard tab characters (\t): "		  LE 2M"
11: B3 Line contains hard tab characters (\t): "		RX PHYs preference: 0x02"
12: B3 Line contains hard tab characters (\t): "		  LE 2M"
13: B3 Line contains hard tab characters (\t): "		PHY options preference: Reserved (0x0000)"
15: B3 Line contains hard tab characters (\t): "	  LE Set PHY (0x08|0x0032) ncmd 1"
16: B3 Line contains hard tab characters (\t): "		Status: Success (0x00)"
18: B3 Line contains hard tab characters (\t): "	  LE PHY Update Complete (0x0c)"
19: B3 Line contains hard tab characters (\t): "		Status: Success (0x00)"
20: B3 Line contains hard tab characters (\t): "		Handle: 0"
21: B3 Line contains hard tab characters (\t): "		TX PHY: LE 2M (0x02)"
22: B3 Line contains hard tab characters (\t): "		RX PHY: LE 2M (0x02)"

Bluetooth: Add support for sending LE PHY Update event over mgmt
10: B3 Line contains hard tab characters (\t): "	  LE PHY Update Complete (0x0c)"
11: B3 Line contains hard tab characters (\t): "		Status: Success (0x00)"
12: B3 Line contains hard tab characters (\t): "		Handle: 0"
13: B3 Line contains hard tab characters (\t): "		TX PHY: LE 2M (0x02)"
14: B3 Line contains hard tab characters (\t): "		RX PHY: LE 2M (0x02)"
16: B3 Line contains hard tab characters (\t): "		LE Address: 45:18:F8:CF:23:7E (Resolvable)"
17: B3 Line contains hard tab characters (\t): "		Status: Success (0x00)"
18: B3 Line contains hard tab characters (\t): "		Updated PHYs: 0x1800"
19: B3 Line contains hard tab characters (\t): "		  LE 2M TX"
20: B3 Line contains hard tab characters (\t): "		  LE 2M RX"

Bluetooth: Update LE TX & RX PHYs when connection established
11: B3 Line contains hard tab characters (\t): "		Handle: 0"
13: B3 Line contains hard tab characters (\t): "	  LE Read PHY (0x08|0x0030) ncmd 1"
14: B3 Line contains hard tab characters (\t): "		Status: Success (0x00)"
15: B3 Line contains hard tab characters (\t): "		Handle: 0"
16: B3 Line contains hard tab characters (\t): "		TX PHY: LE 1M (0x01)"
17: B3 Line contains hard tab characters (\t): "		RX PHY: LE 1M (0x01)"
19: B3 Line contains hard tab characters (\t): "		LE Address: 45:18:F8:CF:23:7E (Resolvable)"
20: B3 Line contains hard tab characters (\t): "		Status: Success (0x00)"
21: B3 Line contains hard tab characters (\t): "		Updated PHYs: 0x0600"
22: B3 Line contains hard tab characters (\t): "		  LE 1M TX"
23: B3 Line contains hard tab characters (\t): "		  LE 1M RX"


##############################
Test: BuildKernel - PASS - 675.81 seconds
Build Kernel with minimal configuration supports Bluetooth


##############################
Test: TestRunner: Setup - PASS - 439.04 seconds
Setup environment for running Test Runner


##############################
Test: TestRunner: l2cap-tester - PASS - 3.18 seconds
Run test-runner with l2cap-tester
Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0

##############################
Test: TestRunner: bnep-tester - PASS - 2.18 seconds
Run test-runner with bnep-tester
Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0

##############################
Test: TestRunner: mgmt-tester - PASS - 34.44 seconds
Run test-runner with mgmt-tester
Total: 448, Passed: 445 (99.3%), Failed: 0, Not Run: 3

##############################
Test: TestRunner: rfcomm-tester - PASS - 2.46 seconds
Run test-runner with rfcomm-tester
Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0

##############################
Test: TestRunner: sco-tester - PASS - 2.34 seconds
Run test-runner with sco-tester
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0

##############################
Test: TestRunner: smp-tester - FAIL - 2.54 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.036 seconds

##############################
Test: TestRunner: userchan-tester - PASS - 2.24 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: 3557 bytes --]

[-- Attachment #4: mgmt-tester.log --]
[-- Type: application/octet-stream, Size: 616827 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 --]

  reply	other threads:[~2021-07-22  7:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210722053858epcas5p2ecff386b264d4d8578a0ee454f898880@epcas5p2.samsung.com>
2021-07-22  5:38 ` [PATCH 0/4] " Ayush Garg
     [not found]   ` <CGME20210722053859epcas5p4b9441d43196ee1111b33b7c8d4827262@epcas5p4.samsung.com>
2021-07-22  5:38     ` [PATCH 1/4] Bluetooth: Fix incorrect parsing of LE_PHY params Ayush Garg
2021-07-22  7:20       ` bluez.test.bot [this message]
     [not found]   ` <CGME20210722053900epcas5p48430eb1335c3e566be02135e63749f33@epcas5p4.samsung.com>
2021-07-22  5:38     ` [PATCH 2/4] Bluetooth: Implement BT_PHY setsocket option Ayush Garg
     [not found]   ` <CGME20210722053902epcas5p4a38e75d06dcebec336ac1b1743c1a540@epcas5p4.samsung.com>
2021-07-22  5:38     ` [PATCH 3/4] Bluetooth: Add support for sending LE PHY Update event over mgmt Ayush Garg
2021-07-22 14:43       ` Marcel Holtmann
     [not found]   ` <CGME20210722053903epcas5p4e25daf9341dca446a0fbfd7b5d54324c@epcas5p4.samsung.com>
2021-07-22  5:38     ` [PATCH 4/4] Bluetooth: Update LE TX & RX PHYs when connection established Ayush Garg

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=60f91c2e.1c69fb81.4bb63.f27b@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=ayush.garg@samsung.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --subject='RE: Bluetooth: Support for LE Set Preferred PHY' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).