From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kiran.k@intel.com
Subject: RE: [v1,1/4] Bluetooth: btintel_pcie: Setup buffers for firmware traces
Date: Tue, 18 Feb 2025 05:17:53 -0800 (PST) [thread overview]
Message-ID: <67b48881.050a0220.239e4.6d32@mx.google.com> (raw)
In-Reply-To: <20250218122620.762523-1-kiran.k@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3416 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=935089
---Test result---
Test Summary:
CheckPatch PENDING 0.40 seconds
GitLint PENDING 0.26 seconds
SubjectPrefix PASS 0.31 seconds
BuildKernel PASS 24.71 seconds
CheckAllWarning PASS 26.95 seconds
CheckSparse PASS 30.76 seconds
BuildKernel32 PASS 24.33 seconds
TestRunnerSetup PASS 431.41 seconds
TestRunner_l2cap-tester PASS 20.91 seconds
TestRunner_iso-tester FAIL 148.82 seconds
TestRunner_bnep-tester PASS 4.80 seconds
TestRunner_mgmt-tester FAIL 129.13 seconds
TestRunner_rfcomm-tester PASS 8.32 seconds
TestRunner_sco-tester PASS 9.58 seconds
TestRunner_ioctl-tester PASS 8.39 seconds
TestRunner_mesh-tester PASS 6.09 seconds
TestRunner_smp-tester PASS 7.19 seconds
TestRunner_userchan-tester PASS 4.96 seconds
IncrementalBuild PENDING 0.56 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:
Total: 125, Passed: 108 (86.4%), Failed: 13, Not Run: 4
Failed Test Cases
ISO Connect2 CIG 0x01 - Success Timed out 2.621 seconds
ISO Defer Connect2 CIG 0x01 - Success Timed out 2.270 seconds
ISO Connected2 Suspend - Success Timed out 2.713 seconds
ISO AC 6(ii) - Success Timed out 1.882 seconds
ISO AC 7(ii) - Success Timed out 2.514 seconds
ISO AC 8(ii) - Success Timed out 2.500 seconds
ISO AC 9(ii) - Success Timed out 2.507 seconds
ISO AC 11(ii) - Success Timed out 2.515 seconds
ISO AC 1 + 2 - Success Timed out 1.968 seconds
ISO AC 1 + 2 CIG 0x01/0x02 - Success Timed out 1.999 seconds
ISO Reconnect AC 6(i) - Success Timed out 2.023 seconds
ISO Reconnect AC 6(ii) - Success Timed out 2.000 seconds
ISO AC 6(ii) CIS 0xEF/auto - Success Timed out 1.999 seconds
##############################
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 3 (AL is full) Failed 0.190 seconds
LL Privacy - Set Flags 3 (2 Devices to RL) Failed 0.174 seconds
LL Privacy - Unpair 1 Timed out 1.894 seconds
LL Privacy - Unpair 2 (Remove from AL) Failed 2.548 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-02-18 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 12:26 [PATCH v1 1/4] Bluetooth: btintel_pcie: Setup buffers for firmware traces Kiran K
2025-02-18 12:26 ` [PATCH v1 2/4] Bluetooth: btintel_pcie: Read hardware exception data Kiran K
2025-02-18 17:28 ` Luiz Augusto von Dentz
2025-02-20 8:11 ` K, Kiran
2025-02-18 12:26 ` [PATCH v1 3/4] Bluetooth: btintel_pcie: Add support for device coredump Kiran K
2025-02-18 12:26 ` [PATCH v1 4/4] Bluetooth: btintel_pcie: Trigger device coredump on exception Kiran K
2025-02-18 13:17 ` bluez.test.bot [this message]
2025-02-18 17:54 ` [PATCH v1 1/4] Bluetooth: btintel_pcie: Setup buffers for firmware traces kernel test robot
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=67b48881.050a0220.239e4.6d32@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=kiran.k@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 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.