From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, sgrubb@redhat.com
Subject: RE: Fix various memory leaks
Date: Wed, 12 May 2021 16:06:52 -0700 (PDT) [thread overview]
Message-ID: <609c5f8c.1c69fb81.3fc3d.8a60@mx.google.com> (raw)
In-Reply-To: <20210512173523.622e0ade@ivy-bridge>
[-- Attachment #1: Type: text/plain, Size: 3354 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=481531
---Test result---
Test Summary:
CheckPatch PASS 1.10 seconds
GitLint PASS 0.61 seconds
Prep - Setup ELL PASS 40.35 seconds
Build - Prep PASS 0.10 seconds
Build - Configure PASS 6.98 seconds
Build - Make FAIL 154.20 seconds
Make Check FAIL 0.63 seconds
Make Distcheck PASS 208.68 seconds
Build w/ext ELL - Configure PASS 7.17 seconds
Build w/ext ELL - Make FAIL 145.96 seconds
Details
##############################
Test: CheckPatch - PASS
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
##############################
Test: GitLint - PASS
Desc: Run gitlint with rule in .gitlint
##############################
Test: Prep - Setup ELL - PASS
Desc: Clone, build, and install ELL
##############################
Test: Build - Prep - PASS
Desc: Prepare environment for build
##############################
Test: Build - Configure - PASS
Desc: Configure the BlueZ source tree
##############################
Test: Build - Make - FAIL
Desc: Build the BlueZ source tree
Output:
obexd/plugins/filesystem.c: In function ‘capability_open’:
obexd/plugins/filesystem.c:418:18: error: assignment to ‘GString *’ {aka ‘struct _GString *’} from incompatible pointer type ‘char *’ [-Werror=incompatible-pointer-types]
418 | object->buffer = buf;
| ^
cc1: all warnings being treated as errors
make[1]: *** [Makefile:7907: obexd/plugins/obexd-filesystem.o] Error 1
make: *** [Makefile:4128: all] Error 2
##############################
Test: Make Check - FAIL
Desc: Run 'make check'
Output:
obexd/plugins/filesystem.c: In function ‘capability_open’:
obexd/plugins/filesystem.c:418:18: error: assignment to ‘GString *’ {aka ‘struct _GString *’} from incompatible pointer type ‘char *’ [-Werror=incompatible-pointer-types]
418 | object->buffer = buf;
| ^
cc1: all warnings being treated as errors
make[1]: *** [Makefile:7907: obexd/plugins/obexd-filesystem.o] Error 1
make: *** [Makefile:10398: check] Error 2
##############################
Test: Make Distcheck - PASS
Desc: Run distcheck to check the distribution
##############################
Test: Build w/ext ELL - Configure - PASS
Desc: Configure BlueZ source with '--enable-external-ell' configuration
##############################
Test: Build w/ext ELL - Make - FAIL
Desc: Build BlueZ source with '--enable-external-ell' configuration
Output:
obexd/plugins/filesystem.c: In function ‘capability_open’:
obexd/plugins/filesystem.c:418:18: error: assignment to ‘GString *’ {aka ‘struct _GString *’} from incompatible pointer type ‘char *’ [-Werror=incompatible-pointer-types]
418 | object->buffer = buf;
| ^
cc1: all warnings being treated as errors
make[1]: *** [Makefile:7907: obexd/plugins/obexd-filesystem.o] Error 1
make: *** [Makefile:4128: all] Error 2
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2021-05-12 23:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 21:35 [Bluez PATCH 1/6] Fix leak in mesh Steve Grubb
2021-05-12 23:06 ` bluez.test.bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-14 13:58 Steve Grubb
2021-05-14 14:11 ` Fix various memory leaks 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=609c5f8c.1c69fb81.3fc3d.8a60@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sgrubb@redhat.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).