From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v2,1/5] shared/util: Add GMAP related UUIDs
Date: Wed, 22 Nov 2023 12:57:14 -0800 (PST) [thread overview]
Message-ID: <655e6b2a.c80a0220.718a1.0d5a@mx.google.com> (raw)
In-Reply-To: <20231122190649.879386-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3710 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=803411
---Test result---
Test Summary:
CheckPatch FAIL 2.19 seconds
GitLint FAIL 1.61 seconds
BuildEll PASS 24.11 seconds
BluezMake PASS 556.69 seconds
MakeCheck PASS 11.10 seconds
MakeDistcheck PASS 149.71 seconds
CheckValgrind PASS 209.27 seconds
CheckSmatch WARNING 317.26 seconds
bluezmakeextell PASS 96.60 seconds
IncrementalBuild PASS 2527.23 seconds
ScanBuild PASS 892.97 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v2,1/5] shared/util: Add GMAP related UUIDs
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#72:
[1] https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=576496
/github/workspace/src/src/13465382.patch total: 0 errors, 1 warnings, 18 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/13465382.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.
[BlueZ,v2,5/5] client/player: Add presets from GMAP
ERROR:SPACING: need consistent spacing around '*' (ctx:VxW)
#194: FILE: client/player.c:1525:
+ LC3_7_5_UNFRAMED(2* 75u, 1u, 15u, 10000u)),
^
ERROR:SPACING: need consistent spacing around '*' (ctx:VxW)
#198: FILE: client/player.c:1529:
+ LC3_10_UNFRAMED(2* 100u, 1u, 20u, 10000u)),
^
/github/workspace/src/src/13465386.patch total: 2 errors, 0 warnings, 105 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/13465386.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/5] shared/util: Add GMAP related UUIDs
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
8: B1 Line exceeds max length (94>80): "[2] https://www.bluetooth.com/wp-content/uploads/Files/Specification/Assigned_Numbers.pdf?id=3"
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
monitor/att.c: note: in included file:monitor/display.h:82:26: warning: Variable length array is used.
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-11-22 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 19:06 [PATCH BlueZ v2 1/5] shared/util: Add GMAP related UUIDs Luiz Augusto von Dentz
2023-11-22 19:06 ` [PATCH BlueZ v2 2/5] monitor/att: Add GMAS attribute decoders Luiz Augusto von Dentz
2023-11-22 19:06 ` [PATCH BlueZ v2 3/5] iso-tester: Add presets from GMAP Luiz Augusto von Dentz
2023-11-22 19:06 ` [PATCH BlueZ v2 4/5] isotest: " Luiz Augusto von Dentz
2023-11-22 19:06 ` [PATCH BlueZ v2 5/5] client/player: " Luiz Augusto von Dentz
2023-11-22 20:57 ` bluez.test.bot [this message]
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=655e6b2a.c80a0220.718a1.0d5a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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