From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, daniel@makrotopia.org
Subject: RE: device_schedule_reprobe(): core helper and conversions
Date: Thu, 10 Sep 2026 12:07:53 -0700 (PDT) [thread overview]
Message-ID: <6aa30009.0db9a8d2.b7c7e.d4b9@mx.google.com> (raw)
In-Reply-To: <1b051bb8145febf69cb33d9e8a83444db079e8f2.1787281239.git.daniel@makrotopia.org>
[-- Attachment #1: Type: text/plain, Size: 2455 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/1149424/
---Test result---
Test Summary:
CheckPatch PASS 3.48 seconds
VerifyFixes PASS 0.10 seconds
VerifySignedoff PASS 0.10 seconds
GitLint PASS 1.24 seconds
SubjectPrefix FAIL 0.39 seconds
BuildKernel PASS 29.55 seconds
CheckAllWarning PASS 33.66 seconds
CheckSparse PASS 36.63 seconds
BuildKernel32 PASS 30.00 seconds
CheckKernelLLVM PASS 43.82 seconds
TestRunnerSetup PASS 775.59 seconds
TestRunner_l2cap-tester PASS 44.07 seconds
TestRunner_iso-tester PASS 93.05 seconds
TestRunner_bnep-tester PASS 12.56 seconds
TestRunner_mgmt-tester FAIL 145.83 seconds
TestRunner_rfcomm-tester PASS 16.05 seconds
TestRunner_sco-tester PASS 23.41 seconds
TestRunner_ioctl-tester PASS 17.22 seconds
TestRunner_mesh-tester FAIL 18.17 seconds
TestRunner_smp-tester PASS 14.88 seconds
TestRunner_userchan-tester PASS 12.96 seconds
TestRunner_6lowpan-tester PASS 16.38 seconds
IncrementalBuild PASS 39.00 seconds
Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 501, Passed: 496 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.156 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.116 seconds
Mesh - Send cancel - 2 Timed out 1.996 seconds
https://github.com/bluez/bluetooth-next/pull/740
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-10 19:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 3:08 [PATCH v3 0/4] device_schedule_reprobe(): core helper and conversions Daniel Golle
2026-08-21 3:08 ` [PATCH v3 1/4] driver core: add device_schedule_reprobe() Daniel Golle
2026-08-21 4:26 ` device_schedule_reprobe(): core helper and conversions bluez.test.bot
2026-09-10 19:07 ` bluez.test.bot [this message]
2026-08-21 3:08 ` [PATCH v3 2/4] wifi: iwlwifi: use device_schedule_reprobe() Daniel Golle
2026-08-21 3:08 ` [PATCH v3 3/4] Bluetooth: hci_h5: " Daniel Golle
2026-08-21 3:08 ` [PATCH v3 4/4] Bluetooth: btintel_pcie: use device_schedule_reprobe() after reset Daniel Golle
-- strict thread matches above, loose matches on Subject: below --
2026-10-17 8:56 [PATCH v4 1/4] driver core: add device_schedule_reprobe() Daniel Golle
2026-10-17 10:32 ` device_schedule_reprobe(): core helper and conversions bluez.test.bot
2026-08-20 0:32 [PATCH v2 1/4] driver core: add device_schedule_reprobe() Daniel Golle
2026-08-20 2:01 ` device_schedule_reprobe(): core helper and conversions bluez.test.bot
2026-08-11 0:48 [RFC PATCH 1/4] driver core: add device_schedule_reprobe() Daniel Golle
2026-08-11 3:28 ` device_schedule_reprobe(): core helper and conversions 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=6aa30009.0db9a8d2.b7c7e.d4b9@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=daniel@makrotopia.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox