From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v2,1/2] Bluetooth: hci_core: Enable buffer flow control for SCO/eSCO
Date: Wed, 12 Mar 2025 08:37:50 -0700 (PDT) [thread overview]
Message-ID: <67d1aa4e.050a0220.17a20f.ee10@mx.google.com> (raw)
In-Reply-To: <20250312151421.201772-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2394 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=943172
---Test result---
Test Summary:
CheckPatch PENDING 0.34 seconds
GitLint PENDING 0.23 seconds
SubjectPrefix PASS 0.24 seconds
BuildKernel PASS 24.83 seconds
CheckAllWarning PASS 27.76 seconds
CheckSparse WARNING 31.09 seconds
BuildKernel32 PASS 24.87 seconds
TestRunnerSetup PASS 556.27 seconds
TestRunner_l2cap-tester PASS 27.73 seconds
TestRunner_iso-tester PASS 62.24 seconds
TestRunner_bnep-tester PASS 7.68 seconds
TestRunner_mgmt-tester FAIL 177.90 seconds
TestRunner_rfcomm-tester PASS 13.22 seconds
TestRunner_sco-tester PASS 17.96 seconds
TestRunner_ioctl-tester PASS 15.13 seconds
TestRunner_mesh-tester PASS 10.95 seconds
TestRunner_smp-tester PASS 11.66 seconds
TestRunner_userchan-tester PASS 8.43 seconds
IncrementalBuild PENDING 0.69 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
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: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 490, Passed: 482 (98.4%), Failed: 4, Not Run: 4
Failed Test Cases
LL Privacy - Add Device 2 (2 Devices to AL) Failed 0.329 seconds
LL Privacy - Set Flags 3 (2 Devices to RL) Failed 0.345 seconds
LL Privacy - Set Flags 4 (RL is full) Failed 0.424 seconds
LL Privacy - Remove Device 3 (Disable RL) Failed 0.382 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-03-12 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 15:14 [PATCH v2 1/2] Bluetooth: hci_core: Enable buffer flow control for SCO/eSCO Luiz Augusto von Dentz
2025-03-12 15:14 ` [PATCH v2 2/2] Bluetooth: hci_vhci: Mark Sync Flow Control as supported Luiz Augusto von Dentz
2025-03-12 15:37 ` bluez.test.bot [this message]
2025-03-12 20:00 ` [PATCH v2 1/2] Bluetooth: hci_core: Enable buffer flow control for SCO/eSCO Pauli Virtanen
2025-03-12 20:30 ` Luiz Augusto von Dentz
2025-03-13 14:00 ` patchwork-bot+bluetooth
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=67d1aa4e.050a0220.17a20f.ee10@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.