From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, josephsih@chromium.org
Subject: RE: [BlueZ,v4,1/8] doc: Introduce the quality report command and event
Date: Tue, 15 Feb 2022 07:58:37 -0800 (PST) [thread overview]
Message-ID: <620bcdad.1c69fb81.5bcba.62d5@mx.google.com> (raw)
In-Reply-To: <20220215133636.2827039-1-josephsih@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 2518 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=614538
---Test result---
Test Summary:
CheckPatch PASS 12.28 seconds
GitLint FAIL 8.19 seconds
Prep - Setup ELL PASS 46.49 seconds
Build - Prep PASS 0.74 seconds
Build - Configure PASS 9.54 seconds
Build - Make PASS 1459.17 seconds
Make Check PASS 12.08 seconds
Make Check w/Valgrind PASS 523.50 seconds
Make Distcheck PASS 264.01 seconds
Build w/ext ELL - Configure PASS 9.98 seconds
Build w/ext ELL - Make PASS 1392.62 seconds
Incremental Build with patchesFAIL 4378.04 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint with rule in .gitlint
Output:
[BlueZ,v4,2/8] lib: Add structures and constants for quality report command and event
1: T1 Title exceeds max length (85>80): "[BlueZ,v4,2/8] lib: Add structures and constants for quality report command and event"
##############################
Test: Incremental Build with patches - FAIL
Desc: Incremental build per patch in the series
Output:
tools/mgmt-tester.c: In function ‘main’:
tools/mgmt-tester.c:12364:5: note: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’, retrying without
12364 | int main(int argc, char *argv[])
| ^~~~
unit/test-avdtp.c: In function ‘main’:
unit/test-avdtp.c:766:5: note: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’, retrying without
766 | int main(int argc, char *argv[])
| ^~~~
unit/test-avrcp.c: In function ‘main’:
unit/test-avrcp.c:989:5: note: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’, retrying without
989 | int main(int argc, char *argv[])
| ^~~~
src/adapter.c:9744:6: error: no previous declaration for ‘is_quality_report_supported’ [-Werror=missing-declarations]
9744 | bool is_quality_report_supported(struct btd_adapter *adapter)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:10187: src/bluetoothd-adapter.o] Error 1
make: *** [Makefile:4308: all] Error 2
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-02-15 15:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 13:36 [BlueZ PATCH v4 1/8] doc: Introduce the quality report command and event Joseph Hwang
2022-02-15 13:36 ` [BlueZ PATCH v4 2/8] lib: Add structures and constants for " Joseph Hwang
2022-02-15 13:36 ` [BlueZ PATCH v4 3/8] adapter: enable quality report via MGMT_OP_SET_QUALITY_REPORT Joseph Hwang
2022-02-15 13:36 ` [BlueZ PATCH v4 4/8] adapter: support AOSP MGMT_EV_QUALITY_REPORT Joseph Hwang
2022-02-15 13:36 ` [BlueZ PATCH v4 5/8] adapter: support Intel MGMT_EV_QUALITY_REPORT Joseph Hwang
2022-02-17 12:21 ` Marcel Holtmann
2022-03-05 8:00 ` Joseph Hwang
2022-02-15 13:36 ` [BlueZ PATCH v4 6/8] tools/btmgmt: fix quality report command Joseph Hwang
2022-02-15 13:36 ` [BlueZ PATCH v4 7/8] monitor: print quality report cmd Joseph Hwang
2022-02-15 13:36 ` [BlueZ PATCH v4 8/8] monitor: packet: add missing decodings of MGMT commands to todo Joseph Hwang
2022-02-15 15:58 ` bluez.test.bot [this message]
2022-02-17 12:13 ` [BlueZ PATCH v4 1/8] doc: Introduce the quality report command and event Marcel Holtmann
2022-03-05 7:57 ` Joseph Hwang
2022-03-05 21:53 ` Marcel Holtmann
2022-03-06 4:23 ` Joseph Hwang
2022-03-06 8:49 ` Marcel Holtmann
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=620bcdad.1c69fb81.5bcba.62d5@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=josephsih@chromium.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.