From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: BAP Server test cases
Date: Fri, 04 Apr 2025 14:18:08 -0700 (PDT) [thread overview]
Message-ID: <67f04c90.170a0220.11788.e974@mx.google.com> (raw)
In-Reply-To: <20250404193959.359008-2-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2365 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=950067
---Test result---
Test Summary:
CheckPatch PENDING 0.35 seconds
GitLint PENDING 0.29 seconds
BuildEll PASS 39.69 seconds
BluezMake PASS 1765.80 seconds
MakeCheck PASS 15.09 seconds
MakeDistcheck PASS 171.81 seconds
CheckValgrind PASS 236.63 seconds
CheckSmatch WARNING 300.08 seconds
bluezmakeextell PASS 107.98 seconds
IncrementalBuild PENDING 0.30 seconds
ScanBuild PASS 865.62 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
src/shared/bap.c:314:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structuressrc/shared/bap.c:314:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structuressrc/shared/bap.c:314:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structuressrc/shared/bap.c:314:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structuressrc/shared/bap.c:314:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structuressrc/shared/bap.c:314:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structures
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-04-04 21:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 19:39 [PATCH BlueZ v1 00/11] BAP Server test cases Luiz Augusto von Dentz
2025-04-04 19:39 ` [PATCH BlueZ v1 01/11] test-bap: Introduce DISC tests for LC3 Luiz Augusto von Dentz
2025-04-04 21:18 ` bluez.test.bot [this message]
2025-04-04 19:39 ` [PATCH BlueZ v1 02/11] test-bap: Introduce USR/SCC " Luiz Augusto von Dentz
2025-04-04 19:39 ` [PATCH BlueZ v1 03/11] test-bap: Introduce USR/SCC - VS " Luiz Augusto von Dentz
2025-04-04 19:39 ` [PATCH BlueZ v1 04/11] test-bap: Introduce USR/SCC QoS " Luiz Augusto von Dentz
2025-04-04 19:39 ` [PATCH BlueZ v1 05/11] test-bap: Introduce USR/SCC QoS tests for VS Luiz Augusto von Dentz
2025-04-04 19:39 ` [PATCH BlueZ v1 06/11] test-bap: Introduce USR/SCC Enable tests for LC3 Luiz Augusto von Dentz
2025-04-04 19:39 ` [PATCH BlueZ v1 07/11] " Luiz Augusto von Dentz
2025-04-04 19:39 ` [PATCH BlueZ v1 08/11] shared/bap: Fix not always sending Releasing state Luiz Augusto von Dentz
2025-04-04 19:39 ` [PATCH BlueZ v1 09/11] test-bap: Introduce USR/SCC Release tests for LC3 Luiz Augusto von Dentz
2025-04-04 19:39 ` [PATCH BlueZ v1 10/11] shared/bap: Fix not sending ASE Notication in case of Metadata update Luiz Augusto von Dentz
2025-04-04 19:39 ` [PATCH BlueZ v1 11/11] test-bap: Introduce USR/SCC Metadata tests for LC3 Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2025-04-07 20:01 [PATCH BlueZ v2 01/15] test-bap: Introduce DISC " Luiz Augusto von Dentz
2025-04-07 21:37 ` BAP Server test cases 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=67f04c90.170a0220.11788.e974@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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