From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, shuai.zhang@oss.qualcomm.com
Subject: RE: [v1] arm64: dts: monac-arduino-monza: Add Bluetooth UART node
Date: Thu, 30 Apr 2026 13:18:01 -0700 (PDT) [thread overview]
Message-ID: <69f3b8f9.050a0220.20bda4.8947@mx.google.com> (raw)
In-Reply-To: <20260428025652.662502-1-shuai.zhang@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 3265 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/project/bluetooth/list/?series=1086526
---Test result---
Test Summary:
CheckPatch PASS 0.71 seconds
GitLint PASS 0.29 seconds
SubjectPrefix FAIL 0.11 seconds
BuildKernel PASS 28.03 seconds
CheckAllWarning PASS 27.20 seconds
CheckSparse PASS 25.80 seconds
BuildKernel32 PASS 24.04 seconds
TestRunnerSetup PASS 519.97 seconds
TestRunner_l2cap-tester FAIL 6.63 seconds
TestRunner_iso-tester PASS 295.81 seconds
TestRunner_bnep-tester FAIL 6.66 seconds
TestRunner_mgmt-tester FAIL 8.83 seconds
TestRunner_rfcomm-tester PASS 29.08 seconds
TestRunner_sco-tester PASS 68.28 seconds
TestRunner_ioctl-tester FAIL 37.35 seconds
TestRunner_mesh-tester PASS 27.08 seconds
TestRunner_smp-tester PASS 6.63 seconds
TestRunner_userchan-tester FAIL 6.65 seconds
TestRunner_6lowpan-tester PASS 22.89 seconds
IncrementalBuild PASS 23.77 seconds
Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
No test result found
##############################
Test: TestRunner_bnep-tester - FAIL
Desc: Run bnep-tester with test-runner
Output:
No test result found
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
No test result found
##############################
Test: TestRunner_ioctl-tester - FAIL
Desc: Run ioctl-tester with test-runner
Output:
Total: 28, Passed: 0 (0.0%), Failed: 11, Not Run: 17
Failed Test Cases
Device List Timed out -30.845 seconds
Device Info Timed out -6.203 seconds
Reset Stat Timed out -6.207 seconds
Set Link Mode - ACCEPT Timed out -6.209 seconds
Set Pkt Type - DM Timed out -14.393 seconds
Set Pkt Type - DH Timed out -14.397 seconds
Set Pkt Type - HV Timed out -14.399 seconds
Set Pkt Type - 2-DH Timed out -14.402 seconds
Set Pkt Type - 2-DH Timed out -14.404 seconds
Set Pkt Type - ALL Timed out -14.407 seconds
Set ACL MTU - 1 Timed out -14.409 seconds
##############################
Test: TestRunner_userchan-tester - FAIL
Desc: Run userchan-tester with test-runner
Output:
No test result found
https://github.com/bluez/bluetooth-next/pull/138
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-04-30 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 2:56 [PATCH v1] arm64: dts: monac-arduino-monza: Add Bluetooth UART node Shuai Zhang
2026-04-28 6:16 ` Paul Menzel
2026-04-28 9:31 ` Konrad Dybcio
2026-04-28 11:26 ` Dmitry Baryshkov
2026-04-30 20:18 ` 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=69f3b8f9.050a0220.20bda4.8947@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=shuai.zhang@oss.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox