From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [RESEND,BlueZ] test: functional: retry pairable when Busy
Date: Fri, 30 Oct 2026 13:47:26 -0700 (PDT) [thread overview]
Message-ID: <6ae5025e.24304cfb.14dc3f.cba0@mx.google.com> (raw)
In-Reply-To: <45f6af417f7b09d62d76bf128c1d6d22189bb2f7.1793381304.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 1406 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/series/1197366/
---Test result---
Test Summary:
CheckPatch PASS 0.45 seconds
GitLint FAIL 0.35 seconds
BuildEll PASS 21.55 seconds
BluezMake PASS 311.62 seconds
MakeCheck PASS 14.66 seconds
MakeDistcheck PASS 150.19 seconds
CheckValgrind PASS 250.31 seconds
CheckSmatch PASS 307.78 seconds
bluezmakeextell PASS 102.69 seconds
TestFunctional PASS 1190.80 seconds
IncrementalBuild PASS 319.20 seconds
ScanBuild PASS 1193.34 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[RESEND,BlueZ] test: functional: retry pairable when Busy
22: B3 Line contains hard tab characters (\t): "[bluetoothctl]> SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb"
23: B3 Line contains hard tab characters (\t): "[bluetoothctl]> SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb"
https://github.com/bluez/bluez/pull/2739
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-10-30 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 17:31 [PATCH RESEND BlueZ] test: functional: retry pairable when Busy Pauli Virtanen
2026-10-30 20:47 ` 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=6ae5025e.24304cfb.14dc3f.cba0@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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