All of lore.kernel.org
 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: Wed, 11 May 2022 10:28:49 -0700 (PDT)	[thread overview]
Message-ID: <627bf251.1c69fb81.32174.755a@mx.google.com> (raw)
In-Reply-To: <20220511155412.740249-2-brian.gix@intel.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      6.70 seconds
GitLint                       PASS      2.25 seconds
SubjectPrefix                 PASS      1.88 seconds
BuildKernel                   PASS      33.01 seconds
BuildKernel32                 PASS      31.50 seconds
Incremental Build with patchesPASS      68.01 seconds
TestRunner: Setup             PASS      491.17 seconds
TestRunner: l2cap-tester      PASS      18.07 seconds
TestRunner: bnep-tester       PASS      6.09 seconds
TestRunner: mgmt-tester       FAIL      107.31 seconds
TestRunner: rfcomm-tester     PASS      9.69 seconds
TestRunner: sco-tester        PASS      9.54 seconds
TestRunner: smp-tester        PASS      9.83 seconds
TestRunner: userchan-tester   PASS      6.59 seconds

Details
##############################
Test: CheckPatch - FAIL - 6.70 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
[v4,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/12846409.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 - 107.31 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.140 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-05-11 17:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 15:54 [PATCH v4 0/2] Add Mesh functionality to net/bluetooth Brian Gix
2022-05-11 15:54 ` [PATCH v4 1/2] Bluetooth: Implement support for Mesh Brian Gix
2022-05-11 17:28   ` bluez.test.bot [this message]
2022-05-11 21:08   ` Luiz Augusto von Dentz
2022-05-12 22:39     ` Gix, Brian
2022-05-11 15:54 ` [PATCH v4 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-10 21:43 [PATCH v3 1/2] Bluetooth: Implement support for Mesh Brian Gix
2022-05-10 23:01 ` 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=627bf251.1c69fb81.32174.755a@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 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.