From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v4,1/2] Bluetooth: hci_sync: Use address filtering when HCI_PA_SYNC is set
Date: Mon, 26 Feb 2024 14:34:25 -0800 (PST) [thread overview]
Message-ID: <65dd11f1.050a0220.791de.a3da@mx.google.com> (raw)
In-Reply-To: <20240226220031.1686256-1-luiz.dentz@gmail.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=830056
---Test result---
Test Summary:
CheckPatch PASS 1.29 seconds
GitLint PASS 0.59 seconds
SubjectPrefix PASS 0.21 seconds
BuildKernel PASS 30.03 seconds
CheckAllWarning PASS 33.36 seconds
CheckSparse PASS 39.30 seconds
CheckSmatch PASS 104.56 seconds
BuildKernel32 PASS 29.22 seconds
TestRunnerSetup PASS 536.96 seconds
TestRunner_l2cap-tester FAIL 25.62 seconds
TestRunner_iso-tester FAIL 52.66 seconds
TestRunner_bnep-tester PASS 5.13 seconds
TestRunner_mgmt-tester FAIL 125.49 seconds
TestRunner_rfcomm-tester PASS 7.79 seconds
TestRunner_sco-tester PASS 15.40 seconds
TestRunner_ioctl-tester PASS 8.37 seconds
TestRunner_mesh-tester FAIL 6.46 seconds
TestRunner_smp-tester PASS 7.14 seconds
TestRunner_userchan-tester PASS 5.30 seconds
IncrementalBuild PASS 35.49 seconds
Details
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Total: 51, Passed: 50 (98.0%), Failed: 1, Not Run: 0
Failed Test Cases
L2CAP LE Client - Close socket 2 Timed out 2.692 seconds
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
Total: 117, Passed: 115 (98.3%), Failed: 2, Not Run: 0
Failed Test Cases
ISO Connect Suspend - Success Timed out 10.255 seconds
ISO Connected Suspend - Success Timed out 8.251 seconds
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 492, Passed: 485 (98.6%), Failed: 5, Not Run: 2
Failed Test Cases
Pairing Acceptor - SMP over BR/EDR 2 Timed out 2.658 seconds
LL Privacy - Add Device 4 (2 Devices to AL) Failed 0.158 seconds
LL Privacy - Add Device 5 (2 Devices to RL) Failed 0.175 seconds
LL Privacy - Add Device 6 (RL is full) Failed 0.191 seconds
LL Privacy - Remove Device 4 (Disable Adv) Timed out 2.052 seconds
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 9 (90.0%), Failed: 1, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Failed 0.112 seconds
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2024-02-26 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 22:00 [PATCH v4 1/2] Bluetooth: hci_sync: Use address filtering when HCI_PA_SYNC is set Luiz Augusto von Dentz
2024-02-26 22:00 ` [PATCH v4 2/2] Bluetooth: hci_sync: Use QoS to determine which PHY to scan Luiz Augusto von Dentz
2024-02-26 22:34 ` 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=65dd11f1.050a0220.791de.a3da@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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;
as well as URLs for NNTP newsgroup(s).