Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, valentin.kindschi@fiveco.ch
Subject: RE: Bluetooth: fix a permanent LE Set Advertising Parameters retry loop after a cancelled central connection
Date: Mon, 17 Aug 2026 07:21:12 -0700 (PDT)	[thread overview]
Message-ID: <6a8318d8.436e7ae1.2a65b4.b0de@mx.google.com> (raw)
In-Reply-To: <20260817132449.509304-2-valentin.kindschi@fiveco.ch>

[-- Attachment #1: Type: text/plain, Size: 3280 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=1147230

---Test result---

Test Summary:
CheckPatch                    PASS      1.11 seconds
VerifyFixes                   PASS      0.08 seconds
VerifySignedoff               PASS      0.08 seconds
GitLint                       FAIL      0.42 seconds
SubjectPrefix                 PASS      0.14 seconds
BuildKernel                   PASS      30.86 seconds
CheckAllWarning               PASS      29.99 seconds
CheckSparse                   PASS      28.66 seconds
BuildKernel32                 PASS      26.43 seconds
CheckKernelLLVM               SKIP      0.00 seconds
TestRunnerSetup               PASS      504.11 seconds
TestRunner_l2cap-tester       PASS      66.41 seconds
TestRunner_iso-tester         PASS      92.33 seconds
TestRunner_bnep-tester        PASS      20.05 seconds
TestRunner_mgmt-tester        FAIL      227.27 seconds
TestRunner_rfcomm-tester      PASS      26.15 seconds
TestRunner_sco-tester         PASS      35.67 seconds
TestRunner_ioctl-tester       PASS      27.18 seconds
TestRunner_mesh-tester        FAIL      26.36 seconds
TestRunner_smp-tester         PASS      24.43 seconds
TestRunner_userchan-tester    PASS      20.67 seconds
TestRunner_6lowpan-tester     PASS      24.35 seconds
IncrementalBuild              PASS      28.77 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v2,1/2] Bluetooth: hci_conn: only re-enable advertising after a failed peripheral connection

1: T1 Title exceeds max length (93>80): "[v2,1/2] Bluetooth: hci_conn: only re-enable advertising after a failed peripheral connection"
[v2,2/2] Bluetooth: hci_event: keep HCI_LE_ADV set when the host cancelled the connection

1: T1 Title exceeds max length (89>80): "[v2,2/2] Bluetooth: hci_event: keep HCI_LE_ADV set when the host cancelled the connection"
6: B3 Line contains hard tab characters (\t): "	/* All controllers implicitly stop advertising in the event of a"
7: B3 Line contains hard tab characters (\t): "	 * connection, so ensure that the state bit is cleared."
8: B3 Line contains hard tab characters (\t): "	 */"
9: B3 Line contains hard tab characters (\t): "	hci_dev_clear_flag(hdev, HCI_LE_ADV);"
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 501, Passed: 496 (99.0%), Failed: 1, Not Run: 4

Failed Test Cases
Read Exp Feature - Success                           Failed       0.256 seconds
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0

Failed Test Cases
Mesh - Send cancel - 1                               Timed out    2.508 seconds
Mesh - Send cancel - 2                               Timed out    1.984 seconds


https://github.com/bluez/bluetooth-next/pull/599

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-08-17 14:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 13:24 [PATCH v2 0/2] Bluetooth: fix a permanent LE Set Advertising Parameters retry loop after a cancelled central connection Valentin Kindschi
2026-08-17 13:24 ` [PATCH v2 1/2] Bluetooth: hci_conn: only re-enable advertising after a failed peripheral connection Valentin Kindschi
2026-08-17 14:21   ` bluez.test.bot [this message]
2026-08-17 13:24 ` [PATCH v2 2/2] Bluetooth: hci_event: keep HCI_LE_ADV set when the host cancelled the connection Valentin Kindschi
  -- strict thread matches above, loose matches on Subject: below --
2026-08-17 12:26 [PATCH 1/2] Bluetooth: hci_conn: only re-enable advertising after a failed peripheral connection Valentin Kindschi
2026-08-17 13:03 ` Bluetooth: fix a permanent LE Set Advertising Parameters retry loop after a cancelled central connection 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=6a8318d8.436e7ae1.2a65b4.b0de@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=valentin.kindschi@fiveco.ch \
    /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