Linux bluetooth development
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [v3,1/1] Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel
Date: Wed, 16 Sep 2026 11:44:33 +0100	[thread overview]
Message-ID: <20260916104433.GN11487@google.com> (raw)
In-Reply-To: <6aa94072.2842b724.2f298f.7f4a@mx.google.com>

On Tue, 15 Sep 2026, bluez.test.bot@gmail.com wrote:

> 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/1165484/
> 
> ---Test result---
> 
> Test Summary:
> CheckPatch                    PASS      0.77 seconds
> VerifyFixes                   PASS      0.12 seconds
> VerifySignedoff               PASS      0.11 seconds
> GitLint                       FAIL      0.41 seconds
> SubjectPrefix                 PASS      5.05 seconds
> BuildKernel                   PASS      28.89 seconds
> CheckAllWarning               PASS      33.54 seconds
> CheckSparse                   PASS      36.17 seconds
> BuildKernel32                 PASS      29.54 seconds
> CheckKernelLLVM               PASS      34.56 seconds
> TestRunnerSetup               PASS      745.28 seconds
> TestRunner_mgmt-tester        FAIL      9.35 seconds
> TestRunner_mesh-tester        FAIL      8.15 seconds
> IncrementalBuild              PASS      27.99 seconds
> 
> Details
> ##############################
> Test: GitLint - FAIL
> Desc: Run gitlint
> Output:
> [v3,1/1] Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel
> 
> 30: B1 Line exceeds max length (105>80): "  - Advance mesh queue on error in mesh_send_start_complete(), skipping -ECANCELED to avoid self-deadlock"

This is just the change log and can be ignored.

> ##############################
> Test: TestRunner_mgmt-tester - FAIL
> Desc: Run mgmt-tester with test-runner
> Output:
> No test result found
> ##############################
> Test: TestRunner_mesh-tester - FAIL
> Desc: Run mesh-tester with test-runner
> Output:
> No test result found

So, is this my problem or the harness's?

> https://github.com/bluez/bluetooth-next/pull/772
> 
> ---
> Regards,
> Linux Bluetooth
> 


-- 
Lee Jones

  reply	other threads:[~2026-09-16 10:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 12:08 [PATCH v3 1/1] Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel Lee Jones
2026-09-15 12:56 ` [v3,1/1] " bluez.test.bot
2026-09-16 10:44   ` Lee Jones [this message]
2026-09-16 17:50 ` [PATCH v3 1/1] " patchwork-bot+bluetooth

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=20260916104433.GN11487@google.com \
    --to=lee@kernel.org \
    --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