From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_chejiang@quicinc.com
Subject: RE: Expand firmware-name property to load specific
Date: Tue, 07 Jan 2025 01:56:04 -0800 (PST) [thread overview]
Message-ID: <677cfa34.050a0220.4339c.92fb@mx.google.com> (raw)
In-Reply-To: <20250107092650.498154-2-quic_chejiang@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 2364 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=922834
---Test result---
Test Summary:
CheckPatch PENDING 0.29 seconds
GitLint PENDING 0.21 seconds
SubjectPrefix FAIL 0.57 seconds
BuildKernel PASS 25.76 seconds
CheckAllWarning PASS 27.54 seconds
CheckSparse PASS 31.11 seconds
BuildKernel32 PASS 24.84 seconds
TestRunnerSetup PASS 435.99 seconds
TestRunner_l2cap-tester PASS 22.59 seconds
TestRunner_iso-tester PASS 36.10 seconds
TestRunner_bnep-tester PASS 4.81 seconds
TestRunner_mgmt-tester FAIL 121.09 seconds
TestRunner_rfcomm-tester PASS 7.53 seconds
TestRunner_sco-tester PASS 9.35 seconds
TestRunner_ioctl-tester PASS 8.12 seconds
TestRunner_mesh-tester PASS 6.07 seconds
TestRunner_smp-tester FAIL 9.27 seconds
TestRunner_userchan-tester PASS 5.08 seconds
IncrementalBuild PENDING 0.44 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 490, Passed: 485 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
LL Privacy - Add Device 2 (2 Devices to AL) Failed 0.183 seconds
##############################
Test: TestRunner_smp-tester - FAIL
Desc: Run smp-tester with test-runner
Output:
WARNING: CPU: 0 PID: 42 at net/bluetooth/hci_conn.c:567 hci_conn_timeout+0x14e/0x190
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-01-07 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 9:26 [PATCH v6 RESEND 0/3] Expand firmware-name property to load specific Cheng Jiang
2025-01-07 9:26 ` [PATCH v6 RESEND 1/3] dt-bindings: net: bluetooth: qca: Expand firmware-name property Cheng Jiang
2025-01-07 9:56 ` bluez.test.bot [this message]
2025-01-07 9:26 ` [PATCH v6 RESEND 2/3] Bluetooth: qca: Update firmware-name to support board specific nvm Cheng Jiang
2025-01-07 9:26 ` [PATCH v6 RESEND 3/3] Bluetooth: qca: Expand firmware-name to load specific rampatch Cheng Jiang
2025-01-08 16:10 ` [PATCH v6 RESEND 0/3] Expand firmware-name property to load specific patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2024-12-17 14:24 [PATCH v6 1/3] dt-bindings: net: bluetooth: qca: Expand firmware-name property Cheng Jiang
2024-12-17 15:00 ` Expand firmware-name property to load specific bluez.test.bot
2024-12-12 15:02 [PATCH v5 1/4] dt-bindings: net: bluetooth: qca: Expand firmware-name property Cheng Jiang
2024-12-12 15:17 ` Expand firmware-name property to load specific bluez.test.bot
2024-12-10 15:16 [PATCH v4 1/4] dt-bindings: net: bluetooth: qca: Expand firmware-name property Cheng Jiang
2024-12-10 15:45 ` Expand firmware-name property to load specific bluez.test.bot
2024-12-05 10:22 [PATCH v3 1/3] dt-bindings: net: bluetooth: qca: Expand firmware-name property Cheng Jiang
2024-12-05 10:46 ` Expand firmware-name property to load specific 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=677cfa34.050a0220.4339c.92fb@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=quic_chejiang@quicinc.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).