From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: [BlueZ] doc: Add missing btmon-cs doc to btmon.rst
Date: Thu, 16 Apr 2026 02:50:33 -0700 (PDT) [thread overview]
Message-ID: <69e0b0e9.050a0220.3d9965.1e2c@mx.google.com> (raw)
In-Reply-To: <20260416084750.3735103-1-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 1478 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=1081931
---Test result---
Test Summary:
CheckPatch PASS 0.24 seconds
GitLint PASS 0.19 seconds
BuildEll PASS 19.92 seconds
BluezMake PASS 648.95 seconds
MakeCheck PASS 18.27 seconds
MakeDistcheck FAIL 56.74 seconds
CheckValgrind PASS 291.92 seconds
CheckSmatch PASS 344.48 seconds
bluezmakeextell PASS 180.81 seconds
IncrementalBuild PASS 643.03 seconds
ScanBuild PASS 1012.54 seconds
Details
##############################
Test: MakeDistcheck - FAIL
Desc: Run Bluez Make Distcheck
Output:
../../doc/btmon.rst:770: (SEVERE/4) Problems with "include" directive path:
InputError: [Errno 2] No such file or directory: '../../doc/btmon-cs.rst'.
Exiting due to level-4 (SEVERE) system message.
make[2]: *** [Makefile:12191: doc/btmon.1] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:4156: all] Error 2
make: *** [Makefile:10690: distcheck] Error 1
https://github.com/bluez/bluez/pull/2044
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-04-16 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 8:47 [PATCH BlueZ] doc: Add missing btmon-cs doc to btmon.rst Bastien Nocera
2026-04-16 9:50 ` bluez.test.bot [this message]
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=69e0b0e9.050a0220.3d9965.1e2c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox