From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v3,1/8] shared/lc3: Add QoS definitions
Date: Mon, 04 Dec 2023 16:43:27 -0800 (PST) [thread overview]
Message-ID: <656e722f.050a0220.c7ae0.2309@mx.google.com> (raw)
In-Reply-To: <20231204221527.2990674-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 6475 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=806820
---Test result---
Test Summary:
CheckPatch FAIL 5.64 seconds
GitLint PASS 2.80 seconds
BuildEll PASS 24.28 seconds
BluezMake PASS 734.05 seconds
MakeCheck PASS 11.65 seconds
MakeDistcheck PASS 160.10 seconds
CheckValgrind PASS 222.68 seconds
CheckSmatch PASS 327.47 seconds
bluezmakeextell PASS 102.44 seconds
IncrementalBuild PASS 5000.55 seconds
ScanBuild WARNING 976.07 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v3,2/8] test-bap: Introduce QoS tests for LC3
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#78:
Verify that a Unicast Client IUT can initiate a Config QoS operation for the
/github/workspace/src/src/13479151.patch total: 0 errors, 1 warnings, 992 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/13479151.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,v3,3/8] test-bap: Add SCC Config QoS, VS tests
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#77:
Verify that a Unicast Client IUT can initiate a Config QoS operation for a
/github/workspace/src/src/13479149.patch total: 0 errors, 1 warnings, 54 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/13479149.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,v3,4/8] test-bap: Add SCC Enable tests
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#77:
Verify that a Unicast Client IUT can initiate an Enable operation for an ASE
/github/workspace/src/src/13479150.patch total: 0 errors, 1 warnings, 116 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/13479150.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,v3,5/8] test-bap: Add SCC Disable tests
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#77:
Verify that a Unicast Client IUT can initiate a Disable operation for an ASE
/github/workspace/src/src/13479152.patch total: 0 errors, 1 warnings, 177 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/13479152.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,v3,7/8] test-bap: Add SCC Release tests
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#77:
Verify that a Unicast Client IUT can release an ASE by initiating a Release
/github/workspace/src/src/13479154.patch total: 0 errors, 1 warnings, 333 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/13479154.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,v3,8/8] test-bap: Add SCC Update Metadata tests
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#81:
The IUT successfully writes to the ASE Control Point characteristic with the
/github/workspace/src/src/13479155.patch total: 0 errors, 1 warnings, 151 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/13479155.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: ScanBuild - WARNING
Desc: Run Scan Build
Output:
src/shared/bap.c:4696:23: warning: Access to field 'type' results in a dereference of a null pointer (loaded from variable 'lpac')
if (!match.rpac && (lpac->type != BT_BAP_BCAST_SOURCE))
^~~~~~~~~~
1 warning generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-12-05 0:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 22:15 [PATCH BlueZ v3 1/8] shared/lc3: Add QoS definitions Luiz Augusto von Dentz
2023-12-04 22:15 ` [PATCH BlueZ v3 2/8] test-bap: Introduce QoS tests for LC3 Luiz Augusto von Dentz
2023-12-04 22:15 ` [PATCH BlueZ v3 3/8] test-bap: Add SCC Config QoS, VS tests Luiz Augusto von Dentz
2023-12-04 22:15 ` [PATCH BlueZ v3 4/8] test-bap: Add SCC Enable tests Luiz Augusto von Dentz
2023-12-04 22:15 ` [PATCH BlueZ v3 5/8] test-bap: Add SCC Disable tests Luiz Augusto von Dentz
2023-12-04 22:15 ` [PATCH BlueZ v3 6/8] shared/bap: Fix possible crash when freeing requests Luiz Augusto von Dentz
2023-12-04 22:15 ` [PATCH BlueZ v3 7/8] test-bap: Add SCC Release tests Luiz Augusto von Dentz
2023-12-04 22:15 ` [PATCH BlueZ v3 8/8] test-bap: Add SCC Update Metadata tests Luiz Augusto von Dentz
2023-12-05 0:43 ` bluez.test.bot [this message]
2023-12-05 3:40 ` [PATCH BlueZ v3 1/8] shared/lc3: Add QoS definitions 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=656e722f.050a0220.c7ae0.2309@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;
as well as URLs for NNTP newsgroup(s).