From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, mengshi.wu@oss.qualcomm.com
Subject: RE: gatt-client:Implement error handling for DB_OUT_OF_SYNC in GATT caching.
Date: Wed, 21 Jan 2026 00:59:04 -0800 (PST) [thread overview]
Message-ID: <69709558.050a0220.9983b.963c@mx.google.com> (raw)
In-Reply-To: <20260121083804.4010106-2-mengshi.wu@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 5208 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=1045032
---Test result---
Test Summary:
CheckPatch PENDING 0.34 seconds
GitLint PENDING 0.32 seconds
BuildEll PASS 19.85 seconds
BluezMake FAIL 13.55 seconds
MakeCheck FAIL 25.40 seconds
MakeDistcheck PASS 240.00 seconds
CheckValgrind FAIL 11.82 seconds
CheckSmatch FAIL 14.07 seconds
bluezmakeextell FAIL 11.37 seconds
IncrementalBuild PENDING 0.36 seconds
ScanBuild FAIL 14.03 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: BluezMake - FAIL
Desc: Build BlueZ
Output:
src/shared/att.c: In function ‘handle_rsp’:
src/shared/att.c:902:22: error: this statement may fall through [-Werror=implicit-fallthrough=]
902 | chan->pending_req = NULL;
| ^
src/shared/att.c:903:3: note: here
903 | case BT_ATT_RETRY_YES:
| ^~~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:7859: src/shared/libshared_mainloop_la-att.lo] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:4243: all] Error 2
##############################
Test: MakeCheck - FAIL
Desc: Run Bluez Make Check
Output:
src/shared/att.c: In function ‘handle_rsp’:
src/shared/att.c:902:22: error: this statement may fall through [-Werror=implicit-fallthrough=]
902 | chan->pending_req = NULL;
| ^
src/shared/att.c:903:3: note: here
903 | case BT_ATT_RETRY_YES:
| ^~~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:7586: src/shared/libshared_glib_la-att.lo] Error 1
make: *** [Makefile:11022: check] Error 2
##############################
Test: CheckValgrind - FAIL
Desc: Run Bluez Make Check with Valgrind
Output:
src/shared/att.c: In function ‘handle_rsp’:
src/shared/att.c:902:22: error: this statement may fall through [-Werror=implicit-fallthrough=]
902 | chan->pending_req = NULL;
| ^
src/shared/att.c:903:3: note: here
903 | case BT_ATT_RETRY_YES:
| ^~~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:7859: src/shared/libshared_mainloop_la-att.lo] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:11022: check] Error 2
##############################
Test: CheckSmatch - FAIL
Desc: Run smatch tool with source
Output:
src/shared/crypto.c:271:21: warning: Variable length array is used.
src/shared/crypto.c:272:23: warning: Variable length array is used.
src/shared/gatt-helpers.c:768:31: warning: Variable length array is used.
src/shared/gatt-helpers.c:846:31: warning: Variable length array is used.
src/shared/gatt-helpers.c:1339:31: warning: Variable length array is used.
src/shared/gatt-helpers.c:1370:23: warning: Variable length array is used.
src/shared/att.c: In function ‘handle_rsp’:
src/shared/att.c:902:22: error: this statement may fall through [-Werror=implicit-fallthrough=]
902 | chan->pending_req = NULL;
| ^
src/shared/att.c:903:3: note: here
903 | case BT_ATT_RETRY_YES:
| ^~~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:7859: src/shared/libshared_mainloop_la-att.lo] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:4243: all] Error 2
##############################
Test: bluezmakeextell - FAIL
Desc: Build Bluez with External ELL
Output:
src/shared/att.c: In function ‘handle_rsp’:
src/shared/att.c:902:22: error: this statement may fall through [-Werror=implicit-fallthrough=]
902 | chan->pending_req = NULL;
| ^
src/shared/att.c:903:3: note: here
903 | case BT_ATT_RETRY_YES:
| ^~~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:7859: src/shared/libshared_mainloop_la-att.lo] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:4243: all] Error 2
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
##############################
Test: ScanBuild - FAIL
Desc: Run Scan Build
Output:
src/shared/att.c: In function ‘handle_rsp’:
src/shared/att.c:902:22: error: this statement may fall through [-Werror=implicit-fallthrough=]
902 | chan->pending_req = NULL;
| ^
src/shared/att.c:903:3: note: here
903 | case BT_ATT_RETRY_YES:
| ^~~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:7859: src/shared/libshared_mainloop_la-att.lo] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:4243: all] Error 2
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-01-21 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 8:38 [PATCH v3 0/2] gatt-client:Implement error handling for DB_OUT_OF_SYNC in GATT caching Mengshi Wu
2026-01-21 8:38 ` [PATCH v3 1/2] shared/att: Implement ATT error retry mechanism with callback support Mengshi Wu
2026-01-21 8:59 ` bluez.test.bot [this message]
2026-01-21 18:15 ` Luiz Augusto von Dentz
2026-01-26 10:44 ` Mengshi Wu
2026-01-27 15:35 ` Luiz Augusto von Dentz
2026-02-02 2:46 ` Mengshi Wu
2026-01-21 8:38 ` [PATCH v3 2/2] gatt-client: Add DB_OUT_OF_SYNC error handling with retry mechanism Mengshi Wu
-- strict thread matches above, loose matches on Subject: below --
2026-01-05 10:38 [PATCH v2 1/1] gatt-client:Implement error handling for DB_OUT_OF_SYNC in GATT caching Mengshi Wu
2026-01-05 10:54 ` 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=69709558.050a0220.9983b.963c@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mengshi.wu@oss.qualcomm.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