From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v2] Bluetooth: hci_event: Fix parsing of CIS Established Event
Date: Wed, 21 Jun 2023 13:33:34 -0700 (PDT) [thread overview]
Message-ID: <64935e9e.920a0220.aea31.2390@mx.google.com> (raw)
In-Reply-To: <20230621195407.977001-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 7049 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=759261
---Test result---
Test Summary:
CheckPatch PASS 0.62 seconds
GitLint PASS 0.28 seconds
SubjectPrefix PASS 0.10 seconds
BuildKernel PASS 32.43 seconds
CheckAllWarning PASS 35.86 seconds
CheckSparse WARNING 40.37 seconds
CheckSmatch WARNING 112.71 seconds
BuildKernel32 PASS 31.55 seconds
TestRunnerSetup PASS 449.78 seconds
TestRunner_l2cap-tester PASS 16.88 seconds
TestRunner_iso-tester FAIL 31.32 seconds
TestRunner_bnep-tester PASS 5.38 seconds
TestRunner_mgmt-tester PASS 129.16 seconds
TestRunner_rfcomm-tester PASS 8.76 seconds
TestRunner_sco-tester PASS 8.00 seconds
TestRunner_ioctl-tester PASS 9.41 seconds
TestRunner_mesh-tester PASS 6.80 seconds
TestRunner_smp-tester PASS 8.00 seconds
TestRunner_userchan-tester PASS 5.66 seconds
IncrementalBuild PASS 30.47 seconds
Details
##############################
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: CheckSmatch - WARNING
Desc: Run smatch tool with source
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: 80, Passed: 17 (21.2%), Failed: 63, Not Run: 0
Failed Test Cases
ISO QoS 8_1_1 - Success Failed 1.140 seconds
ISO QoS 8_2_1 - Success Failed 0.207 seconds
ISO QoS 16_1_1 - Success Failed 0.211 seconds
ISO QoS 16_2_1 - Success Failed 0.205 seconds
ISO QoS 16_2_1 CIG 0x01 - Success Failed 0.208 seconds
ISO QoS 16_2_1 CIG 0x01 CIS 0x01 - Success Failed 0.206 seconds
ISO QoS 24_1_1 - Success Failed 0.208 seconds
ISO QoS 24_2_1 - Success Failed 0.210 seconds
ISO QoS 32_1_1 - Success Failed 0.206 seconds
ISO QoS 32_2_1 - Success Failed 0.202 seconds
ISO QoS 44_1_1 - Success Failed 0.205 seconds
ISO QoS 44_2_1 - Success Failed 0.197 seconds
ISO QoS 48_1_1 - Success Failed 0.197 seconds
ISO QoS 48_2_1 - Success Failed 0.208 seconds
ISO QoS 48_3_1 - Success Failed 0.207 seconds
ISO QoS 48_4_1 - Success Failed 0.206 seconds
ISO QoS 48_5_1 - Success Failed 0.199 seconds
ISO QoS 48_6_1 - Success Failed 0.198 seconds
ISO QoS 8_1_2 - Success Failed 0.208 seconds
ISO QoS 8_2_2 - Success Failed 0.205 seconds
ISO QoS 16_1_2 - Success Failed 0.209 seconds
ISO QoS 16_2_2 - Success Failed 0.205 seconds
ISO QoS 24_1_2 - Success Failed 0.207 seconds
ISO QoS 24_2_2 - Success Failed 0.206 seconds
ISO QoS 32_1_2 - Success Failed 0.207 seconds
ISO QoS 32_2_2 - Success Failed 0.206 seconds
ISO QoS 44_1_2 - Success Failed 0.202 seconds
ISO QoS 44_2_2 - Success Failed 0.206 seconds
ISO QoS 48_1_2 - Success Failed 0.207 seconds
ISO QoS 48_2_2 - Success Failed 0.198 seconds
ISO QoS 48_3_2 - Success Failed 0.199 seconds
ISO QoS 48_4_2 - Success Failed 0.207 seconds
ISO QoS 48_5_2 - Success Failed 0.199 seconds
ISO QoS 48_6_2 - Success Failed 0.210 seconds
ISO Send - Success Failed 0.203 seconds
ISO Receive - Success Failed 0.194 seconds
ISO Receive Timestamped - Success Failed 0.185 seconds
ISO Defer Connect - Success Failed 0.205 seconds
ISO Defer Connect2 CIG 0x01 - Success Failed 0.295 seconds
ISO Defer Send - Success Failed 0.207 seconds
ISO 48_2_1 Defer Send - Success Failed 0.209 seconds
ISO Defer Receive - Success Failed 0.187 seconds
ISO 48_2_1 Defer Receive - Success Failed 0.184 seconds
ISO Send and Receive - Success Failed 0.209 seconds
ISO Disconnect - Success Failed 0.208 seconds
ISO Reconnect - Success Failed 0.202 seconds
ISO AC 1 & 4 - Success Failed 0.200 seconds
ISO AC 2 & 10 - Success Failed 0.199 seconds
ISO AC 3 & 5 - Success Failed 0.203 seconds
ISO AC 6(i) - Success Failed 0.230 seconds
ISO AC 6(ii) - Success Failed 0.307 seconds
ISO AC 7(i) - Success Failed 0.231 seconds
ISO AC 7(ii) - Success Failed 0.289 seconds
ISO AC 8(i) - Success Failed 0.237 seconds
ISO AC 8(ii) - Success Failed 0.299 seconds
ISO AC 9(i) - Success Failed 0.236 seconds
ISO AC 9(ii) - Success Failed 0.287 seconds
ISO AC 11(i) - Success Failed 0.234 seconds
ISO AC 11(ii) - Success Failed 0.297 seconds
ISO AC 1 + 2 - Success Failed 4.292 seconds
ISO AC 1 + 2 CIG 0x01/0x02 - Success Failed 4.287 seconds
ISO Reconnect AC 6(i) - Success Failed 0.296 seconds
ISO Reconnect AC 6(ii) - Success Failed 0.294 seconds
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-06-21 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 19:54 [PATCH v2] Bluetooth: hci_event: Fix parsing of CIS Established Event Luiz Augusto von Dentz
2023-06-21 20:33 ` Pauli Virtanen
2023-06-21 21:12 ` Luiz Augusto von Dentz
2023-06-21 21:46 ` Pauli Virtanen
2023-06-21 22:23 ` Luiz Augusto von Dentz
2023-06-21 20:33 ` 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=64935e9e.920a0220.aea31.2390@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 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.