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: Thu, 17 Nov 2022 20:15:08 -0800 (PST) [thread overview]
Message-ID: <637706cc.9d0a0220.ad2b5.53b4@mx.google.com> (raw)
In-Reply-To: <20221116143334.4990-1-abhay.maheshbhai.maheta@intel.com>
[-- Attachment #1: Type: text/plain, Size: 5137 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 0.59 seconds
GitLint PASS 0.28 seconds
SubjectPrefix FAIL 0.35 seconds
BuildKernel PASS 33.62 seconds
BuildKernel32 PASS 29.94 seconds
TestRunnerSetup PASS 418.08 seconds
TestRunner_l2cap-tester PASS 15.64 seconds
TestRunner_iso-tester FAIL 14.97 seconds
TestRunner_bnep-tester PASS 5.41 seconds
TestRunner_mgmt-tester PASS 103.52 seconds
TestRunner_rfcomm-tester PASS 9.04 seconds
TestRunner_sco-tester PASS 8.46 seconds
TestRunner_ioctl-tester PASS 9.68 seconds
TestRunner_mesh-tester PASS 6.62 seconds
TestRunner_smp-tester PASS 8.39 seconds
TestRunner_userchan-tester PASS 5.51 seconds
IncrementalBuild PASS 30.91 seconds
Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
Total: 55, Passed: 11 (20.0%), Failed: 44, Not Run: 0
Failed Test Cases
ISO QoS 8_1_1 - Success Failed 2.009 seconds
ISO QoS 8_2_1 - Success Failed 0.142 seconds
ISO QoS 16_1_1 - Success Failed 0.143 seconds
ISO QoS 16_2_1 - Success Failed 0.142 seconds
ISO QoS 16_2_1 CIG 0x01 - Success Failed 0.141 seconds
ISO QoS 16_2_1 CIG 0x01 CIS 0x01 - Success Failed 0.140 seconds
ISO QoS 24_1_1 - Success Failed 0.139 seconds
ISO QoS 24_2_1 - Success Failed 0.141 seconds
ISO QoS 32_1_1 - Success Failed 0.139 seconds
ISO QoS 32_2_1 - Success Failed 0.139 seconds
ISO QoS 44_1_1 - Success Failed 0.142 seconds
ISO QoS 44_2_1 - Success Failed 0.141 seconds
ISO QoS 48_1_1 - Success Failed 0.140 seconds
ISO QoS 48_2_1 - Success Failed 0.140 seconds
ISO QoS 48_3_1 - Success Failed 0.142 seconds
ISO QoS 48_4_1 - Success Failed 0.141 seconds
ISO QoS 48_5_1 - Success Failed 0.139 seconds
ISO QoS 48_6_1 - Success Failed 0.139 seconds
ISO QoS 8_1_2 - Success Failed 0.143 seconds
ISO QoS 8_2_2 - Success Failed 0.143 seconds
ISO QoS 16_1_2 - Success Failed 0.141 seconds
ISO QoS 16_2_2 - Success Failed 0.145 seconds
ISO QoS 24_1_2 - Success Failed 0.142 seconds
ISO QoS 24_2_2 - Success Failed 0.143 seconds
ISO QoS 32_1_2 - Success Failed 0.141 seconds
ISO QoS 32_2_2 - Success Failed 0.141 seconds
ISO QoS 44_1_2 - Success Failed 0.140 seconds
ISO QoS 44_2_2 - Success Failed 0.137 seconds
ISO QoS 48_1_2 - Success Failed 0.140 seconds
ISO QoS 48_2_2 - Success Failed 0.137 seconds
ISO QoS 48_3_2 - Success Failed 0.141 seconds
ISO QoS 48_4_2 - Success Failed 0.139 seconds
ISO QoS 48_5_2 - Success Failed 0.137 seconds
ISO QoS 48_6_2 - Success Failed 0.139 seconds
ISO Connect2 CIG 0x01 - Success Failed 0.176 seconds
ISO Send - Success Failed 0.140 seconds
ISO Receive - Success Failed 0.145 seconds
ISO Defer Send - Success Failed 0.141 seconds
ISO 48_2_1 Defer Send - Success Failed 0.139 seconds
ISO Defer Receive - Success Failed 0.139 seconds
ISO 48_2_1 Defer Receive - Success Failed 0.135 seconds
ISO Send and Receive - Success Failed 0.141 seconds
ISO Disconnect - Success Failed 0.140 seconds
ISO Reconnect - Success Failed 0.141 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-11-18 4:15 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
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 [this message]
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=637706cc.9d0a0220.ad2b5.53b4@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