From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: Fix bluetoothctl --help hanging if daemon isn't running
Date: Tue, 13 May 2025 04:03:48 -0700 (PDT) [thread overview]
Message-ID: <68232714.170a0220.11c97c.e53c@mx.google.com> (raw)
In-Reply-To: <20250513093913.396876-2-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 1879 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=962345
---Test result---
Test Summary:
CheckPatch PENDING 0.29 seconds
GitLint PENDING 0.30 seconds
BuildEll PASS 20.52 seconds
BluezMake PASS 2734.32 seconds
MakeCheck PASS 19.90 seconds
MakeDistcheck PASS 199.61 seconds
CheckValgrind PASS 277.78 seconds
CheckSmatch WARNING 305.92 seconds
bluezmakeextell PASS 129.21 seconds
IncrementalBuild PENDING 0.33 seconds
ScanBuild PASS 913.02 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/shell.c: note: in included file (through /usr/include/readline/readline.h):src/shared/shell.c: note: in included file (through /usr/include/readline/readline.h):src/shared/shell.c: note: in included file (through /usr/include/readline/readline.h):src/shared/shell.c: note: in included file (through /usr/include/readline/readline.h):src/shared/shell.c: note: in included file (through /usr/include/readline/readline.h):src/shared/shell.c: note: in included file (through /usr/include/readline/readline.h):
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-05-13 11:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 9:38 [BlueZ v4 0/9] Fix bluetoothctl --help hanging if daemon isn't running Bastien Nocera
2025-05-13 9:38 ` [BlueZ v4 1/9] client: Split installing submenu and doing I/O Bastien Nocera
2025-05-13 11:03 ` bluez.test.bot [this message]
2025-05-13 9:38 ` [BlueZ v4 2/9] client: Install submenus before contacting bluez daemon Bastien Nocera
2025-05-13 9:38 ` [BlueZ v4 3/9] shared/shell: Add function to handle early help calls Bastien Nocera
2025-05-13 9:38 ` [BlueZ v4 4/9] client: Fix --help hanging if bluetoothd is not running Bastien Nocera
2025-05-13 9:38 ` [BlueZ v4 5/9] shared/shell: Add pre_run menu callback Bastien Nocera
2025-05-13 9:38 ` [BlueZ v4 6/9] client: Port "admin" menu to pre_run Bastien Nocera
2025-05-13 9:38 ` [BlueZ v4 7/9] client: Port "player" " Bastien Nocera
2025-05-13 9:38 ` [BlueZ v4 8/9] client: Port "mgmt" " Bastien Nocera
2025-05-13 9:38 ` [BlueZ v4 9/9] client: Port "assistant" " Bastien Nocera
2025-05-13 15:51 ` Luiz Augusto von Dentz
2025-05-13 16:32 ` Bastien Nocera
2025-05-13 17:10 ` [BlueZ v4 0/9] Fix bluetoothctl --help hanging if daemon isn't running patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2024-10-22 14:10 [BlueZ v3 1/7] configure.ac: Update requirement to glib 2.34 Bastien Nocera
2024-10-22 18:29 ` Fix bluetoothctl --help hanging if daemon isn't running bluez.test.bot
2024-10-22 11:58 [BlueZ v2 1/7] configure.ac: Update requirement to glib 2.34 Bastien Nocera
2024-10-22 12:31 ` Fix bluetoothctl --help hanging if daemon isn't running bluez.test.bot
2024-10-22 12:40 ` Bastien Nocera
2024-10-22 14:43 ` Bastien Nocera
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=68232714.170a0220.11c97c.e53c@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hadess@hadess.net \
--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.