Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, frederic.danis@collabora.com
Subject: RE: [v4,RESEND] Bluetooth: MGMT: Add management security level changed event
Date: Fri, 25 Sep 2026 08:34:27 -0700 (PDT)	[thread overview]
Message-ID: <6ab69483.24304cfb.18cbc8.2597@mx.google.com> (raw)
In-Reply-To: <20260925101853.3278769-1-frederic.danis@collabora.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.43 seconds
VerifyFixes                   PASS      0.14 seconds
VerifySignedoff               PASS      0.62 seconds
GitLint                       PASS      0.33 seconds
SubjectPrefix                 PASS      0.13 seconds
BuildKernel                   PASS      21.70 seconds
CheckAllWarning               PASS      24.95 seconds
CheckSparse                   WARNING   27.36 seconds
BuildKernel32                 PASS      22.03 seconds
CheckKernelLLVM               PASS      24.47 seconds
TestRunnerSetup               PASS      573.52 seconds
TestRunner_l2cap-tester       PASS      17.08 seconds
TestRunner_iso-tester         PASS      25.72 seconds
TestRunner_bnep-tester        PASS      2.87 seconds
TestRunner_mgmt-tester        PASS      57.04 seconds
TestRunner_rfcomm-tester      PASS      4.09 seconds
TestRunner_sco-tester         PASS      7.16 seconds
TestRunner_ioctl-tester       PASS      4.26 seconds
TestRunner_mesh-tester        FAIL      7.73 seconds
TestRunner_smp-tester         PASS      4.05 seconds
TestRunner_userchan-tester    PASS      2.94 seconds
TestRunner_6lowpan-tester     PASS      4.07 seconds
IncrementalBuild              PASS      21.14 seconds

Details
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
##############################
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.620 seconds
Mesh - Send cancel - 2                               Timed out    1.999 seconds


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

---
Regards,
Linux Bluetooth


      reply	other threads:[~2026-09-25 15:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 10:18 [PATCH v4 RESEND] Bluetooth: MGMT: Add management security level changed event Frédéric Danis
2026-09-25 15:34 ` 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=6ab69483.24304cfb.18cbc8.2597@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=frederic.danis@collabora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox