From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, aluvala.sai.teja@intel.com
Subject: RE: Bluetooth: add hardware rfkill handling
Date: Thu, 01 Oct 2026 20:14:31 -0700 (PDT) [thread overview]
Message-ID: <6abf2197.ec46f90a.b79ba.26c7@mx.google.com> (raw)
In-Reply-To: <cec8b1c81c62ec805bdc4c32e59515d92e62cc65.1790905146.git.aluvala.sai.teja@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2225 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/1178028/
---Test result---
Test Summary:
CheckPatch PASS 1.50 seconds
VerifyFixes PASS 0.86 seconds
VerifySignedoff PASS 0.74 seconds
GitLint PASS 0.56 seconds
SubjectPrefix PASS 0.17 seconds
BuildKernel PASS 22.65 seconds
CheckAllWarning PASS 26.26 seconds
CheckSparse PASS 27.89 seconds
BuildKernel32 PASS 22.88 seconds
CheckKernelLLVM PASS 25.29 seconds
TestRunnerSetup PASS 566.67 seconds
TestRunner_l2cap-tester PASS 13.50 seconds
TestRunner_iso-tester PASS 9.48 seconds
TestRunner_bnep-tester PASS 2.74 seconds
TestRunner_mgmt-tester FAIL 56.99 seconds
TestRunner_rfcomm-tester PASS 4.01 seconds
TestRunner_sco-tester PASS 5.04 seconds
TestRunner_ioctl-tester PASS 4.14 seconds
TestRunner_mesh-tester FAIL 7.64 seconds
TestRunner_smp-tester PASS 3.91 seconds
TestRunner_userchan-tester PASS 7.88 seconds
TestRunner_6lowpan-tester PASS 5.01 seconds
IncrementalBuild PASS 23.03 seconds
Details
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 503, Passed: 502 (99.8%), Failed: 1, Not Run: 0
Failed Test Cases
Pairing Acceptor - LE Security Level Changed Failed 0.020 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.668 seconds
Mesh - Send cancel - 2 Timed out 1.998 seconds
https://github.com/bluez/bluetooth-next/pull/849
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-02 3:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 1:43 [PATCH v2 0/2] Bluetooth: add hardware rfkill handling Sai Teja Aluvala
2026-10-02 1:43 ` [PATCH v2 1/2] Bluetooth: Add interface to allow stack to communicate hw rfkill events Sai Teja Aluvala
2026-10-02 3:14 ` bluez.test.bot [this message]
2026-10-02 1:43 ` [PATCH v2 2/2] Bluetooth: btintel_pcie: add HW rfkill interrupt/doorbell flow Sai Teja Aluvala
2026-10-02 15:24 ` [PATCH v2 0/2] Bluetooth: add hardware rfkill handling Luiz Augusto von Dentz
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=6abf2197.ec46f90a.b79ba.26c7@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=aluvala.sai.teja@intel.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