From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, wangliang74@huawei.com
Subject: RE: [net-next,v3] net: replace ND_PRINTK with dynamic debug
Date: Mon, 07 Jul 2025 21:23:33 -0700 (PDT) [thread overview]
Message-ID: <686c9d45.c80a0220.6779d.8ac5@mx.google.com> (raw)
In-Reply-To: <20250708033342.1627636-1-wangliang74@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2195 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=979865
---Test result---
Test Summary:
CheckPatch PENDING 0.25 seconds
GitLint PENDING 0.21 seconds
SubjectPrefix FAIL 0.31 seconds
BuildKernel PASS 26.55 seconds
CheckAllWarning PASS 27.29 seconds
CheckSparse PASS 30.12 seconds
BuildKernel32 PASS 24.01 seconds
TestRunnerSetup PASS 465.05 seconds
TestRunner_l2cap-tester PASS 25.09 seconds
TestRunner_iso-tester PASS 38.08 seconds
TestRunner_bnep-tester PASS 5.97 seconds
TestRunner_mgmt-tester PASS 130.40 seconds
TestRunner_rfcomm-tester PASS 9.30 seconds
TestRunner_sco-tester PASS 14.83 seconds
TestRunner_ioctl-tester PASS 10.05 seconds
TestRunner_mesh-tester FAIL 11.45 seconds
TestRunner_smp-tester PASS 8.99 seconds
TestRunner_userchan-tester PASS 6.31 seconds
IncrementalBuild PENDING 0.74 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_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.153 seconds
Mesh - Send cancel - 2 Timed out 1.994 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-07-08 4:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 3:33 [PATCH net-next v3] net: replace ND_PRINTK with dynamic debug Wang Liang
2025-07-08 4:23 ` bluez.test.bot [this message]
2025-07-09 13:10 ` Ido Schimmel
2025-07-11 0:31 ` patchwork-bot+netdevbpf
2025-07-23 15:59 ` 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=686c9d45.c80a0220.6779d.8ac5@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=wangliang74@huawei.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