From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ssorensen@roku.com
Subject: RE: Bluetooth: Fixes for BR/EDR connection idle timeout configuration
Date: Tue, 16 Dec 2025 02:09:10 -0800 (PST) [thread overview]
Message-ID: <69412fc6.050a0220.25ca59.2046@mx.google.com> (raw)
In-Reply-To: <20251216092011.111208-2-ssorensen@roku.com>
[-- Attachment #1: Type: text/plain, Size: 3030 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=1033698
---Test result---
Test Summary:
CheckPatch PENDING 0.36 seconds
GitLint PENDING 0.27 seconds
SubjectPrefix PASS 0.33 seconds
BuildKernel PASS 25.25 seconds
CheckAllWarning PASS 27.92 seconds
CheckSparse WARNING 31.32 seconds
BuildKernel32 PASS 25.31 seconds
TestRunnerSetup PASS 551.71 seconds
TestRunner_l2cap-tester PASS 25.41 seconds
TestRunner_iso-tester PASS 80.01 seconds
TestRunner_bnep-tester PASS 6.24 seconds
TestRunner_mgmt-tester FAIL 115.42 seconds
TestRunner_rfcomm-tester PASS 9.40 seconds
TestRunner_sco-tester FAIL 14.50 seconds
TestRunner_ioctl-tester PASS 10.44 seconds
TestRunner_mesh-tester FAIL 11.56 seconds
TestRunner_smp-tester PASS 8.57 seconds
TestRunner_userchan-tester PASS 6.59 seconds
IncrementalBuild PENDING 0.79 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/mgmt_config.c:127:17: warning: incorrect type in initializer (different base types)net/bluetooth/mgmt_config.c:127:17: expected restricted __le16 [usertype] typenet/bluetooth/mgmt_config.c:127:17: got restricted __le32 [usertype]
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 488 (98.8%), Failed: 2, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.103 seconds
LL Privacy - Set Flags 1 (Add to RL) Failed 0.153 seconds
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
BUG: sleeping function called from invalid context at net/core/sock.c:3782
Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 1.850 seconds
Mesh - Send cancel - 2 Timed out 1.997 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-12-16 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 9:20 [PATCH 0/3] Bluetooth: Fixes for BR/EDR connection idle timeout configuration Stefan Sørensen
2025-12-16 9:20 ` [PATCH 1/3] Bluetooth: hci_conn: use mod_delayed_work for active mode timeout Stefan Sørensen
2025-12-16 10:09 ` bluez.test.bot [this message]
2025-12-16 9:20 ` [PATCH 2/3] Bluetooth: hci_conn: Set link_policy on incoming ACL connections Stefan Sørensen
2025-12-16 9:20 ` [PATCH 3/3] Bluetooth: mgmt: Add idle_timeout to configurable system parameters Stefan Sørensen
2025-12-16 15:02 ` Luiz Augusto von Dentz
2025-12-20 14:23 ` kernel test robot
2025-12-20 14:45 ` kernel test robot
2025-12-20 15:10 ` kernel test robot
2025-12-20 18:54 ` kernel test robot
2025-12-17 21:50 ` [PATCH 0/3] Bluetooth: Fixes for BR/EDR connection idle timeout configuration 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=69412fc6.050a0220.25ca59.2046@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ssorensen@roku.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.