From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, yang.li@amlogic.com
Subject: RE: [v2] Bluetooth: fix socket matching ambiguity between BIS and CIS
Date: Fri, 09 May 2025 04:02:20 -0700 (PDT) [thread overview]
Message-ID: <681de0bc.050a0220.1b4ddb.530e@mx.google.com> (raw)
In-Reply-To: <20250509-iso-v2-1-da53bd18c193@amlogic.com>
[-- Attachment #1: Type: text/plain, Size: 2896 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=961268
---Test result---
Test Summary:
CheckPatch PENDING 0.37 seconds
GitLint PENDING 0.25 seconds
SubjectPrefix PASS 1.15 seconds
BuildKernel PASS 24.23 seconds
CheckAllWarning PASS 26.98 seconds
CheckSparse WARNING 30.38 seconds
BuildKernel32 PASS 23.75 seconds
TestRunnerSetup PASS 455.29 seconds
TestRunner_l2cap-tester PASS 22.12 seconds
TestRunner_iso-tester FAIL 41.14 seconds
TestRunner_bnep-tester PASS 4.99 seconds
TestRunner_mgmt-tester FAIL 121.78 seconds
TestRunner_rfcomm-tester PASS 7.71 seconds
TestRunner_sco-tester PASS 14.99 seconds
TestRunner_ioctl-tester PASS 8.14 seconds
TestRunner_mesh-tester PASS 6.38 seconds
TestRunner_smp-tester PASS 7.15 seconds
TestRunner_userchan-tester PASS 4.90 seconds
IncrementalBuild PENDING 0.51 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
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_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
Total: 127, Passed: 122 (96.1%), Failed: 4, Not Run: 1
Failed Test Cases
ISO Broadcaster Receiver - Success Timed out 2.393 seconds
ISO Broadcaster Receiver SID 0xff - Success Timed out 1.994 seconds
ISO Broadcaster Receiver2 - Success Timed out 2.010 seconds
ISO Broadcaster Receiver Encrypted - Success Timed out 1.986 seconds
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 490, Passed: 482 (98.4%), Failed: 4, Not Run: 4
Failed Test Cases
LL Privacy - Add Device 3 (AL is full) Failed 0.202 seconds
LL Privacy - Set Flags 1 (Add to RL) Failed 0.149 seconds
LL Privacy - Set Flags 2 (Enable RL) Failed 0.157 seconds
LL Privacy - Start Discovery 2 (Disable RL) Failed 0.198 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-05-09 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 10:17 [PATCH v2] Bluetooth: fix socket matching ambiguity between BIS and CIS Yang Li
2025-05-09 10:17 ` Yang Li via B4 Relay
2025-05-09 11:02 ` bluez.test.bot [this message]
2025-05-09 15:46 ` Pauli Virtanen
2025-05-09 16:13 ` Luiz Augusto von Dentz
2025-05-12 11:55 ` Yang Li
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=681de0bc.050a0220.1b4ddb.530e@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=yang.li@amlogic.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 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.