From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zzzccc427@gmail.com
Subject: RE: Bluetooth: 6LoWPAN lifecycle fixes
Date: Mon, 21 Sep 2026 10:34:05 -0700 (PDT) [thread overview]
Message-ID: <6ab16a8d.9eb508be.1ae927.d794@mx.google.com> (raw)
In-Reply-To: <pm-series-6lowpan-lifecycle-82fab5876048c8c9503c-1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2405 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/series/1170521/
---Test result---
Test Summary:
CheckPatch PASS 5.37 seconds
VerifyFixes PASS 0.14 seconds
VerifySignedoff PASS 0.14 seconds
GitLint FAIL 1.79 seconds
SubjectPrefix FAIL 0.66 seconds
BuildKernel PASS 29.34 seconds
CheckAllWarning PASS 33.40 seconds
CheckSparse PASS 36.26 seconds
BuildKernel32 PASS 29.12 seconds
CheckKernelLLVM PASS 35.03 seconds
TestRunnerSetup PASS 797.01 seconds
TestRunner_l2cap-tester PASS 16.57 seconds
TestRunner_iso-tester PASS 28.97 seconds
TestRunner_bnep-tester PASS 3.11 seconds
TestRunner_mgmt-tester PASS 62.84 seconds
TestRunner_rfcomm-tester PASS 4.47 seconds
TestRunner_sco-tester PASS 7.63 seconds
TestRunner_ioctl-tester PASS 4.65 seconds
TestRunner_mesh-tester FAIL 7.84 seconds
TestRunner_smp-tester PASS 4.38 seconds
TestRunner_userchan-tester PASS 3.21 seconds
TestRunner_6lowpan-tester PASS 4.43 seconds
IncrementalBuild PASS 75.68 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[4/5] Bluetooth: 6lowpan: handle channel setup failure and callback lifetime
29: B1 Line exceeds max length (81>80): " [ 101.222759] BUG: unable to handle page fault for address: ffffffffc040199f"
##############################
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.419 seconds
Mesh - Send cancel - 2 Timed out 1.998 seconds
https://github.com/bluez/bluetooth-next/pull/808
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-21 17:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 15:38 [PATCH 0/5] Bluetooth: 6LoWPAN lifecycle fixes Cen Zhang
2026-09-21 15:38 ` [PATCH 1/5] Bluetooth: L2CAP: ignore close requests for deleted channels Cen Zhang
2026-09-21 16:56 ` Pauli Virtanen
2026-09-21 17:34 ` bluez.test.bot [this message]
2026-09-21 15:38 ` [PATCH 2/5] workqueue: add support for module-owned work Cen Zhang
2026-09-21 16:16 ` Tejun Heo
2026-09-21 17:03 ` Cen Zhang
2026-09-21 15:39 ` [PATCH 3/5] Bluetooth: L2CAP: drain channel timers on connection teardown Cen Zhang
2026-09-21 15:54 ` Luiz Augusto von Dentz
2026-09-21 15:39 ` [PATCH 4/5] Bluetooth: 6lowpan: handle channel setup failure and callback lifetime Cen Zhang
2026-09-21 15:39 ` [PATCH 5/5] Bluetooth: 6lowpan: quiesce peers before channel deletion Cen Zhang
2026-09-21 16:07 ` [PATCH 0/5] Bluetooth: 6LoWPAN lifecycle fixes Luiz Augusto von Dentz
2026-09-21 16:59 ` Cen Zhang
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=6ab16a8d.9eb508be.1ae927.d794@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=zzzccc427@gmail.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