linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, mahesh.talewad@nxp.com
Subject: RE: Implementation of AICS service and Unit Test cases
Date: Fri, 08 Dec 2023 05:41:41 -0800 (PST)	[thread overview]
Message-ID: <65731d15.0c0a0220.4e074.433f@mx.google.com> (raw)
In-Reply-To: <20231208114258.133709-2-mahesh.talewad@nxp.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      3.21 seconds
GitLint                       FAIL      1.13 seconds
BuildEll                      PASS      24.11 seconds
BluezMake                     PASS      713.67 seconds
MakeCheck                     PASS      12.20 seconds
MakeDistcheck                 PASS      161.09 seconds
CheckValgrind                 PASS      224.75 seconds
CheckSmatch                   PASS      329.37 seconds
bluezmakeextell               PASS      106.51 seconds
IncrementalBuild              PASS      2017.55 seconds
ScanBuild                     PASS      933.73 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v2,3/3] unit/test-vcp.c: AICS unit test case implementation
WARNING:TYPO_SPELLING: 'Implementated' may be misspelled - perhaps 'Implemented'?
#113: 
- Implementated 15-Mandatory AICS Unit Test cases.
  ^^^^^^^^^^^^^

/github/workspace/src/src/13485348.patch total: 0 errors, 1 warnings, 1570 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/src/13485348.patch 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 - FAIL
Desc: Run gitlint
Output:
[BlueZ,v2,1/3] - Added AICS Characteristics UUID(s).

WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
1: T3 Title has trailing punctuation (.): "[BlueZ,v2,1/3] - Added AICS Characteristics UUID(s)."
[BlueZ,v2,2/3] - Code Implementation related Service- AICS

WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
4: B3 Line contains hard tab characters (\t): "	AICS_v1.0.pdf"
6: B3 Line contains hard tab characters (\t): "	mandatory testcases passed."
[BlueZ,v2,3/3] unit/test-vcp.c: AICS unit test case implementation

WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
7: B3 Line contains hard tab characters (\t): "	AICS.TS.p0.pdf"


---
Regards,
Linux Bluetooth


  reply	other threads:[~2023-12-08 13:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 11:42 [PATCH BlueZ v2 0/3] Implementation of AICS service and Unit Test cases Mahesh Talewad
2023-12-08 11:42 ` [PATCH BlueZ v2 1/3] - Added AICS Characteristics UUID(s) Mahesh Talewad
2023-12-08 13:41   ` bluez.test.bot [this message]
2023-12-08 11:42 ` [PATCH BlueZ v2 2/3] - Code Implementation related Service- AICS Mahesh Talewad
2023-12-08 11:42 ` [PATCH BlueZ v2 3/3] unit/test-vcp.c: AICS unit test case implementation Mahesh Talewad
2023-12-18 20:50 ` [PATCH BlueZ v2 0/3] Implementation of AICS service and Unit Test cases patchwork-bot+bluetooth

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=65731d15.0c0a0220.4e074.433f@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mahesh.talewad@nxp.com \
    /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).