From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iulia.tanasescu@nxp.com
Subject: RE: Bluetooth: Split bt_iso_qos into dedicated structures
Date: Tue, 28 Mar 2023 01:03:11 -0700 (PDT) [thread overview]
Message-ID: <64229f3f.a70a0220.65aba.9911@mx.google.com> (raw)
In-Reply-To: <20230328072545.16876-2-iulia.tanasescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 6551 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=734491
---Test result---
Test Summary:
CheckPatch PASS 1.94 seconds
GitLint PASS 0.24 seconds
SubjectPrefix PASS 0.06 seconds
BuildKernel PASS 44.08 seconds
CheckAllWarning PASS 48.31 seconds
CheckSparse WARNING 53.70 seconds
CheckSmatch WARNING 144.02 seconds
BuildKernel32 PASS 42.76 seconds
TestRunnerSetup PASS 607.28 seconds
TestRunner_l2cap-tester PASS 20.13 seconds
TestRunner_iso-tester FAIL 19.69 seconds
TestRunner_bnep-tester PASS 7.10 seconds
TestRunner_mgmt-tester PASS 132.33 seconds
TestRunner_rfcomm-tester PASS 11.07 seconds
TestRunner_sco-tester PASS 10.00 seconds
TestRunner_ioctl-tester PASS 11.91 seconds
TestRunner_mesh-tester PASS 8.81 seconds
TestRunner_smp-tester PASS 9.92 seconds
TestRunner_userchan-tester PASS 7.40 seconds
IncrementalBuild PASS 39.77 seconds
Details
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_conn.c:2095:18: warning: incorrect type in assignment (different base types)net/bluetooth/hci_conn.c:2095:18: expected restricted __le16 [usertype] skipnet/bluetooth/hci_conn.c:2095:18: got unsigned short [usertype] skipnet/bluetooth/hci_conn.c:2096:26: warning: incorrect type in assignment (different base types)net/bluetooth/hci_conn.c:2096:26: expected restricted __le16 [usertype] sync_timeoutnet/bluetooth/hci_conn.c:2096:26: got unsigned short [usertype] sync_timeoutnet/bluetooth/hci_conn.c:2126:24: warning: incorrect type in assignment (different base types)net/bluetooth/hci_conn.c:2126:24: expected restricted __le16 [addressable] [assigned] [usertype] timeoutnet/bluetooth/hci_conn.c:2126:24: got unsigned short [usertype] timeoutnet/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: 57, Passed: 10 (17.5%), Failed: 47, Not Run: 0
Failed Test Cases
Basic ISO Set Socket Option - Success Failed 0.184 seconds
ISO QoS 8_1_1 - Success Failed 0.188 seconds
ISO QoS 8_2_1 - Success Failed 0.176 seconds
ISO QoS 16_1_1 - Success Failed 0.184 seconds
ISO QoS 16_2_1 - Success Failed 0.184 seconds
ISO QoS 16_2_1 CIG 0x01 - Success Failed 0.192 seconds
ISO QoS 16_2_1 CIG 0x01 CIS 0x01 - Success Failed 0.184 seconds
ISO QoS 24_1_1 - Success Failed 0.196 seconds
ISO QoS 24_2_1 - Success Failed 0.180 seconds
ISO QoS 32_1_1 - Success Failed 0.176 seconds
ISO QoS 32_2_1 - Success Failed 0.188 seconds
ISO QoS 44_1_1 - Success Failed 0.188 seconds
ISO QoS 44_2_1 - Success Failed 0.184 seconds
ISO QoS 48_1_1 - Success Failed 0.184 seconds
ISO QoS 48_2_1 - Success Failed 0.180 seconds
ISO QoS 48_3_1 - Success Failed 0.176 seconds
ISO QoS 48_4_1 - Success Failed 0.184 seconds
ISO QoS 48_5_1 - Success Failed 0.184 seconds
ISO QoS 48_6_1 - Success Failed 0.200 seconds
ISO QoS 8_1_2 - Success Failed 0.192 seconds
ISO QoS 8_2_2 - Success Failed 0.184 seconds
ISO QoS 16_1_2 - Success Failed 0.176 seconds
ISO QoS 16_2_2 - Success Failed 0.188 seconds
ISO QoS 24_1_2 - Success Failed 0.176 seconds
ISO QoS 24_2_2 - Success Failed 0.192 seconds
ISO QoS 32_1_2 - Success Failed 0.184 seconds
ISO QoS 32_2_2 - Success Failed 0.188 seconds
ISO QoS 44_1_2 - Success Failed 0.184 seconds
ISO QoS 44_2_2 - Success Failed 0.184 seconds
ISO QoS 48_1_2 - Success Failed 0.192 seconds
ISO QoS 48_2_2 - Success Failed 0.188 seconds
ISO QoS 48_3_2 - Success Failed 0.188 seconds
ISO QoS 48_4_2 - Success Failed 0.176 seconds
ISO QoS 48_5_2 - Success Failed 0.192 seconds
ISO QoS 48_6_2 - Success Failed 0.180 seconds
ISO Connect - Reject Failed 0.180 seconds
ISO Connect2 CIG 0x01 - Success Failed 0.188 seconds
ISO Send - Success Failed 0.176 seconds
ISO Defer - Success Failed 0.180 seconds
ISO Defer Send - Success Failed 0.184 seconds
ISO 48_2_1 Defer Send - Success Failed 0.188 seconds
ISO Send and Receive - Success Failed 0.176 seconds
ISO Disconnect - Success Failed 0.172 seconds
ISO Reconnect - Success Failed 0.172 seconds
ISO Broadcaster - Success Failed 0.180 seconds
ISO Broadcaster BIG 0x01 - Success Failed 0.184 seconds
ISO Broadcaster BIG 0x01 BIS 0x01 - Success Failed 0.188 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-03-28 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 7:25 [PATCH v2 0/1] Bluetooth: Split bt_iso_qos into dedicated structures Iulia Tanasescu
2023-03-28 7:25 ` [PATCH v2 1/1] " Iulia Tanasescu
2023-03-28 8:03 ` bluez.test.bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-31 15:38 [PATCH v3 " Iulia Tanasescu
2023-03-31 16:35 ` bluez.test.bot
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=64229f3f.a70a0220.65aba.9911@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=iulia.tanasescu@nxp.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 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.