From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, prathibha.madugonde@oss.qualcomm.com
Subject: RE: [BlueZ,v2] shared/rap: Add client ranging registration and notification parsing
Date: Thu, 21 May 2026 05:47:30 -0700 (PDT) [thread overview]
Message-ID: <6a0efee2.35fd6435.87d0d.f56e@mx.google.com> (raw)
In-Reply-To: <20260521103227.2479443-1-prathm@qti.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 1338 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=1098658
---Test result---
Test Summary:
CheckPatch PASS 1.00 seconds
GitLint PASS 0.34 seconds
BuildEll PASS 19.90 seconds
BluezMake PASS 601.40 seconds
MakeCheck PASS 0.99 seconds
MakeDistcheck FAIL 216.80 seconds
CheckValgrind PASS 202.65 seconds
CheckSmatch PASS 323.03 seconds
bluezmakeextell PASS 165.37 seconds
IncrementalBuild PASS 604.56 seconds
ScanBuild PASS 918.98 seconds
Details
##############################
Test: MakeDistcheck - FAIL
Desc: Run Bluez Make Distcheck
Output:
make[4]: *** [Makefile:10239: test-suite.log] Error 1
make[3]: *** [Makefile:10347: check-TESTS] Error 2
make[2]: *** [Makefile:10818: check-am] Error 2
make[1]: *** [Makefile:10820: check] Error 2
make: *** [Makefile:10741: distcheck] Error 1
https://github.com/bluez/bluez/pull/2142
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-05-21 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 10:32 [PATCH BlueZ v2] shared/rap: Add client ranging registration and notification parsing Prathibha Madugonde
2026-05-21 12:47 ` bluez.test.bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-21 7:18 Prathibha Madugonde
2026-05-21 9:42 ` [BlueZ,v2] " 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=6a0efee2.35fd6435.87d0d.f56e@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=prathibha.madugonde@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