From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, radek@podgorny.cz
Subject: RE: Bluetooth: dial the address the peer is actually on air with
Date: Tue, 08 Sep 2026 17:23:42 -0700 (PDT) [thread overview]
Message-ID: <6aa0a70e.8e75e0cb.3a5f1c.baa5@mx.google.com> (raw)
In-Reply-To: <20260909-for-upstream-le-connect-on-air-addr-v3-1-0e49c4e7abc2@podgorny.cz>
[-- Attachment #1: Type: text/plain, Size: 2367 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/1160889/
---Test result---
Test Summary:
CheckPatch PASS 1.08 seconds
VerifyFixes PASS 0.08 seconds
VerifySignedoff PASS 0.08 seconds
GitLint PASS 0.53 seconds
SubjectPrefix PASS 0.15 seconds
BuildKernel PASS 25.45 seconds
CheckAllWarning PASS 27.91 seconds
CheckSparse PASS 26.74 seconds
BuildKernel32 PASS 24.55 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 459.84 seconds
TestRunner_l2cap-tester PASS 65.99 seconds
TestRunner_iso-tester PASS 110.99 seconds
TestRunner_bnep-tester PASS 18.95 seconds
TestRunner_mgmt-tester FAIL 223.71 seconds
TestRunner_rfcomm-tester PASS 26.23 seconds
TestRunner_sco-tester PASS 32.16 seconds
TestRunner_ioctl-tester PASS 26.27 seconds
TestRunner_mesh-tester FAIL 25.89 seconds
TestRunner_smp-tester PASS 24.07 seconds
TestRunner_userchan-tester PASS 19.56 seconds
TestRunner_6lowpan-tester PASS 23.07 seconds
IncrementalBuild PASS 26.07 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.249 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.159 seconds
Mesh - Send cancel - 2 Timed out 1.991 seconds
https://github.com/bluez/bluetooth-next/pull/726
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-09 0:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 22:29 [PATCH v3 0/2] Bluetooth: dial the address the peer is actually on air with Radek Podgorny
2026-09-08 22:29 ` [PATCH v3 1/2] Bluetooth: forget a peer's RPA once it advertises its identity address Radek Podgorny
2026-09-09 0:23 ` bluez.test.bot [this message]
2026-09-08 22:29 ` [PATCH v3 2/2] Bluetooth: put the peer's on-air address on air when we cannot resolve Radek Podgorny
2026-09-09 19:40 ` [PATCH v3 0/2] Bluetooth: dial the address the peer is actually on air with 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=6aa0a70e.8e75e0cb.3a5f1c.baa5@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=radek@podgorny.cz \
/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.