From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ravindra@intel.com
Subject: RE: [v1,1/2] Bluetooth: btintel_pcie: Support for S4 (Hibernate)
Date: Wed, 15 Oct 2025 03:00:42 -0700 (PDT) [thread overview]
Message-ID: <68ef70ca.c80a0220.1a1a4e.4453@mx.google.com> (raw)
In-Reply-To: <20251015093903.480282-1-ravindra@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3090 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=1011778
---Test result---
Test Summary:
CheckPatch PENDING 0.35 seconds
GitLint PENDING 0.46 seconds
SubjectPrefix PASS 0.23 seconds
BuildKernel PASS 25.34 seconds
CheckAllWarning PASS 28.15 seconds
CheckSparse PASS 31.67 seconds
BuildKernel32 PASS 25.61 seconds
TestRunnerSetup PASS 496.68 seconds
TestRunner_l2cap-tester PASS 24.29 seconds
TestRunner_iso-tester FAIL 29.76 seconds
TestRunner_bnep-tester PASS 6.32 seconds
TestRunner_mgmt-tester FAIL 125.60 seconds
TestRunner_rfcomm-tester PASS 9.46 seconds
TestRunner_sco-tester PASS 14.51 seconds
TestRunner_ioctl-tester FAIL 10.38 seconds
TestRunner_mesh-tester FAIL 12.39 seconds
TestRunner_smp-tester PASS 8.67 seconds
TestRunner_userchan-tester PASS 6.63 seconds
IncrementalBuild PENDING 1.02 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
BUG: KASAN: slab-use-after-free in iso_conn_hold_unless_zero+0x76/0x1c0
No test result found
##############################
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
Pair Device - Legacy Success 1 Failed 0.202 seconds
Pair Device - Sec Mode 3 Success 1 Failed 0.190 seconds
Pair Device - Legacy Reject 2 Failed 0.165 seconds
Read Exp Feature - Success Failed 0.106 seconds
##############################
Test: TestRunner_ioctl-tester - FAIL
Desc: Run ioctl-tester with test-runner
Output:
Total: 28, Passed: 26 (92.9%), Failed: 2, Not Run: 0
Failed Test Cases
Connection List Failed 1.059 seconds
Connection Info Failed 0.143 seconds
##############################
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 2.776 seconds
Mesh - Send cancel - 2 Timed out 1.999 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-10-15 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 9:39 [PATCH v1 1/2] Bluetooth: btintel_pcie: Support for S4 (Hibernate) Ravindra
2025-10-15 9:39 ` [PATCH v1 2/2] Bluetooth: btintel_pcie: Suspend/Resume: Controller doorbell interrupt handling Ravindra
2025-10-15 10:00 ` bluez.test.bot [this message]
2025-10-22 13:50 ` [PATCH v1 1/2] Bluetooth: btintel_pcie: Support for S4 (Hibernate) 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=68ef70ca.c80a0220.1a1a4e.4453@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ravindra@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).