From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, abhay.maheshbhai.maheta@intel.com
Subject: RE: hci_event: handling CIS QoS
Date: Wed, 16 Nov 2022 07:03:52 -0800 (PST) [thread overview]
Message-ID: <6374fbd8.4a0a0220.48530.6d2f@mx.google.com> (raw)
In-Reply-To: <20221116143334.4990-1-abhay.maheshbhai.maheta@intel.com>
[-- Attachment #1: Type: text/plain, Size: 5138 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=696036
---Test result---
Test Summary:
CheckPatch PASS 1.33 seconds
GitLint PASS 0.95 seconds
SubjectPrefix FAIL 0.59 seconds
BuildKernel PASS 33.54 seconds
BuildKernel32 PASS 31.34 seconds
Incremental Build with patchesPASS 45.63 seconds
TestRunner: Setup PASS 513.97 seconds
TestRunner: l2cap-tester PASS 16.64 seconds
TestRunner: iso-tester FAIL 16.78 seconds
TestRunner: bnep-tester PASS 6.58 seconds
TestRunner: mgmt-tester PASS 101.31 seconds
TestRunner: rfcomm-tester PASS 10.44 seconds
TestRunner: sco-tester PASS 9.29 seconds
TestRunner: ioctl-tester PASS 11.12 seconds
TestRunner: mesh-tester PASS 7.99 seconds
TestRunner: smp-tester PASS 9.90 seconds
TestRunner: userchan-tester PASS 6.81 seconds
Details
##############################
Test: SubjectPrefix - FAIL - 0.59 seconds
Check subject contains "Bluetooth" prefix
"Bluetooth: " is not specified in the subject
##############################
Test: TestRunner: iso-tester - FAIL - 16.78 seconds
Run test-runner with iso-tester
Total: 55, Passed: 11 (20.0%), Failed: 44, Not Run: 0
Failed Test Cases
ISO QoS 8_1_1 - Success Failed 1.977 seconds
ISO QoS 8_2_1 - Success Failed 0.152 seconds
ISO QoS 16_1_1 - Success Failed 0.151 seconds
ISO QoS 16_2_1 - Success Failed 0.150 seconds
ISO QoS 16_2_1 CIG 0x01 - Success Failed 0.150 seconds
ISO QoS 16_2_1 CIG 0x01 CIS 0x01 - Success Failed 0.150 seconds
ISO QoS 24_1_1 - Success Failed 0.149 seconds
ISO QoS 24_2_1 - Success Failed 0.152 seconds
ISO QoS 32_1_1 - Success Failed 0.150 seconds
ISO QoS 32_2_1 - Success Failed 0.150 seconds
ISO QoS 44_1_1 - Success Failed 0.150 seconds
ISO QoS 44_2_1 - Success Failed 0.156 seconds
ISO QoS 48_1_1 - Success Failed 0.151 seconds
ISO QoS 48_2_1 - Success Failed 0.150 seconds
ISO QoS 48_3_1 - Success Failed 0.150 seconds
ISO QoS 48_4_1 - Success Failed 0.149 seconds
ISO QoS 48_5_1 - Success Failed 0.150 seconds
ISO QoS 48_6_1 - Success Failed 0.148 seconds
ISO QoS 8_1_2 - Success Failed 0.150 seconds
ISO QoS 8_2_2 - Success Failed 0.149 seconds
ISO QoS 16_1_2 - Success Failed 0.150 seconds
ISO QoS 16_2_2 - Success Failed 0.150 seconds
ISO QoS 24_1_2 - Success Failed 0.150 seconds
ISO QoS 24_2_2 - Success Failed 0.150 seconds
ISO QoS 32_1_2 - Success Failed 0.148 seconds
ISO QoS 32_2_2 - Success Failed 0.150 seconds
ISO QoS 44_1_2 - Success Failed 0.148 seconds
ISO QoS 44_2_2 - Success Failed 0.150 seconds
ISO QoS 48_1_2 - Success Failed 0.149 seconds
ISO QoS 48_2_2 - Success Failed 0.148 seconds
ISO QoS 48_3_2 - Success Failed 0.150 seconds
ISO QoS 48_4_2 - Success Failed 0.149 seconds
ISO QoS 48_5_2 - Success Failed 0.149 seconds
ISO QoS 48_6_2 - Success Failed 0.151 seconds
ISO Connect2 CIG 0x01 - Success Failed 0.191 seconds
ISO Send - Success Failed 0.153 seconds
ISO Receive - Success Failed 0.167 seconds
ISO Defer Send - Success Failed 0.156 seconds
ISO 48_2_1 Defer Send - Success Failed 0.158 seconds
ISO Defer Receive - Success Failed 0.154 seconds
ISO 48_2_1 Defer Receive - Success Failed 0.150 seconds
ISO Send and Receive - Success Failed 0.157 seconds
ISO Disconnect - Success Failed 0.162 seconds
ISO Reconnect - Success Failed 0.163 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-11-16 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 14:33 [PATCH] hci_event: handling CIS QoS Abhay Maheta
2022-11-16 15:03 ` bluez.test.bot [this message]
2022-11-16 21:28 ` Luiz Augusto von Dentz
2022-11-16 15:27 ` [PATCH] " Paul Menzel
2022-11-16 23:01 ` kernel test robot
2022-11-18 4:15 ` bluez.test.bot
2022-11-18 5:05 ` bluez.test.bot
2022-11-18 5:56 ` bluez.test.bot
2022-11-18 7:07 ` bluez.test.bot
2022-11-18 7:54 ` 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=6374fbd8.4a0a0220.48530.6d2f@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=abhay.maheshbhai.maheta@intel.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