From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, frederic.danis@collabora.com
Subject: RE: profiles: Add remote endpoint path to SelectProperties
Date: Tue, 30 Aug 2022 09:07:53 -0700 (PDT) [thread overview]
Message-ID: <630e35d9.020a0220.8c3cf.63d7@mx.google.com> (raw)
In-Reply-To: <20220830144734.55263-2-frederic.danis@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 2399 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=672467
---Test result---
Test Summary:
CheckPatch PASS 3.40 seconds
GitLint FAIL 2.32 seconds
Prep - Setup ELL PASS 26.45 seconds
Build - Prep PASS 0.68 seconds
Build - Configure PASS 8.09 seconds
Build - Make PASS 735.40 seconds
Make Check PASS 11.29 seconds
Make Check w/Valgrind PASS 286.38 seconds
Make Distcheck PASS 237.35 seconds
Build w/ext ELL - Configure PASS 8.26 seconds
Build w/ext ELL - Make PASS 82.60 seconds
Incremental Build w/ patches PASS 292.60 seconds
Scan Build WARNING 516.29 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint with rule in .gitlint
Output:
[BlueZ,v2,3/3] profiles: Fix function definition style
6: B3 Line contains hard tab characters (\t): "+ int (*select) (struct bt_bap_pac *lpac, struct bt_bap_pac *rpac,"
##############################
Test: Scan Build - WARNING
Desc: Run Scan Build with patches
Output:
*****************************************************************************
The bugs reported by the scan-build may or may not be caused by your patches.
Please check the list and fix the bugs if they are caused by your patch.
*****************************************************************************
profiles/audio/media.c:1459:6: warning: 8th function call argument is an uninitialized value
if (media_endpoint_create(adapter, sender, path, uuid, delay_reporting,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
profiles/audio/media.c:3005:3: warning: Use of memory after it is freed
release_endpoint(adapter->endpoints->data);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
profiles/audio/media.c:3008:3: warning: Use of memory after it is freed
media_player_destroy(adapter->players->data);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3 warnings generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-08-30 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 14:47 [PATCH BlueZ v2 0/3] profiles: Add remote endpoint path to SelectProperties Frédéric Danis
2022-08-30 14:47 ` [PATCH BlueZ v2 1/3] " Frédéric Danis
2022-08-30 16:07 ` bluez.test.bot [this message]
2022-08-30 14:47 ` [PATCH BlueZ v2 2/3] doc: " Frédéric Danis
2022-08-30 14:47 ` [PATCH BlueZ v2 3/3] profiles: Fix function definition style Frédéric Danis
2022-08-30 21:30 ` [PATCH BlueZ v2 0/3] profiles: Add remote endpoint path to SelectProperties patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2022-08-30 20:54 [PATCH BlueZ v3 1/3] " Frédéric Danis
2022-08-30 22:03 ` bluez.test.bot
2022-08-29 20:31 [PATCH BlueZ 1/2] " Frédéric Danis
2022-08-29 21:29 ` 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=630e35d9.020a0220.8c3cf.63d7@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=frederic.danis@collabora.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