All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [v2,1/1] Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel
Date: Wed, 2 Sep 2026 11:24:08 +0100	[thread overview]
Message-ID: <20260902102408.GP2943942@google.com> (raw)
In-Reply-To: <CABBYNZJ9PLqVhDKUtGEpsfgK9WOeKynVR6EFmen3s97+J-OWxA@mail.gmail.com>

On Tue, 01 Sep 2026, Luiz Augusto von Dentz wrote:

> Hi Lee,
> 
> On Tue, Sep 1, 2026 at 1:10 PM Luiz Augusto von Dentz
> <luiz.dentz@gmail.com> wrote:
> >
> > Hi Lee,
> >
> > On Tue, Sep 1, 2026 at 1:07 PM <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/project/bluetooth/list/?series=1155482
> > >
> > > ---Test result---
> > >
> > > Test Summary:
> > > CheckPatch                    PASS      0.75 seconds
> > > VerifyFixes                   PASS      0.10 seconds
> > > VerifySignedoff               PASS      0.08 seconds
> > > GitLint                       PASS      0.22 seconds
> > > SubjectPrefix                 PASS      0.07 seconds
> > > BuildKernel                   PASS      28.57 seconds
> > > CheckAllWarning               PASS      31.59 seconds
> > > CheckSparse                   PASS      29.62 seconds
> > > BuildKernel32                 PASS      27.44 seconds
> > > CheckKernelLLVM               SKIP      0.00 seconds
> > > TestRunnerSetup               PASS      510.88 seconds
> > > TestRunner_mgmt-tester        FAIL      233.06 seconds
> > > TestRunner_mesh-tester        FAIL      26.88 seconds
> > > IncrementalBuild              PASS      26.40 seconds
> > >
> > > Details
> > > ##############################
> > > 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.262 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.732 seconds
> > > Mesh - Send cancel - 2                               Timed out    1.986 seconds
> >
> > These are preexisting errorrs but I was hoping your changes would address them.
> 
> Looks like there are more problems:
> 
> https://sashiko.dev/#/patchset/20260901154427.3991920-1-lee%40kernel.org

That's annoying!  I ran Sashiko on this locally before pushing.

Looking now.

-- 
Lee Jones

  reply	other threads:[~2026-09-02 10:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 15:44 [PATCH v2 1/1] Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel Lee Jones
2026-09-01 17:00 ` Greg KH
2026-09-01 17:07 ` [v2,1/1] " bluez.test.bot
2026-09-01 17:10   ` Luiz Augusto von Dentz
2026-09-01 17:22     ` Luiz Augusto von Dentz
2026-09-02 10:24       ` Lee Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-09 11:10 [PATCH v2 1/1] " Lee Jones
2026-09-09 11:46 ` [v2,1/1] " 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=20260902102408.GP2943942@google.com \
    --to=lee@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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 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.