From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, arun@asymptotic.io
Subject: RE: ASHA plugin
Date: Wed, 15 May 2024 16:48:08 -0700 (PDT) [thread overview]
Message-ID: <664549b8.170a0220.8216e.eadc@mx.google.com> (raw)
In-Reply-To: <20240515201552.1831618-2-arun@asymptotic.io>
[-- Attachment #1: Type: text/plain, Size: 2063 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=853506
---Test result---
Test Summary:
CheckPatch FAIL 2.36 seconds
GitLint PASS 1.07 seconds
BuildEll PASS 24.44 seconds
BluezMake PASS 1666.53 seconds
MakeCheck PASS 13.26 seconds
MakeDistcheck PASS 178.56 seconds
CheckValgrind PASS 248.43 seconds
CheckSmatch PASS 354.05 seconds
bluezmakeextell PASS 119.54 seconds
IncrementalBuild PASS 7792.07 seconds
ScanBuild WARNING 1012.28 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v3,3/5] test: Add a script to test ASHA
ERROR:EXECUTE_PERMISSIONS: do not set execute permissions for source files
#103: FILE: test/simple-asha
/github/workspace/src/src/13665531.patch total: 1 errors, 0 warnings, 158 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/13665531.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:
profiles/audio/media.c:1048:7: warning: Use of memory after it is freed
if (req->cb != pac_select_cb) {
^~~~~~~
1 warning generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-05-15 23:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 20:15 [PATCH BlueZ,v3 0/5] ASHA plugin Arun Raghavan
2024-05-15 20:15 ` [PATCH BlueZ,v3 1/5] src/shared: Add initial implementation for an ASHA profile Arun Raghavan
2024-05-15 23:48 ` bluez.test.bot [this message]
2024-05-15 20:15 ` [PATCH BlueZ,v3 2/5] profiles/audio: Add an ASHA plugin Arun Raghavan
2024-05-15 20:15 ` [PATCH BlueZ,v3 3/5] test: Add a script to test ASHA Arun Raghavan
2024-05-15 20:15 ` [PATCH BlueZ,v3 4/5] gitignore: Add compile_commands.json Arun Raghavan
2024-05-15 20:15 ` [PATCH BlueZ,v3 5/5] gitignore: Add __pycache__ Arun Raghavan
-- strict thread matches above, loose matches on Subject: below --
2024-06-10 22:35 [PATCH BlueZ,v9 1/3] src/shared: Add initial implementation for an ASHA profile Arun Raghavan
2024-06-10 22:53 ` ASHA plugin bluez.test.bot
2024-05-23 15:52 [PATCH BlueZ,v8 1/5] src/shared: Add initial implementation for an ASHA profile Arun Raghavan
2024-05-23 18:05 ` ASHA plugin bluez.test.bot
2024-05-23 10:29 [PATCH BlueZ,v7 1/6] src/shared: Add initial implementation for an ASHA profile Arun Raghavan
2024-05-23 12:27 ` ASHA plugin bluez.test.bot
2024-05-16 19:38 [PATCH BlueZ,v6 1/5] src/shared: Add initial implementation for an ASHA profile Arun Raghavan
2024-05-16 23:26 ` ASHA plugin bluez.test.bot
2024-05-16 14:54 [PATCH BlueZ,v4 1/5] src/shared: Add initial implementation for an ASHA profile Arun Raghavan
2024-05-16 18:28 ` ASHA plugin bluez.test.bot
2024-05-09 2:26 [PATCH BlueZ,v2 1/4] profiles: Add initial code for an " Arun Raghavan
2024-05-09 2:57 ` bluez.test.bot
2024-05-08 15:46 [PATCH BlueZ 1/5] profiles: Add initial code for an " Arun Raghavan
2024-05-08 17:36 ` 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=664549b8.170a0220.8216e.eadc@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=arun@asymptotic.io \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).