From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, Tim.Bird@sony.com
Subject: RE: [v2] Bluetooth: Add SPDX id lines to some source files
Date: Wed, 03 Jun 2026 22:48:59 -0700 (PDT) [thread overview]
Message-ID: <6a2111cb.541e6ed7.38c93c.64f0@mx.google.com> (raw)
In-Reply-To: <20260604004125.715884-1-tim.bird@sony.com>
[-- Attachment #1: Type: text/plain, Size: 2473 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=1105609
---Test result---
Test Summary:
CheckPatch PASS 11.11 seconds
VerifyFixes PASS 0.12 seconds
VerifySignedoff PASS 0.12 seconds
GitLint PASS 0.29 seconds
SubjectPrefix PASS 0.16 seconds
BuildKernel PASS 24.21 seconds
CheckAllWarning PASS 26.43 seconds
CheckSparse PASS 25.14 seconds
BuildKernel32 PASS 23.25 seconds
TestRunnerSetup PASS 521.43 seconds
TestRunner_l2cap-tester FAIL 60.35 seconds
TestRunner_iso-tester PASS 82.36 seconds
TestRunner_bnep-tester PASS 18.66 seconds
TestRunner_mgmt-tester FAIL 212.20 seconds
TestRunner_rfcomm-tester PASS 25.41 seconds
TestRunner_sco-tester PASS 32.36 seconds
TestRunner_ioctl-tester PASS 25.64 seconds
TestRunner_mesh-tester FAIL 24.88 seconds
TestRunner_smp-tester PASS 23.19 seconds
TestRunner_userchan-tester PASS 19.58 seconds
TestRunner_6lowpan-tester PASS 22.48 seconds
IncrementalBuild PASS 22.52 seconds
Details
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Total: 96, Passed: 95 (99.0%), Failed: 1, Not Run: 0
Failed Test Cases
L2CAP BR/EDR Server - Set PHY 3M Failed 0.277 seconds
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.243 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 1.857 seconds
Mesh - Send cancel - 2 Timed out 1.989 seconds
https://github.com/bluez/bluetooth-next/pull/285
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-06-04 5:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 0:41 [PATCH v2] Bluetooth: Add SPDX id lines to some source files Tim Bird
2026-06-04 5:48 ` bluez.test.bot [this message]
2026-06-04 11:32 ` Bastien Nocera
2026-06-04 15:16 ` Luiz Augusto von Dentz
2026-06-04 16:38 ` Bird, Tim
2026-06-04 15:28 ` Luiz Augusto von Dentz
2026-06-04 16:41 ` Bird, Tim
2026-06-04 16:53 ` Luiz Augusto von Dentz
2026-06-04 17:03 ` Bird, Tim
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=6a2111cb.541e6ed7.38c93c.64f0@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=Tim.Bird@sony.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