All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, benquike@gmail.com
Subject: RE: Bluetooth: MGMT: fix mesh_tx leak on hci_cmd_sync_queue() failure
Date: Sat, 19 Sep 2026 08:33:03 -0700 (PDT)	[thread overview]
Message-ID: <6aaeab2f.1290c124.f9130.9e7b@mx.google.com> (raw)
In-Reply-To: <20260919115436.3998954-1-benquike@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2736 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/1169247/

---Test result---

Test Summary:
CheckPatch                    PASS      0.70 seconds
VerifyFixes                   PASS      0.11 seconds
VerifySignedoff               PASS      0.11 seconds
GitLint                       FAIL      0.29 seconds
SubjectPrefix                 PASS      0.10 seconds
BuildKernel                   PASS      28.95 seconds
CheckAllWarning               PASS      32.94 seconds
CheckSparse                   PASS      35.66 seconds
BuildKernel32                 PASS      29.20 seconds
CheckKernelLLVM               PASS      33.21 seconds
TestRunnerSetup               PASS      782.58 seconds
TestRunner_mgmt-tester        FAIL      61.32 seconds
TestRunner_mesh-tester        FAIL      7.82 seconds
IncrementalBuild              PASS      29.25 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: MGMT: fix mesh_tx leak on hci_cmd_sync_queue() failure

6: B3 Line contains hard tab characters (\t): "	sending = hci_dev_test_flag(hdev, HCI_MESH_SENDING);"
7: B3 Line contains hard tab characters (\t): "	mesh_tx = mgmt_mesh_add(sk, hdev, send, len);"
9: B3 Line contains hard tab characters (\t): "	if (!mesh_tx)"
10: B3 Line contains hard tab characters (\t): "		err = -ENOMEM;"
11: B3 Line contains hard tab characters (\t): "	else if (!sending)"
12: B3 Line contains hard tab characters (\t): "		err = hci_cmd_sync_queue(hdev, mesh_send_sync, mesh_tx,"
13: B3 Line contains hard tab characters (\t): "					 mesh_send_start_complete);"
19: B3 Line contains hard tab characters (\t): "	if (mesh_tx) {"
20: B3 Line contains hard tab characters (\t): "		if (sending)"
21: B3 Line contains hard tab characters (\t): "			mgmt_mesh_remove(mesh_tx);"
22: B3 Line contains hard tab characters (\t): "	}"
##############################
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.022 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.403 seconds
Mesh - Send cancel - 2                               Timed out    1.999 seconds


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

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-09-19 15:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-19 11:54 [PATCH] Bluetooth: MGMT: fix mesh_tx leak on hci_cmd_sync_queue() failure Hui Peng
2026-09-19 15:33 ` bluez.test.bot [this message]
2026-10-06 20:18 ` Iaroslav Voitovych

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=6aaeab2f.1290c124.f9130.9e7b@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=benquike@gmail.com \
    --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.