public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, inga.stotland@intel.com
Subject: RE: Convert tester tools to use ELL
Date: Tue, 08 Jun 2021 21:05:38 -0700 (PDT)	[thread overview]
Message-ID: <60c03e12.1c69fb81.54894.51f3@mx.google.com> (raw)
In-Reply-To: <20210606063719.339794-2-inga.stotland@intel.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      5.15 seconds
GitLint                       PASS      1.19 seconds
Prep - Setup ELL              PASS      43.38 seconds
Build - Prep                  PASS      0.12 seconds
Build - Configure             PASS      7.34 seconds
Build - Make                  PASS      177.48 seconds
Make Check                    PASS      8.32 seconds
Make Distcheck                PASS      207.15 seconds
Build w/ext ELL - Configure   PASS      7.31 seconds
Build w/ext ELL - Make        PASS      165.37 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
shared/bttester: tester framework wrapper to use ELL
WARNING:PREFER_DEFINED_ATTRIBUTE_MACRO: Prefer __packed over __attribute__((packed))
#330: FILE: src/shared/bttester.h:16:
+#define __packed __attribute__((packed))

WARNING:PREFER_DEFINED_ATTRIBUTE_MACRO: Prefer __printf(1, 2) over __attribute__((format(printf, 1, 2)))
#340: FILE: src/shared/bttester.h:26:
+				__attribute__((format(printf, 1, 2)));

WARNING:PREFER_DEFINED_ATTRIBUTE_MACRO: Prefer __printf(1, 2) over __attribute__((format(printf, 1, 2)))
#342: FILE: src/shared/bttester.h:28:
+				__attribute__((format(printf, 1, 2)));

WARNING:PREFER_DEFINED_ATTRIBUTE_MACRO: Prefer __printf(1, 2) over __attribute__((format(printf, 1, 2)))
#344: FILE: src/shared/bttester.h:30:
+				__attribute__((format(printf, 1, 2)));

- total: 0 errors, 4 warnings, 321 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.

"[PATCH] shared/bttester: tester framework wrapper to use ELL" has style problems, please review.

NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.


##############################
Test: GitLint - PASS
Desc: Run gitlint with rule in .gitlint

##############################
Test: Prep - Setup ELL - PASS
Desc: Clone, build, and install ELL

##############################
Test: Build - Prep - PASS
Desc: Prepare environment for build

##############################
Test: Build - Configure - PASS
Desc: Configure the BlueZ source tree

##############################
Test: Build - Make - PASS
Desc: Build the BlueZ source tree

##############################
Test: Make Check - PASS
Desc: Run 'make check'

##############################
Test: Make Distcheck - PASS
Desc: Run distcheck to check the distribution

##############################
Test: Build w/ext ELL - Configure - PASS
Desc: Configure BlueZ source with '--enable-external-ell' configuration

##############################
Test: Build w/ext ELL - Make - PASS
Desc: Build BlueZ source with '--enable-external-ell' configuration



---
Regards,
Linux Bluetooth


  reply	other threads:[~2021-06-09  4:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-06  6:37 [PATCH BlueZ 00/11] Convert tester tools to use ELL Inga Stotland
2021-06-06  6:37 ` [PATCH BlueZ 01/11] shared/bttester: tester framework wrapper " Inga Stotland
2021-06-09  4:05   ` bluez.test.bot [this message]
2021-06-06  6:37 ` [PATCH BlueZ 02/11] emulator/hciemu: Create ELL based version of hciemu Inga Stotland
2021-06-06  6:37 ` [PATCH BlueZ 03/11] tools/gap-tester: Convert to use ELL library Inga Stotland
2021-06-06  6:37 ` [PATCH BlueZ 04/11] tools/sco-tester: " Inga Stotland
2021-06-06  6:37 ` [PATCH BlueZ 05/11] tools/userchan-tester: " Inga Stotland
2021-06-06  6:37 ` [PATCH BlueZ 06/11] tools/smp-tester: " Inga Stotland
2021-06-06  6:37 ` [PATCH BlueZ 07/11] tools/bnep-tester: " Inga Stotland
2021-06-06  6:37 ` [PATCH BlueZ 08/11] tools/l2cap-tester: " Inga Stotland
2021-06-06  6:37 ` [PATCH BlueZ 09/11] tools/mgmt-tester: " Inga Stotland
2021-06-06  6:37 ` [PATCH BlueZ 10/11] tools/rfcomm-tester: " Inga Stotland
2021-06-06  6:37 ` [PATCH BlueZ 11/11] tools/hci-tester: " Inga Stotland
2021-06-07 23:50 ` [PATCH BlueZ 00/11] Convert tester tools to use ELL Luiz Augusto von Dentz
  -- strict thread matches above, loose matches on Subject: below --
2021-05-07  5:56 [RFC BlueZ v2 01/11] shared/bttester: tester framework wrapper " Inga Stotland
2021-05-07  6:47 ` Convert tester tools " 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=60c03e12.1c69fb81.54894.51f3@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=inga.stotland@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