linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, brian.gix@intel.com
Subject: RE: Add Mesh functionality to net/bluetooth
Date: Tue, 10 May 2022 16:01:58 -0700 (PDT)	[thread overview]
Message-ID: <627aeee6.1c69fb81.3fcea.1001@mx.google.com> (raw)
In-Reply-To: <20220510214325.633935-2-brian.gix@intel.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      6.48 seconds
GitLint                       PASS      2.12 seconds
SubjectPrefix                 PASS      1.95 seconds
BuildKernel                   PASS      32.15 seconds
BuildKernel32                 PASS      28.72 seconds
Incremental Build with patchesPASS      65.13 seconds
TestRunner: Setup             PASS      468.98 seconds
TestRunner: l2cap-tester      PASS      17.39 seconds
TestRunner: bnep-tester       PASS      6.15 seconds
TestRunner: mgmt-tester       FAIL      101.05 seconds
TestRunner: rfcomm-tester     PASS      9.68 seconds
TestRunner: sco-tester        PASS      9.57 seconds
TestRunner: smp-tester        PASS      9.59 seconds
TestRunner: userchan-tester   PASS      6.42 seconds

Details
##############################
Test: CheckPatch - FAIL - 6.48 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
[v3,1/2] Bluetooth: Implement support for Mesh\CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#701: FILE: net/bluetooth/hci_request.c:2122:
+	if (!hci_dev_test_flag(hdev, HCI_LE_SCAN) ||
+			       hci_dev_test_flag(hdev, HCI_MESH))

ERROR:CODE_INDENT: code indent should use tabs where possible
#1515: FILE: net/bluetooth/mgmt.c:10062:
+^I^I              u8 addr_type, s8 rssi, u32 flags, u8 *eir,$

CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#1515: FILE: net/bluetooth/mgmt.c:10062:
+static void mesh_device_found(struct hci_dev *hdev, bdaddr_t *bdaddr,
+		              u8 addr_type, s8 rssi, u32 flags, u8 *eir,

total: 1 errors, 0 warnings, 2 checks, 1474 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.

NOTE: Whitespace errors detected.
      You may wish to use scripts/cleanpatch or scripts/cleanfile

/github/workspace/src/12845561.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.

[v3,2/2] Bluetooth: Add experimental wrapper for MGMT based mesh\CHECK:BRACES: Unbalanced braces around else statement
#244: FILE: net/bluetooth/mgmt.c:4537:
+	else {

total: 0 errors, 0 warnings, 1 checks, 182 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.

/github/workspace/src/12845560.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: TestRunner: mgmt-tester - FAIL - 101.05 seconds
Run test-runner with mgmt-tester
Total: 493, Passed: 492 (99.8%), Failed: 1, Not Run: 0

Failed Test Cases
Read Exp Feature - Success                           Failed       0.094 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-05-10 23:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 21:43 [PATCH v3 0/2] Add Mesh functionality to net/bluetooth Brian Gix
2022-05-10 21:43 ` [PATCH v3 1/2] Bluetooth: Implement support for Mesh Brian Gix
2022-05-10 23:01   ` bluez.test.bot [this message]
2022-05-11  6:14   ` kernel test robot
2022-05-10 21:43 ` [PATCH v3 2/2] Bluetooth: Add experimental wrapper for MGMT based mesh Brian Gix
  -- strict thread matches above, loose matches on Subject: below --
2022-09-01 19:19 [PATCH v7 1/2] Bluetooth: Implement support for Mesh Brian Gix
2022-09-01 20:01 ` Add Mesh functionality to net/bluetooth bluez.test.bot
2022-09-01 18:25 [PATCH v6 1/2] Bluetooth: Implement support for Mesh Brian Gix
2022-09-01 19:12 ` Add Mesh functionality to net/bluetooth bluez.test.bot
2022-07-20 19:45 [PATCH v5 1/2] Bluetooth: Implement support for Mesh Brian Gix
2022-07-20 21:09 ` Add Mesh functionality to net/bluetooth bluez.test.bot
2022-05-11 15:54 [PATCH v4 1/2] Bluetooth: Implement support for Mesh Brian Gix
2022-05-11 17:28 ` Add Mesh functionality to net/bluetooth bluez.test.bot
2022-05-09 22:05 [PATCH v2 1/2] Bluetooth: Implement support for Mesh Brian Gix
2022-05-09 23:08 ` Add Mesh functionality to net/bluetooth bluez.test.bot
2022-03-31 18:07 [PATCH 1/3] Bluetooth: Keep MGMT pending queue ordered FIFO Brian Gix
2022-03-31 19:13 ` Add Mesh functionality to net/bluetooth bluez.test.bot

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=627aeee6.1c69fb81.3fcea.1001@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=brian.gix@intel.com \
    --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 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).